メニュー
Break a PRD into independently-workable, vertical-slice issues as markdown files in issues/. Use to turn a PRD into concrete tasks ordered by dependencies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write, refactor, restructure, edit, or audit technical documentation using the Diátaxis framework (tutorials, how-to guides, reference, explanation). Produces clear, concise, scannable docs and fights the default tendency toward bloated, over-explained AI prose. Use this skill for ANY documentation work — README and CONTRIBUTING files, API/reference docs, runbooks, guides, getting-started pages, conceptual write-ups, docs-site content, or doc reviews — even when the user just says "document this," "write docs for X," "clean up these docs," "explain how this works in the docs," or "what's missing from our documentation." If the deliverable is documentation, reach for this skill rather than writing prose freehand.
Retroactively create Linear tickets and PRs from untracked commits. Use for commits without tickets, "founder mode", or formalizing experimental work.
Create well-structured git commits from analyzed changes. Use when the user asks to commit, save work, or create a commit.
Find architectural friction and propose deep-module refactors as RFC issues. Use to improve architecture, find refactoring opportunities, or deepen shallow modules.
Initialize the AI Engineering Harness (AGENTS.md + thoughts/ structure). Use on /init_harness or when setting up the harness in a repo.
Interview the user relentlessly to stress-test a plan or design. Use to validate design decisions, "drill in", or "ask me questions" before implementation.
| name | prd-to-issues |
| description | Break a PRD into independently-workable, vertical-slice issues as markdown files in issues/. Use to turn a PRD into concrete tasks ordered by dependencies. |
| allowed-tools | Read, Bash, Grep, Glob, Write |
Break a PRD into independently-grabbable issues using vertical slices (tracer bullets), written as local markdown files.
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.
If you have not already explored the codebase, do so to understand the current state of the code.
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.
Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick onesPresent the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
Iterate until the user approves the breakdown.
For each approved slice, write a markdown file in issues/ using the naming pattern issues/NNN-short-title.md (e.g. issues/001-add-user-auth.md).
Number issues starting from the next available number (check what files already exist in issues/).
Create files in dependency order (blockers first) so you can reference real filenames in the "Blocked by" field.
Do NOT use gh issue create or any GitHub CLI commands. Do NOT reference GitHub issue numbers. Use local filenames for all cross-references.
issues/prd.md (or whichever PRD file was used)
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Reference specific sections of the parent PRD rather than duplicating content.
issues/NNN-title.md (if any)Or "None - can start immediately" if no blockers.
Reference by number from the parent PRD:
Do NOT close or modify the parent PRD file.