roll-fixlisted

# Fix Ship (TCR Edition) > Follows the Architecture Constraints, Development Discipline, and Engineering Common Sense defined in the project AGENTS.md. Execute a single `FIX-XXX` / `BUG-XXX`, suitable for small-scope fixes or hotfixes. ## Trigger Use when: - There is a clearly defined `FIX-XXX` or `BUG-XXX` - It is a single issue, single hotfix, or single small enhancement - It does not need to be split into multiple Stories / Actions to deliver **Workflow:** 1. Read .roll/backlog.md index → Find FIX/BUG row → Follow link to `.roll/features/<feature>.md` 2. Single Action (no splitting) 3. Execute via TCR workflow 4. Write back: update .roll/backlog.md status column + update FIX section in Feature file Do not use for: - Multi-step feature development - Large changes spanning multiple subsystems - Requirements that need planning and splitting first - Roadmap work that should be tracked as Stories If the issue expands beyond a single bounded change, switch to `roll-build`. ## Project Context Rule Before creating any file or directory: 1. **Read existing project structure** — check for `package.json`, `go.mod`, `Cargo.toml`, `pyproject.toml`, existing `src/`, `api/`, `cmd/` directories 2. **Infer conventions from evidence** — don't assume a project type; observe what already exists 3. **Follow what already exists** — introduce new patterns only when the current structure has no precedent > `roll init` no longer asks for project type. Skills are responsible for readin