prd-drafter

Draft a new PRD (Product Requirements Document). Conversational discovery followed by structured drafting, with open questions surfaced explicitly. Saves to the path resolved by .prdrc.json (or ./prds/ by default).

Update an existing PRD. Handles three flows — resolving open questions during/after build, scope/content changes, and status promotion through the configured lifecycle. Reads the PRD, asks targeted delta questions, and produces an updated version with a changelog.

Validate a PRD for structural completeness, open-question hygiene, specificity, and internal consistency. Produces a validation report with a status (PASS / CONDITIONAL / FAIL) and a decision-readiness judgement.

Use this agent to turn a captured Feature Context block into a written PRD. Requires a Feature Context block in the conversation (produce one with the prd-interviewer agent first). Writes a structured PRD per the prd-template skill, with all required sections and only the triggered conditional sections. Surfaces open questions in the AI-readable Question/Answer format.

Use this agent at the start of any PRD drafting session to elicit the feature context from the user. Conducts a conversational discovery — not an interrogation — challenging assumptions, surfacing open questions, and producing a Feature Context block that the prd-drafter then turns into a PRD. Use proactively whenever the user invokes /prd-drafter:draft for a new feature.

Use this agent to update an existing PRD. Handles three common update flows — resolving open questions during/after build, expanding scope mid-flight, and promoting a PRD through its status lifecycle. Reads the existing PRD, asks targeted delta questions, and produces an updated version with bumped Version and updated Date.

Use this agent to validate a drafted or updated PRD for structural completeness, open-question hygiene, specificity, and internal consistency. Produces a validation report with a status (PASS / CONDITIONAL / FAIL) and a decision-readiness judgement. Use after any drafter or updater finishes, or when the user runs /prd-drafter:validate.

Conventions for PRD file naming, folder placement, status lifecycle, and project association. Reads .prdrc.json at the repo root for per-repo overrides, otherwise applies sensible defaults. Loaded by every agent in the prd-drafter plugin so drafts land in the right place with consistent naming.

Conversation approach for eliciting a PRD from a user. Defines how to ask questions (batched, not interrogative), when to challenge ideas, how to surface open questions, and how to adapt the template to the feature in front of you. Loaded by the prd-interviewer and prd-drafter agents.

End-to-end workflow for drafting a new Product Requirements Document. Conducts conversational discovery (acting as a PM, not a stenographer), composes the PRD with required and triggered conditional sections, surfaces open questions as first-class output, and saves to the path resolved by .prdrc.json. Use when the user asks to draft, create, write, or start a new PRD for a feature.

Quality checks for a drafted PRD. Defines structural completeness, open-question hygiene, common anti-patterns, and the validator's scoring rubric. Loaded by the prd-validator agent.

The PRD template and section structure used by the prd-drafter agent. Defines the canonical sections, when each one is required vs optional, and how to phrase open questions for AI-readable downstream consumption. Loaded by every drafter/updater/validator agent in this plugin.