using-augmentslisted

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific, scoped task, **stop — do not use this skill** and carry on with the task you were handed. Orientation is the dispatcher's job. (Task-specific skills like `debugging` or `test-driven-development` remain yours to use — this guard is only about the router.) </SUBAGENT-STOP> # Using Augments Augments is a toolbox of opt-in engineering skills, organized by the phases of the software development life cycle. This skill is the map — it points you to the right tool; it does no work itself. ## The mental model You are a non-deterministic generator. These skills surround your work with **deterministic gates** — a test, a check, a reproduction. Truth comes from the gate, never from your confidence: **"done" means a check passed, not that you believe it's done.** That one idea is what makes every skill below cohere. The full rationale is in `docs/augments/philosophy.md`. These are tools, not a pipeline: reach for the one that fits the moment; there is no sequence you must walk. The disciplines enforce themselves through their own gates, not through ceremony. ## The map Reach for a skill when its trigger fits. Whenever a request, plan, or design is unclear, `interview-me` grills it into a short alignment brief — in any phase. When a question is faster to build than to argue, `prototyping` answers it with a throwaway spike, then deletes it. To get oriented in code you don't know, `zoom-out` maps the modules