roll-buildlisted

# Roll Build (Universal Delivery) > Follows the Architecture Constraints, Development Discipline, and Engineering Common Sense defined in the project AGENTS.md. One entry point. Any input. Full delivery. ## Trigger **Input detection:** ``` Input received ├── matches "US-[A-Z]+-[0-9]+" → Story mode: read BACKLOG → TCR workflow ├── matches "FIX-[A-Z]+-[0-9]+" → redirect to $roll-fix ├── matches "IDEA-[0-9]+" → redirect to $roll-idea (lookup and expand) └── anything else → Fly mode: clarify → design → execute ``` **Story mode** — use when: - The user provides a `US-XXX` identifier - An existing backlog Story needs to be executed **Fly mode** — use when: - The user has a vague one-sentence request - No `US-XXX` exists yet; planning and execution are both needed - No input at all — ask the user what they want to build **Redirect to `$roll-fix`** when: - Input matches `FIX-XXX` or `BUG-XXX` pattern Do not use for: - Pure analysis or research with no code changes (use `$roll-design`) - Single-line hotfix with no planning needed (use `$roll-fix`) ## Core Philosophy 1. **Clarity over assumptions** — When scope is unclear, clarify first 2. **Just enough planning** — Plan to the level the uncertainty demands 3. **TCR rhythm** — Test-first, micro-steps, auto-commit on green, auto-revert on red 4. **Push to GitHub** — Complete implementation, commit, and push; code is on remote 5. **Stay reversible** — Every micro-step leaves the repo in a clean, gr