plan-to-tickets

# Plan To Tickets Turn a large plan into small, independently executable tickets. Use this before handing a broad plan to agents, before long autonomous work, or when the user asks for tickets/issues/slices. ## Output Location If no issue tracker is explicitly selected, write local tickets under: `<project>/.agent/tickets/<YYYY-MM-DD>-<slug>/` Each ticket is one Markdown file: `TICKET-001-short-slug.md` ## Required Ticket Shape Each ticket must include these headings exactly: - `## Status` - `## Parent` - `## What To Build` - `## Acceptance Criteria` - `## Verification` - `## Blocked By` - `## Notes` `## Status` must contain `ready-for-agent` only when all acceptance criteria and verification steps are concrete. `## Acceptance Criteria` must contain checklist items (`- [ ] ...`). `## Verification` must contain at least one command, script, test, artifact check, or explicit manual-review gate. ## Slicing Rules - Prefer vertical tracer bullets: a narrow complete path through the required layers, not "all backend" then "all UI" then "all tests". - A ticket must be independently verifiable. - Put prefactoring first only when it makes a later slice smaller or safer. - Keep dependencies explicit in `## Blocked By`; write `None` when it can start immediately. - Do not include stale-prone file paths unless the path is already a stable contract or current codebase evidence. - Do not publish external tracker issues unless the user asked for that tracker. ## Workflow 1. ...