
Orient in project state before starting work
Use before claiming any fix, deploy, or implementation is complete. Requires showing evidence — not assertions.
Use when executing an implementation plan. Builds in TDD cycles with disciplined commits — one commit per plan step, no unrelated files swept in.
Use when diagnosing bugs, test failures, or unexpected behavior. Requires hypotheses before fixes — no jumping to solutions.
Use before building anything non-trivial — new features, architectural changes, multi-file modifications. Explores intent, requirements, and design before implementation.
Review open issues and PRs across the workspace to decide what needs action
Deploy one or more services end-to-end with health verification
Examine evidence (files, logs, code, output) against user instructions and baseline quality factors. Audit only, no fixes.