product-prd-drafter

Generating a PRD from meeting notes involves extracting feature descriptions, validating them against a product registry, and loading project context from memory to produce a 2-3 page structured document. The process automatically structures your rough input into defined sections like Problem Statement and User Stories.

Structuring product requirements from Slack threads uses memory context to capture project goals, user feedback, and constraints, transforming scattered discussions into a coherent plan. This approach ensures functional and non-functional requirements are clearly defined from chaotic communication.

Yes, you can create Asana tasks directly from a generated product requirements document through built-in Asana integration. This allows you to reference existing tasks, collect feedback, and create epics or milestones to track project progress immediately after drafting.

PRD generation works with existing roadmaps by checking feature descriptions against a current product registry to align with scope. It retrieves project context from memory, including audience and constraints, ensuring the output matches your established product goals.

Completed PRDs are saved to the product vault at ~/.second-brain/vault/product/prds/YYYY-MM-DD-<feature-slug>.md and logged to the daily activity log. This standardizes file naming using feature slugs and ensures all document creation is tracked.

An automatically drafted product requirements document includes structured sections like Problem Statement, Goals, User Stories, Functional and Non-Functional Requirements, Risks, and Open Questions. These sections are populated by analyzing rough notes and loading relevant project context.