prd-to-issues
PRD to Issues
Break a PRD into independently-grabbable implementation issues using vertical slices (tracer bullets).
Process
1. Locate the PRD
Ask the user where the PRD lives. It might be a local file path, a GitHub wiki page, a Notion or Confluence doc, or already in the conversation. The user may also provide links to Linear issues/projects or Figma designs for additional context.
Read or fetch the PRD from wherever it lives.
2. Gather external context
If the user provided references to external tools, use the available MCP tools to pull in additional context:
- Linear: The user may provide ticket codes (e.g.,
EO-1234) or URLs. Fetch related issues, project details, or initiative context to understand scope, dependencies, and prior decisions. - Figma: The user may provide a Figma URL. Fetch design context and screenshots to understand UI requirements and component boundaries for each slice.
- Notion: The user may provide page titles or URLs. Search Notion by title if no URL is given. Fetch documents for supplementary specs, notes, or research.
More from evans-sam/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".
15git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git and gh CLI commands before they execute. Use when user wants to prevent destructive git operations, block dangerous GitHub CLI actions (repo delete, pr merge, secret management, API mutations), or add git/gh safety hooks to Claude Code.
14write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then save as a local markdown document. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
13request-refactor-plan
Create a detailed refactor plan with tiny commits via user interview, then save it as a local markdown RFC document. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
13design-an-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
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".
11