Menu
Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze changed code for complex, under-tested functions using CRAP scoring; produce ranked refactor and test recommendations.
Validate strict DAE quality gates after implementation-affecting changes, require machine-readable evidence, and write the quality-gate summary before completion or release.
This skill should be used when the user asks to "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving mutants", "verify test effectiveness with mutations", "run stryker", "run mutmut", "run pitest", "set up mutation testing", "how good are my tests", "are my tests catching bugs", or mentions mutation testing, mutation score, or mutant survival in the context of testing. It adds a third validation layer to the ATDD workflow: after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies that tests actually catch bugs.
This skill should be used when the user asks to "build a feature", "implement a feature", "add functionality", "start development", "write acceptance tests", "write specs", "use ATDD", "use TDD with acceptance tests", or begins any feature implementation work. Also available as the atdd plugin's main skill. Enforces the Acceptance Test Driven Development workflow: write Given/When/Then specs before code, generate a project-specific test pipeline, and maintain two test streams.
This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a six-phase ATDD workflow โ spec writing, spec review, pipeline generation, implementation, refine, verify & harden โ spawning a fresh agent per phase so no agent erodes across a long-running feature.
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
| name | spec-check |
| description | Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path. |
Audit acceptance test specifications for implementation leakage. Use the deterministic checker first:
python3 ${PLUGIN_ROOT}/../engineer/scripts/dae_spec_leak.py <path-or-root>
If the deterministic checker is unavailable from the installed plugin layout,
use the project custom agent spec-guardian when available; otherwise run the
same read-only review directly.
If a file path is provided, review only that file. If no path is provided,
review features/*/spec.md and legacy specs/*.txt.
Report concrete file/line findings, the leaked implementation term, and a domain-language rewrite. Do not edit specs unless the user explicitly asks.