to-prd

Invoke the to-prd skill after discussing the feature. It synthesizes the existing conversation context and codebase exploration into a structured PRD with problem statement, user stories, and implementation decisions, without asking you additional interview questions.

The PRD template includes Problem Statement, Solution, an extensive numbered list of User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes. Code snippets are only included when they encode decisions more precisely than prose.

Yes, after writing the PRD it publishes the document to the project issue tracker and applies the ready-for-agent triage label. The tracker and label vocabulary must be configured first via the setup command.

A deep module encapsulates significant functionality behind a simple, testable interface that rarely changes. The skill actively looks for opportunities to extract deep modules during planning and confirms the module list with the user before writing the PRD.

Avoid it when the feature scope has not been discussed yet, since the skill does not interview the user and only synthesizes existing context. It is also unsuitable when no issue tracker or triage label vocabulary has been configured.