fcc-to-prd
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know. A PRD records what was decided: anything not established in the conversation or the brief belongs in Open Questions, not stated as a decision.
Process
-
Explore the repo or boilerplate to understand the current state, if you haven't already. If a brief from
fcc-refine-ideaexists (docs/briefs/<slug>-brief.md), treat it as the source of truth for concept, learner, and scope. -
Sketch the seams at which you're going to test the feature. Prefer seams the stack or boilerplate already provides (component boundaries, game-state layer, level/lesson definitions) over new ones. Place any new seam at the highest point you can — the fewer seams, the better; the ideal number is one.
Check with the user that these seams match their expectations. This is the only checkpoint — after it, write the PRD without further questions.
-
Write the PRD to
docs/specs/<slug>-prd.mdusing the template below.
Problem Statement
The problem the audience is facing, from their perspective. Constellation projects serve ordinary people who want to learn, advance their skills, get more productive, or add a tool to their belt.