to-issues

To Issues

Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets). Each issue cuts end-to-end through every layer, not horizontally through one layer.

Workflow

1. Gather context

Work from whatever is already in the conversation. If the user passes a GitHub issue number or URL, fetch it with gh issue view <number> (with comments). If a NOUS plan file exists at .nous/plans/<domain>-plan.md or docs/nous/plans/<domain>-plan.md, read it.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand current state.

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 (schema, API, UI, tests), NOT a horizontal slice of one layer.

Slices may be HITL or AFK:

• HITL — Human In The Loop. Requires architectural decision, design review, or judgment call.
• AFK — Away From Keyboard. 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 demoable or verifiable on its own.
• Prefer many thin slices over few thick ones. </vertical-slice-rules>

4. Quiz 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 complete first
• User stories covered — which user stories this addresses (if the source has them)

Ask:

• Does the granularity feel right? (too coarse / too fine)
• Are the dependency relationships correct?
• Should any slices be merged or split further?
• Are the correct slices marked HITL vs AFK?

Iterate until the user approves the breakdown.

5. Create the GitHub issues

For each approved slice, create a GitHub issue with gh issue create. Use the body template below.

Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.

Issue template

## Parent

#<parent-issue-number> (omit this section if there is no parent)

## What to build

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

## Acceptance criteria

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

## Blocked by

- Blocked by #<issue-number> (if any)

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

Rules

• Do NOT close or modify the parent issue.
• No file paths or line numbers in the issue body — describe behaviors and contracts.
• Use the project's domain language (UBIQUITOUS_LANGUAGE.md / CONTEXT.md if present).
• After filing, print all issue URLs with blocking relationships summarized.