prd-to-issues
PRD to Issues
Break a PRD into independent GitHub issues, where each issue is a fully deliverable work item.
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> --comments
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the system.
3. Draft issues
Break the PRD into independent backend and frontend issues:
More from sones3/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".
13write-a-prd
Create a business-focused PRD through user interview, repo exploration, and rigorous clarification, then review it with the user before submitting it as a GitHub issue. Use when the user wants to write a PRD, create a product requirements document, scope a feature, or plan a new capability.
12ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
12start-next-issue
Suggests the next GitHub issue to work on from a PRD breakdown, confirms it with the user, and initiates the pre-implementation discussion.
11discuss-in-french
Ensures that discussions with the user are conducted in French, but all deliverables, documentation, and implementation outputs are written in English.
10start-implementation
Implements a GitHub issue continuously until finished, documents the work and recommendations, commits, and closes the issue. Confirms the issue with the user only if it is not already in context.
9