Menu
Break a plan, spec, or PRD into independently-committable issues using vertical slices. Use when converting a plan into trackable work items.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Find deepening opportunities in the codebase — refactors that reduce coupling, simplify interfaces, and improve AI-navigability. Use when improving architecture, finding refactoring opportunities, or making a codebase easier to work with.
Use before any feature work — explores intent, asks clarifying questions one at a time, produces a design doc. Invoke before writing any code or plan.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "less tokens", or invokes /caveman.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → review. Use when something is broken, throwing errors, or regressing.
Interview the user or a design relentlessly until reaching shared understanding. Walk down every branch of the decision tree, resolving dependencies one by one. Use when stress-testing a plan, clarifying design, or the user says "grill me".
Use at the start of any session to understand which skill to invoke. Maps the full workflow — feature development, bug fixing, architecture, and utilities — for a C++ game server project with SVN.
| name | to-issues |
| description | Break a plan, spec, or PRD into independently-committable issues using vertical slices. Use when converting a plan into trackable work items. |
Break a plan into independently-committable issues using vertical slices (tracer bullets).
Work from the plan or PRD already in context. If an issue reference was provided, fetch it from the issue tracker.
Understand the current code state. Issue titles and descriptions should use the project's domain vocabulary (Manager names, struct names, module names).
Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL layers end-to-end — sdp definition + Logic + CmdParser + response — NOT a horizontal slice of one layer.
Slices may be HITL (requires human interaction: design decision, deployment approval) or AFK (can be implemented and committed to SVN without human interaction). Prefer AFK over HITL where possible.
Vertical slice rules:
Present the proposed breakdown as a numbered list. For each slice:
Ask the user:
Iterate until the user approves.
For each approved slice, create an issue. Use the template below. Publish in dependency order (blockers first).
## Parent
Reference to the parent plan or PRD (if applicable).
## What to Build
A concise description of this vertical slice. Describe the end-to-end behavior (sdp → logic → response), not layer-by-layer steps.
Avoid specific file paths or code — they go stale. Exception: if a prototype produced a key data structure or state machine snippet, inline it here.
## Acceptance Criteria
- [ ] CmdId enum value added and unique
- [ ] CS/SC structs defined in sdp
- [ ] Logic implemented in Manager
- [ ] CmdParser handler implemented and registered in CmdRegister.h
- [ ] ./qmake.sh compiles clean
- [ ] Code review passed (no Critical/Important issues)
- [ ] svn commit done
## Blocked By
- [issue reference] OR "None — can start immediately"