Use this when the user wants to implement a new feature, endpoint, module, or behavior change in an existing codebase. Plans the change, confirms placement and business rules, then writes code in one serialized lane with tests. Not for bug fixes or cleanup.
Use this when the user wants a strong Codex, Cursor, Claude Code, Windsurf, phase, audit, harness, bug-fix, production-readiness, or handoff prompt. Use the readiness gate before large prompts.
Use this for git safety, public repo cleanliness, forbidden tracked files, generated artifacts, release readiness, and safe staging. Do not use for feature work or broad code cleanup.
Use this when the user reports a bug or failed behavior. Verify first, classify bug vs misunderstanding vs expected behavior vs feature request, then propose a minimal fix before editing.
Use this only for high-risk cleanup or refactoring. Requires warning, clean git state, recovery branch/tag, audit first, batch plan, one batch at a time, tests after each batch, and confirmation before continuing.
Use this for session handoffs, final reports, continuity summaries, next-session prompts, and milestone delivery notes. Do not use for code changes or bug fixing.
Use this for full audits, scoped audits, UX/performance audits, and production-readiness checks. This team tests and reports only; it does not fix by default.
Use this when the user wants to implement a new feature, endpoint, module, or behavior change in an existing codebase. Plans the change, confirms placement and business rules, then writes code in one serialized lane with tests. Not for bug fixes or cleanup.