product-builder

To convert a vague product idea into a structured PRD, describe your initial concept and the system guides you through five stages, generating a product definition card and consistent Markdown deliverables.

You can start writing technical documentation from any stage of the product workflow, as the system supports flexible entry points and provides prior stage outputs to maintain document continuity and alignment.

To ensure consistency between PRDs and technical plans during product planning, the system enforces stage-by-stage backtracking and consistency rules, verifying that all downstream documents align with prior definitions.

The best way to generate executable task lists from product ideas is to progress through the five-stage documentation workflow, which concludes by producing structured Markdown task lists and project configurations.

You do not need any specific tools or dependencies to produce these Markdown product documents, as the system operates independently without external component requirements to generate the structured deliverables.

If your technical plan no longer aligns with the original PRD, you should use the stage backtracking rules to revise the prior documents, ensuring information consistency and preventing misalignment across the workflow.