Break the PRD into a set of executable, well-organized development issues so the agent does not improvise beyond the scope of the specification.
Process
1. Receive the PRD
The PRD is located in the issue tracker, and this skill can retrieve it from there. It is a structured document that defines the product or feature to be built.
2. Break into Issues
Break the PRD into independent, ordered, clearly scoped issues. Each issue:
- Should point to the corresponding section in the PRD
- The name should use the imperative mood ("Add...", "Create...", "Implement...")
- The scope should be specific enough to be independently evaluated, implemented, and tested
Every sentence in the PRD containing "must", "should not", and every acceptance criterion should be reflected in at least one issue. No sentence is decorative.
3. Ordering
Order by dependencies:
- Infrastructure and type definitions come first
- Core logic comes on top of infrastructure
- User interface comes after core logic
- Integration and testing run throughout and stay closely adjacent to the corresponding work
4. Publish
Write all issues to the issue tracker. The body of each issue should contain:
- Relevant context from the PRD
- Specific acceptance criteria
- Links to the PRD and to any blocked issue
Add a summary comment to the PRD issue listing all created issues and their dependencies.