Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pocock-engineering
Breaks plans, specs, or PRDs into tracer-bullet vertical-slice issues on the project issue tracker. Useful for converting plans into grabbable implementation tickets.
npx claudepluginhub jackreis/dancer-a2a --plugin pocock-engineeringHow this skill is triggered — by the user, by Claude, or both
Slash command
/pocock-engineering:to-issuesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
Breaks plans, specs, or PRDs into thin vertical-slice issues on the project issue tracker using tracer bullets. Useful for converting high-level work into grabbable implementation tickets.
Decomposes plans, PRDs, or specs into vertical-slice issues as markdown files or GitHub issues. Creates independently demoable end-to-end tasks across layers for parallel implementation.
Decomposes user requests into requirements and TODOs, clarifies ambiguities via questions, then bulk-creates GitHub Issues per task in dependency order with structured bodies, priorities, estimates, and labels.
Share bugs, ideas, or general feedback.
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
Break the plan 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, publish a new issue to the issue tracker. Use the issue body template below. Apply the needs-triage triage label so each issue enters the normal triage flow.
Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
## ParentA reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
Or "None - can start immediately" if no blockers.
Do NOT close or modify any parent issue.