メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 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.
| name | wdad-planning-board-audit |
| description | 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. |
Keep the planning board honest when humans can move items manually.
Read-only/planning mode. Do not move cards or edit issues unless separately instructed.
README.md or AGENTS.mdBacklog -> Ready: outcome, non-goals, acceptance checks, stop conditions, and verification path exist.Ready -> In Progress: the wave is shaped enough to start and has no unresolved blocking decision recorded.In Progress -> Review: the PR or equivalent review artifact exists, the current verify result is recorded, a bounded refactor pass is recorded or marked not applicable for a no-code wave, and no approved outcome, included issue, or acceptance check was deferred or descoped without explicit user signoff recorded in the issue or PR.Review -> Done: closeout is updated, review evidence exists, follow-up issues are created where needed, and any approved-scope deferral records explicit user signoff.Parked: the deferral reason is clear enough that the item can be revisited later; parking approved scope is invalid without explicit user signoff.