to-issues
Installation
SKILL.md
To Issues
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
Issues live in issues/ as markdown files. issues/BACKLOG.md is the ordered queue: dependencies, type (AFK/HITL), and status. There is no external issue tracker — issues/ is the tracker, and BACKLOG.md is its entry point.
Artifacts
Paths are defaults — if the repo already names them differently, its names win.
| Role | Default path |
|---|---|
| Live queue | issues/BACKLOG.md — todo and in progress only |
| Completed queue | issues/ARCHIVE.md — rows move here on acceptance |
| Issue files | issues/NNN-kebab-case-title.md |
| Domain glossary | CONTEXT.md |
| Product spec | docs/REQUIREMENTS-AND-NOTES.md |
Read the glossary for domain vocabulary before drafting. If the glossary or spec is missing, say so once and draft from the conversation instead — do not author them here and do not keep searching. They are grill-me output, and a project can run on issues alone.