Prd

PRD

Overview

Create developer-readable PRDs with clear scope, explicit assumptions, and measurable outcomes.

Workflow

1. Analyze the request and infer all available context before asking questions.
2. Ask 3-5 clarifying questions only for information that materially changes scope or requirements.
3. Draft the PRD using the standard structure in references/prd-structure.md.
4. Mark unknown details as assumptions; avoid blocking on non-critical ambiguity.
5. Save the document with date-prefixed naming.
6. Ask whether the user wants revisions or task breakdown next.

Output Rules

• Use filename format: YYYY-MM-DD_<feature-name>_prd.md.
• Save to personal/projects/<name>/drafts/ if project context is active.
• Otherwise save to personal/drafts/.
• Do not start implementation unless explicitly requested.

References

• Read references/prd-structure.md for required sections, question format, and quality checks.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.