to-issueslisted

# To Issues Break a plan into independently-grabbable issues using vertical slices (tracer bullets). The project issue-tracker owner and label vocabulary live in `docs/agents/issue-tracker.md` and `docs/agents/triage-labels.md`. If either is unresolved, stop and ask for the tracker decision; do not invoke an unrelated setup workflow. ## Process ### 1. Gather context Read `contract.json` and `task_plan.md` from the project root if available. These define scope boundaries, acceptance criteria, and task decomposition. Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments. ### 2. Explore the codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching. ### 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 one layer. Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a 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 COM