Use before saying work is complete, fixed, passing, approved, ready, or safe to hand off.
Define behavior and architecture before edits when a change is user-visible, risky, or not yet bounded.
Compact engineering rules for implementation and review when the repository has no stronger local guidance.
Implement an accepted or clear change with minimal diff, direct verification, and no compatibility wrappers unless required by the contract.
Read-only investigation for unclear requests, bug reports, failures, architecture questions, or project health checks.
Install, repair, package, or verify the SpecPowers plugin and its generated payloads.
Review a diff, commit range, worktree, or implementation plan for correctness, risk, maintainability, and evidence gaps.
Use at session start or before deciding how SpecPowers should shape a task. Routes work into the small core workflow set.