Individual skill
to-issues
Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.
skills/to-issues/SKILL.md
Source commit 6f3983e45b13fcce8ebe1c4523983beb6174326e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 243
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- skills Repository topic
- agentic-workflows Repository topic
- ai-agents Repository topic
- claude-code-skills Repository topic
- open-source Repository topic
- product-ops Repository topic
- personal-corp Repository topic
- agent-skills Repository topic
- codex Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# To Issues
Break a plan into independently-grabbable task files using vertical slices (tracer bullets).
## Process
### 1. Gather context
Work from whatever is already in the conversation context. If `PRD.md` exists in the project folder root, read it in full. If the user points at another spec file, read that instead.
### 2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Task titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
