Idea to PRD

This skill is the first step in the build pipeline — it turns a raw product idea into a structured PRD:

idea-to-prd  →  prd-to-design  →  design-to-tasks  →  tasks-to-code
  (what/why)      (architecture)     (task list)         (build)

prd-to-design is optional — skip it for simple features and hand the PRD straight to design-to-tasks. The full lifecycle this pipeline belongs to — including code-review, release-checklist, plan-retrospective, the audit skills, and the routing rules between them — is defined once in shared conventions.

Intake check: this skill is the entry point for new or changed behavior. If the request is actually a bug ("X is broken") route to debug-and-fix; if it is a structure-only cleanup route to refactor; if the user is unsure what the work even is, route to next-step. Audit findings (from ui-design-audit, security-review, performance-review) arrive as ready-made PRDs and do not pass through this skill — they enter the pipeline at design-to-tasks.

File Structure

The PRD is the first artifact in a plan folder. The full plans/ layout and the active → plans/archive/<name>/ lifecycle are defined once in shared conventions; this skill creates plans/<dasherized-name>/prd.md.

Rules: