to-issues

Files (1)

• SKILL.md

SKILL.md (first lines)

# To Issues

Break a plan into issues that can be picked up independently 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.

## Process

### 1. Gather context

Work from what's already in the conversation context. If the user passes an issue reference (number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.

### 2. Explore the code (optional)

If you haven't explored the code yet, do so to understand the current state. Issue titles and descriptions must use the project's domain glossary vocabulary and respect ADRs in the affected area.

### 3. Draft vertical slices

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 a single layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, like an architectural decision or design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

<vertical-slice-rules>
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
- A completed slice is demonstrable or verifiable on its own
- Prefer many thin slices over a few thick ones
</vertical-slice-rules>

### 4. Ask the user

Present the proposed breakdown as a numbered list. For each slice, show:

- **Title**: short, descriptive name
- **Type**: HITL / AFK
- **Blocked by**: which other slices (if any) must be completed first
- **User stories covered**: which user stories this slice resolves (if the source material has them)

Ask the user:

- Does the granularity seem right? (too coarse / too fine)
- Are the dependency relationships correct?
- Should any slice be merged or split further?
- Are the right slices marked HITL and AFK?

Iterate until the user approves the breakdown.

### 5. Publish issues to the tracker

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 identifiers in the "Blocked by" field.

<issue-template>
## Source

A reference to the source issue in the tracker (if the source is an existing issue, otherwise omit this section).

## What to Build

A concise description of this vertical slice. Describe the end-to-end behavior, not the layer-by-layer implementation.

Avoid specific file paths or code snippets — they become outdated quickly. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose (state machine, reducer, schema, type format), include it here and briefly note that it came from a prototype. Trim to only the decision-dense parts.

## Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

## Blocked By

- A reference to the blocking ticket (if any)

Or "None — can start immediately" if there are no blockers.

</issue-template>

DO NOT close or modify any source issue.

From hcb2019/claude-code-skills, MIT.

More from hcb2019/claude-code-skills