Use when reviewing code changes for quality, security, performance, or maintainability issues and identifying simplification opportunities in a single token-efficient pass
Use when the user invokes /inspirer or asks to brainstorm creatively, think outside the box, explore unconventional approaches, break out of stagnation, or generate…
Use when the user invokes /evolve-loop or asks to run autonomous improvement cycles, self-evolving development, compound discovery, or multi-cycle code improvement with research,…
Security-focused code review that emits a numeric composite score (0.0–1.0) suitable for the evolve-loop Builder self-review convergence loop
Use when the user invokes /verify-release or asks to check whether a release has propagated, whether the marketplace is up to date, or whether installed plugins reflect the latest…
Use after evolve-build has produced build-report.md. Validates the build via four parallel sub-auditors (eval-replay, lint, regression, build-quality) and produces ALL-PASS…
Use after evolve-ship completes. Three sub-reflectors (instinct, gene, failure) run in parallel to extract lessons, update gene pool, and analyze any failures.
Use when scout-report.md exists and TDD/Build hasn't started yet. Runs four lenses (CEO, Eng, Design, Security) in parallel on the task list and produces a verdict (PROCEED,…
Use after evolve-audit returns Verdict PASS. Atomic git commit + tag + ledger update. Single-writer; cannot fan-out.
Use when starting a new evolve-loop cycle and the cycle goal is ambiguous or only described as a one-line objective.
Use after evolve-tdd has written RED tests and the contract is in team-context.md. Implements the minimum code to turn RED tests GREEN.
Use when the plan-review verdict is PROCEED (or plan-review is disabled) and code has not yet been written. Writes RED tests first, defining the contract Builder must satisfy.
Pre-Scout intent capture phase. Structures vague user goals into intent.md before any subagent budget is spent. Opt-in via EVOLVE_REQUIRE_INTENT=1.