yeaight7

Run large codebase migrations in reviewable local batches with codemods, checkpoints, and verification. Use when a wide refactor is too risky to ship as one monolithic change.

Record why an architectural choice was made to prevent agents or humans from unintentionally reverting it.

Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when reproducing, isolating, and fixing a bug with the smallest safe change.

Use when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test metadata.

Use when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test metadata.

Ensure the project README provides immediate, exact commands for setup, testing, and deployment to help agents and humans bootstrap quickly.

Turn vague implementation requests into testable requirements before coding.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies