to-issues

Generated source view for the actual executable engineering/to-issues skill. The durable routing article is Agent Engineering Skills. Source: skills/engineering/to-issues/SKILL.md

Runtime Source

Field Value
Category engineering
Origin personal
Slug to-issues
Source slug to-issues
Family Agent Engineering Skills
Source skills/engineering/to-issues/SKILL.md

Bundled Resources

No bundled resource files.

Description

Break a PRD, plan, or spec into independently grabbable vertical-slice issues/tickets. Use when the user says "/to-tickets", "turn this into issues", "break this down", "make tickets", "create implementation tasks", or wants AFK/HITL agent-ready work packets. Adapted from mattpocock/skills.

Skill Source

---
name: to-issues
description: Break a PRD, plan, or spec into independently grabbable vertical-slice issues/tickets. Use when the user says "/to-tickets", "turn this into issues", "break this down", "make tickets", "create implementation tasks", or wants AFK/HITL agent-ready work packets. Adapted from mattpocock/skills.
origin: personal
source_slug: to-issues
---

# To Issues

Convert a plan into tracer-bullet issues: thin vertical slices through every relevant
layer, each independently demoable.

## First Move

1. Read the PRD/spec/plan in full.
2. Identify the user-visible capabilities and the proof seam.
3. Search existing issues/plans to avoid duplicates.
4. Choose output:
   - GitHub/Linear only when Kevin explicitly wants writes
   - otherwise `plans/issues/<slug>.md` or repo-local `docs/issues/<slug>.md`

## Slice Rules

- Prefer many thin issues over a few thick ones.
- Avoid horizontal tickets like "write all tests" or "build backend".
- Each issue must include its own proof.
- Mark `AFK` when an agent can execute without human input.
- Mark `HITL` when product, taste, credentialed, or irreversible judgment is needed.

## Issue Template

```markdown
## <Issue Title>

Type: AFK | HITL

Outcome:
Scope:
Out of scope:
Implementation notes:
Proof:
Dependencies:
```

## Related Skills

- `to-prd` for the spec source.
- `tdd` for implementing each slice.
- `agent-iteration-loop` for execution.
- `issue` when creating a GitHub issue is explicitly requested.

Upstream: `github.com/mattpocock/skills/skills/engineering/to-issues/SKILL.md`
at `5d78bd0903420f97c791f834201e550c765699f8`.

Timeline

1 page links here