feature-agentslisted

# Feature agents A delegation layer for a feature: five subagents, each with the tools its job needs and nothing else. Read `.claude/project-profile.md` first. If it is missing, stop and point at `/project-setup`. These agents plan against your conventions, and a plan built on a guessed stack is a plan you will throw away. ## When to use this instead of `/ship` `ship` runs the same delivery arc in one context, and for most changes that is the right call: less overhead, less handoff, one continuous train of thought. Reach for this one when the change is big enough that **phase discipline stops holding on its own**. In a single context the pull toward writing code while still working out the requirements is strong, and what comes out is a plan reverse engineered from a half finished implementation. Delegation makes that structurally impossible. The spec writer has `Read, Grep, Glob, AskUserQuestion` and cannot write a file. The planner cannot run bash. The QA agent cannot push. The boundary is not a promise in a prompt, it is the tool list. Rough line: three or more files, a schema change, an integration, or anything where being wrong is expensive. Below that, `ship`. ## The five | Agent | Gets | Cannot | |---|---|---| | `feature-spec` | Read, Grep, Glob, AskUserQuestion | write anything, propose architecture | | `feature-planner` | Read, Grep, Glob | write, run commands | | `feature-tester` | Read, Write, Edit, Bash, Grep, Glob | set up test infra that did not exist |