Loop Issues

Break a PRD into issues an unattended agent can land. The slicing follows tracer-bullet vertical slices (after mattpocock's to-issues); the addition that makes the loop work is the criteria gate: no issue is published until every acceptance criterion names a runnable check. Decisions are drained here, while the human is in the room — work-issue never asks.

Requires .loop/config.md — if missing, stop and point the user to /loop-setup.

Process

1. Gather context

Work from the PRD or plan already in conversation. If the user passes a file path or issue reference, read/fetch it in full (body and comments).

2. Explore the codebase

If not already explored: check .codemap/MAP.md first, else Glob/Grep. Two goals — use the project's existing vocabulary in issue titles/bodies, and learn what check infrastructure exists (test runner, typecheck, lint, e2e). The gate in step 4 depends on knowing this.

3. Draft vertical slices

Each issue is a thin tracer bullet through all layers (schema, API, UI, tests) — never a horizontal slice of one layer.