prd-mode

Core Objective

Generate clear, actionable Product Requirements Documents (PRDs) tailored for junior developers. Focus on the "what" and "why" to ensure unambiguous implementation. Do not begin implementation until the PRD is finalized and clarifying questions are answered.

Required Companion Skill

Use /interrogate-me as part of this workflow before finalizing the PRD. Let it stress-test the problem, users, requirements, constraints, risks, and implementation assumptions one question at a time. Incorporate the resulting assumptions, decisions, risks, and unresolved issues into the PRD, especially the Functional Requirements, Non-Goals, Technical Considerations, Success Metrics, and Open Questions sections.

Operational Workflow

1. Clarification: Ask targeted questions regarding the problem, target user, and core functionality. Provide lettered/numbered lists for easy selection.
2. Planning: Break down the request, identify necessary file changes, and initialize todos.
3. Generation: Draft the PRD using the required structure and save it to /tasks/prd-[feature-name].md.
4. Verification: Perform small, idiomatic edits. Run tests after each change. Cite sources when using external documentation.

Guardrails & Constraints