| name | idea-to-prd |
| description | Multi-step workflow that takes a raw idea from validation through design to a complete PRD. Chains idea-validator → brainstorming → prd-writer with explicit gates between steps. Use when starting a new feature or side project from scratch. Triggers on: /idea, "validate this idea", "should I build this", "new feature idea", "take this idea to PRD". Prevents building without validating and prevents specifying without designing. |
Idea to PRD Workflow
Converts a raw idea into a production-ready PRD by running three skills in sequence. Each step produces a document that the next step reads before proceeding. Do not skip steps — skipping validation leads to building the wrong thing; skipping design leads to an incoherent PRD.
Skill Chain
idea-validator
↓ [Gate 1: Quick Verdict ≠ "Skip it"]
brainstorming
↓ [Gate 2: design doc exists in docs/designs/]
prd-writer
↓ [Gate 3: PRD sections complete]
→ Hand off to planning or full-stack-build
Step 1 — Validate the Idea
Load skill: idea-validator
Run a rapid validation of the idea before investing any design or engineering time.
Input: One sentence describing the idea, the target user, and the core problem it solves.
Questions idea-validator answers:
- Is there demand evidence or only assumed demand?
- Is market saturation already high?
- Can a solo builder ship an MVP in 2-4 weeks?
- Is there a clear monetization path?
Output: Quick Verdict — one of:
- Build it — validated, proceed to Step 2
- Maybe — proceed to Step 2 with caveats documented
- Skip it — stop here; document reason in
docs/ideas/YYYY-MM-DD-[idea]-skip.md
Gate 1: If Quick Verdict is "Skip it", stop the workflow. Record the verdict and reason. Revisit in 30 days or with new evidence. Do not proceed to Step 2 out of attachment to the idea.
