to-issues

name	to-issues
description	Break a PRD, plan, spec, or parent issue into independently grabbable vertical-slice issues on the configured issue tracker. Use when Codex needs to convert a durable contract into implementation slices with acceptance and regression evidence requirements.

To Issues

Break a parent contract into tracer-bullet vertical slices. Each slice should be small enough for one implementation round and independently acceptable.

Read docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.md, and docs/agents/verification.md if they exist.

Process

1. Fetch The Parent Contract

Resolve the PRD, plan, spec, title, link, local path, or branch reference the user gives. Read the full body and relevant comments.

If there is no durable parent contract, ask whether to create one with to-prd first or create a single agent-ready issue for a small task.

2. Explore The Codebase

Explore enough to understand existing seams, similar vertical paths, tests, and verification commands. Use domain glossary vocabulary and respect relevant ADRs.

Look for prefactors only when they make the first vertical slice simpler or safer. Do not create horizontal module tasks unless the prefactor is independently verifiable.

3. Draft Vertical Slices

Each slice must:

• Deliver a narrow but complete path through the relevant layers.
• Be demoable or verifiable on its own.
• Include acceptance criteria and regression checks.
• Name dependencies clearly.
• Avoid requiring future chat context.

Prefer fewer, clearer slices over a large backlog of tiny implementation chores.

4. Review With The User

Present the proposed breakdown as a numbered list:

• Title
• Outcome
• Blocked by
• User stories or capabilities covered
• Acceptance evidence
• Regression check

Ask the user to confirm granularity and dependencies before creating issues.

5. Publish Slice Issues

Publish approved issues in dependency order so blockers can reference real issue links or paths.

If the tracker supports labels and docs/agents/triage-labels.md defines category/state labels:

• Apply category enhancement.
• Apply state ready-for-agent unless a slice still needs human input.
• Apply state needs-info when missing information prevents safe implementation.

If publishing to local markdown fallback, every slice must start with this header:

Type: slice
Status: ready-for-agent | needs-info
Parent: <PRD path or URL>
Linked PR / Branch / Commit: None

Use this template:

Type: slice
Status: ready-for-agent | needs-info
Parent: <PRD path or URL>
Linked PR / Branch / Commit: None

## Parent

Reference to the parent PRD or issue.

## What to build

A concise description of the end-to-end behavior this slice delivers.

Avoid stale file paths or code snippets unless a prototype snippet encodes a durable decision.

## Capabilities covered

- Capability or user story covered by this slice.

## Acceptance criteria

- [ ] Criterion 1
- [ ] Criterion 2

## Acceptance evidence

- Expected automated tests, manual checks, demo steps, CI checks, or command outputs needed before acceptance.

## Regression checks

- Existing behavior that must still work.
- Test, CI check, or manual checklist that should prove it.

## Blocked by

- Blocking issue link, or `None - can start immediately`.

## Notes for implementation

- Constraints, known risks, or out-of-scope details needed by the implementation agent.

Do not close or modify the parent issue unless the user explicitly asks.

6. Finish

Return the created issue links or local paths, the dependency order, and any slices that still need human clarification.