casa-rs

Use when moving work from backlog to ready. Produces a single-issue or wave-lead issue with outcome, acceptance checks, stop conditions, and a short shaping interview when the request is still sparse.

Use on a schedule to audit a project's planning board for state/metadata consistency. Flags items that were moved into stages like Ready, Review, or Done without the supporting detail or evidence those stages imply.

Use for final PR review and housekeeping. If serious issues are found, leave detailed PR comments and stop. If the PR is ready, merge to main, close linked issues, prune the branch, delete the temporary worktree, and report the result.

Use to implement an approved wave on a branch. Keeps work inside the approved boundary without silently descoping accepted work, runs preflight and refactor passes only where bounded by the wave, commits and pushes the wave branch, and creates or updates the PR.

Use when optimizing casa-rs imaging performance or correctness/performance parity against CASA, especially for MFS, cube, mosaic, W/AW projection, MT-MFS, multi-worker CPU, Metal/GPU, benchmark bundles, or large MeasurementSet streaming behavior.

Use for a dedicated architecture pass on a branch or diff. Checks boundaries, dependencies, public contracts, and entropy risk against the scaled-layer docs.

Use when `verify`, release, or scheduled CI checks fail repeatedly. Produces a diagnosis, a likely root cause, and the smallest safe next step.

Use after a scaled-layer wave or at architecture checkpoints. Compares code and tests with ARCHITECTURE.md, TESTING.md, ADRs, and generated artifacts.

Use when a brownfield repo needs a focused wave to repair the development loop, tighten verification, or reduce local entropy before feature work continues.

Use for a skeptical review of the tests after implementation. Looks for shallow coverage, over-mocking, and ways the implementation could still be wrong while tests pass.

Read-only review agent for casa-rs. Analyzes interop test coverage, performance tests, demo parity, rustdoc documentation, and crate separation against quality criteria. Use when reviewing a wave, branch, or the full codebase.