Help us improve
Share bugs, ideas, or general feedback.
From craft-workspace-webconsulting-skills
Converts plans, specs, or PRDs into independently-grabbable issues using tracer-bullet vertical slices. Useful for breaking down work into actionable implementation tickets.
npx claudepluginhub dirnbauer/webconsulting-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/craft-workspace-webconsulting-skills: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 independently-grabbable issues using tracer-bullet vertical slices. Useful when converting a plan into implementation tickets.
Breaks down plans, specs, or PRDs into independent issues using vertical slices (tracer bullets). Useful for converting plans into implementation tickets or breaking down work into granular, demo-able tasks.
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. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
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.
Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
Or "None - can start immediately" if no blockers.
Do NOT close or modify any parent issue.
This skill is based on the excellent work by Matt Pocock.
Original repository: https://github.com/mattpocock/skills
Copyright (c) Matt Pocock - Agent skills for real engineering workflows (MIT License)
Special thanks to Matt Pocock for their generous open-source contributions, which helped shape this skill collection. Adapted by webconsulting.at for this skill collection