to-prd

To convert conversation context into a structured PRD, this Skill synthesizes existing context and codebase understanding into comprehensive user stories, implementation decisions, and testing plans without requiring additional interviews.

Generating user stories and module design from a codebase requires exploring current repo terminology and ADRs. This Skill proposes major modules and deep-module candidates grounded in your actual code structure.

Yes, you can publish a product requirements document to your issue tracker automatically. This Skill formats the PRD using the required template and publishes it directly with the ready-for-agent triage label.

The best way to formalize product requirements without new interviews is leveraging existing conversation context. This Skill builds the PRD directly from what is already known, skipping additional questioning.

Generating a PRD from conversation context fully respects existing architecture decision records. The Skill mandates repo exploration to ensure implementation decisions align with current ADRs and repo terminology.

A limitation when synthesizing a PRD from current conversation context is the dependency on pre-existing knowledge. The Skill builds exclusively from active context and codebase exploration without asking clarifying questions to fill gaps.