prd-to-issues
Convert product requirements into independently-deliverable GitHub issues using vertical-slice architecture.
- Fetches PRD content from GitHub, analyzes the codebase context, and breaks requirements into thin vertical slices that span all integration layers end-to-end
- Distinguishes between HITL (human-in-the-loop, requiring decisions) and AFK (autonomous, mergeable without review) slices, preferring AFK where possible
- Presents proposed breakdown for user feedback on granularity, dependencies, and slice categorization before creating issues
- Generates GitHub issues in dependency order with acceptance criteria, blocker references, and traceability back to parent PRD user stories
PRD to Issues
Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets).
Process
1. Locate the PRD
Ask the user for the PRD GitHub issue number (or URL).
If the PRD is not already in your context window, fetch it with gh issue view <number> (with comments).
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code.
3. Draft vertical slices
Break the PRD into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
More from mattpocock/skills
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
124.2Kimprove-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
91.2Ktdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
89.7Kgrill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
72.8Kto-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
72.6Kto-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
69.7K