to-prd

To generate a PRD without stakeholder interviews, this Skill synthesizes existing conversation context and codebase understanding into a structured product requirement document. It leverages current repository knowledge and domain vocabulary to produce actionable requirements.

Drafting user stories that respect architecture decisions requires applying existing ADR constraints and repo-specific vocabulary. This Skill structures expected implementation work into major modules with testable interfaces while capturing key architecture decisions.

Yes, you can automatically publish a product requirement document to an issue tracker using this Skill. It applies the ready-for-agent triage label during publication, ensuring the generated PRD is properly triaged for team action.

Generating a PRD from codebase context requires adherence to a provided PRD template. The Skill enforces this structure to ensure explicit implementation and testing decisions are documented alongside extensive user stories.

A key limitation when converting conversation context into product planning documents is that it applies to scenarios where requirements must be drafted without interviewing users. It relies entirely on current codebase understanding rather than direct stakeholder feedback.