yeaight7

Coordinate multi-system deployment steps as a review-first runbook with explicit approval before any external write or promotion action.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use before tagging a release or deploying to production to ensure all quality gates have passed.

Deterministic 3-cycle loop for gathering codebase context before acting. Broad search → exact source and tests → target-specific docs and setup. Stop after enough context or report what is still missing.

Verify that all hyperparameters, metrics, and data references are properly logged.

Use before submitting a PR or considering a task done to evaluate the 'blast radius' of your changes.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "no fluff", "be concise", "use less tokens", or similar.

Use when connecting to a managed codebase-context MCP/session service, checking stale maps, or safely using MCP-provided repository context.

Analyze BigQuery usage, identify cost hotspots, repeated failures, and practical optimization opportunities.

Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

Use after fixing a bug to generate a blameless post-mortem summary for human review.