prd-to-issues
PRD to Issues
Break a PRD into independently-grabbable issues using vertical slices (tracer bullets), written as local markdown files.
Process
1. Locate the PRD
Ask the user for the PRD file path (e.g. issues/prd.md).
If the PRD is not already in your context window, read it from the file.
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/ai-engineer-workshop-2026-project
write-a-prd
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
19improve-codebase-architecture
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
17grill-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".
16tdd
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.
14better-sqlite3-rebuild
Use when seeing errors about better-sqlite3 native module, NODE_MODULE_VERSION mismatch, "was compiled against a different Node.js version", or similar native binding errors.
7