메뉴
Break a PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when the user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Convert a project complexity diagnosis into a practical intervention plan. Use after project-complexity-mapper, especially when the user provides a TOE findings table, quadrant chart, hotspot quadrants, management-fit table, or handoff table and wants actions, interventions, sequencing, owners, or next steps.
Diagnose project complexity from a rough project description using the DelftX TOE framework and detail/dynamic complexity model. Use when the user wants to map, score, visualize, or understand project complexity; create a TOE matrix; generate a quadrant chart; or choose a fit-for-purpose management approach.
Perform a language-agnostic first-pass code review covering logic errors, bad practices, operation ordering, magic strings, pattern improvements, strict type checking, and SQL injection. Use when asked to review code, audit a file, or check a diff. Accepts a single file, a diff with multiple hunks, or can explore the repo when needed to resolve external references. If no input is provided, ask the user to share a file or diff before proceeding.
Run a cross-cutting audit across all code produced for a feature. Use when a feature is complete, all PRs are merged, and the user wants a final review for security issues, logic errors, consistency, and best practices.
Break an issue file into concrete, ordered, AI-executable tasks. Use when the user wants to implement an issue, start work on a ticket, or break down an issue into smaller steps.
Create a PRD through user interview, codebase exploration, and module design, then save it as a file. Use when the user wants to write a PRD, create a product requirements document, or plan a new feature.
| name | prd-to-issues |
| description | Break a PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when the user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items. |
Break a PRD into independently-grabbable issues using vertical slices (tracer bullets).
Ask the user for the PRD file. Ask the user for the format, name, and location where the issue list should be saved.
If you have not already explored the codebase, do so to understand the current state of the implementation. Focus on the modules identified in the PRD's Module Design section.
Break the PRD into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end — schema, logic, API, UI, and tests — not a horizontal slice of a single layer.
Slices may be HITL or AFK:
Prefer AFK over HITL wherever possible.
- Each slice delivers a narrow but complete path through every relevant layer - A completed slice is demoable or independently verifiable - Prefer many thin slices over few thick ones - Slices that cannot be verified on their own are too coarsePresent the proposed breakdown as a numbered list. For each slice show:
Ask the user:
Flag any slice that addresses more than 2–3 user stories or would likely take more than half a day — it is probably too coarse and should be split.
Iterate until the user approves the breakdown.
Write all approved issues to the file the user specified. Number issues sequentially and use those numbers for cross-references within the file.
Use the issue template below for each issue. Write issues in dependency order (blockers first).
Do NOT modify the PRD file.
## Issue : Type: HITL / AFK Blocked by: Issue / None — can start immediately<prd-filename>
A concise description of this vertical slice. Describe the end-to-end behaviour, not layer-by-layer implementation steps. Reference sections of the PRD rather than duplicating content.
Exactly how a developer (or the AI implementing this) confirms the slice is complete:
