to-prd

To generate a PRD from conversation context, the Skill synthesizes existing domain language, architectural decisions, and priming context into a structured requirements document. It identifies context gaps to explore and produces an artifact covering the problem, solution, user stories, decisions, and handoff notes.

A requirements doc for implementation handoff should include the problem statement, proposed solution, user stories, architectural decisions, and handoff notes. The Skill structures these sections automatically to ensure the feature spec is complete and traceable for downstream planning.

Yes, you can save a synthesized PRD directly to repository docs. The Skill supports file-based emission to the docs/prd directory, ensuring the durable artifact is saved as a markdown file for implementation planning and reference.

Yes, the PRD synthesis tool supports creating GitHub issues. When requested via a flag, it takes the synthesized requirements doc and generates a GitHub issue to facilitate implementation planning and traceability directly within your repository.

The best way to synthesize domain language into a PRD is to reuse priming context from conversations and identify gaps to explore. This approach ensures the requirements doc accurately captures architectural decisions and domain terminology before implementation planning begins.

You should generate a requirements doc before starting implementation work whenever a feature needs traceable decisions and user stories. Synthesizing a PRD beforehand ensures the artifact is complete, captures architectural context, and provides durable handoff notes for the team.