launch-craft

v0.3.3MITMaking something

Turns raw project briefs and codebase reality into trace-verified PRDs and bespoke, high-craft interactive launch sites. Uses Gemini via agy to update OVERVIEW.md and PRD.md, then crafts a GSAP and Three.js marketing site with live interactive feature slices, authentic Luke Rhodes copy, dual pricing, and 5-platform coverage.

Install

/plugin install launch-craft@fledgeling-plugins

Needs the marketplace added first — how to do that.

Reach for it when

Turn repository briefs, plans, code and mocks into traceable OVERVIEW.md and PRD.md documents, then an interactive launch site grounded in the actual product.

What ships with it

Scripts it runs itself
4 reference files
Measured evals

Say any of this

build a launch site for this repo
update the PRD and marketing website
turn these product briefs into a launch page

Taken from the skill’s own trigger description — these are the phrases it listens for. You do not have to match them exactly.

What comes backIllustrative — written from the skill’s documentation, not captured from a run

build a launch site for this repo and update the PRD

launch-craft pipeline · 4 phases

Phase 1: Gemini Synthesis via agy
  docs/features-to-triage/ ..... 8 briefs scanned
  PRD.md & OVERVIEW.md ......... updated with 100% requirement traceability

Phase 2: Positioning & Copywriting
  docs/positioning/ ............ 00-decision.md verified
  Copy drafted ................. /create-luke-content (marketing persona)
  Pricing architecture ......... $9.99 BYOK perpetual vs $4.99/mo hosted

Phase 3: Interactive Marketing Site
  design/marketing/index.html .. GSAP scroll timeline, Three.js 3D hero,
                                 interactive UI slices, 5-platform badges

Phase 4: Validation Gate
  validate_site.py ............. WCAG AA pass (4.5:1), 0 em dashes, responsive clean

What it delivers

launch-craft:launch-craft turns briefs, plans, code and mocks into traceable OVERVIEW.md and PRD.md documents, a feature-to-source matrix, and a working launch site. Its four phases are synthesis, positioning and copy, implementation, and rendered acceptance.

The site uses the project's confirmed audience, prices, entitlements and supported platforms. Design routes through design-craft:design-craft and ux-craft:ux-craft; Luke-voice copy uses create-luke-content:create-luke-content. GSAP and Three.js are available techniques when motion or 3D belongs in the brief.

The pipeline preserves the user's model division, including Opus 5 planning, Gemini 3.8 implementation and GPT-6 orchestration, using identifiers supported by the current harness.

Quick start

Run /launch-craft:launch-craft in the project and provide the intended launch audience, output location and any approved positioning or commercial decisions. Existing project context supplies the rest; unresolved facts stay explicit.

Verification and limits

The inventory helper lists conventional brief, plan, spec and mock paths. It does not invoke a model or write the documents:

python3 plugins/launch-craft/skills/launch-craft/scripts/run_synthesis.py --root . --dry-run

The source checker can enforce approved text in standalone HTML:

python3 plugins/launch-craft/skills/launch-craft/scripts/validate_site.py launch.html --require-text "Approved product name"

Its exit code covers only the reported source checks. Browser inspection establishes layout, accessibility, dependency loading and interactions. The skill reports unverified checks and never invents shipped features, prices or support claims. Deployment follows the user's authorization.

Install

/plugin add fledgeling-co/fledgeling-plugins
/plugin install launch-craft@fledgeling-plugins