メニュー
Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers — "engineer plugin -> consistency-check skill", "check consistency", "validate the artifacts", "are the specs and ACs in sync", "audit this feature".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 | consistency-check |
| description | Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers — "engineer plugin -> consistency-check skill", "check consistency", "validate the artifacts", "are the specs and ACs in sync", "audit this feature". |
Cross-artifact validation for DAE — the methodology's take on Speckit's /analyze. Read-only: reports inconsistencies and suggests fixes; never mutates. Any agent may run it (mechanical validation, not judgment-heavy verification). checkpoint: null.
Before major pipeline transitions and as a CI gate.
engineer plugin -> consistency-check skill <slug> — one feature's artifactsengineer plugin -> consistency-check skill --project — project-wide invariantsNot for: fixing inconsistencies (run the suggested fix skill); within-one-artifact ambiguity (clarify); code risk (crap-analyzer).
${PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md). Feature scope: load every artifact in features/NNN-<slug>/ + CHARTER.md. Project scope: load CHARTER.md + every feature.md frontmatter. For identifier lookups (does symbol X actually exist in the code?), prefer LSP find-definitions / workspace-symbols when an LSP MCP capability is available; fall back to grep + Read otherwise. See ${PLUGIN_ROOT}/references/code-lookup.md.| Check | Severity |
|---|---|
feature.md slug matches folder name | error |
feature.md mandatory frontmatter present; status: ready ⇒ autonomy_level set | error |
acs.md AC IDs unique + sequential; ac_count matches actual | error |
acs.md ACs in domain language (implementation-leakage heuristic) | warning |
acs.md ACs cover the feature.md outcome | warning |
relevant_adrs reference ADRs that exist | error |
spec.md and .build/spec.json agree | error |
plan.md Charter Check: every ⚠️ deviation has a matching amendment | error |
Validation method honored? — if feature.md declares a non-default validation_method, plan.md's Test strategy section must reference it (canary phase, dashboard names, rollback trigger, etc. as relevant) | warning |
Verification handoffs: agent_id ≠ implementer's (Principle 7) | error |
tracker_ref resolves on the configured tracker | warning |
Handoff completeness: no checkpoint marked done in progress.md lacks a complete handoff | error |
parent_feature set ⇒ parent exists and lists this in child_features | error |
The handoff-completeness check is the after-the-fact sweep for handoff-as-gate
(Foundation Design Section 5): run ${PLUGIN_ROOT}/scripts/dae_handoff.py <feature-dir> — it flags any checkpoint marked done with a missing,
interrupted, or unmet-exit_criteria handoff.
| Check | Severity |
|---|---|
CHARTER.md section 5 roles == manifest.team.default_roles | error |
manifest.yml schema valid; enum values legal | error |
| Feature folder numbering monotonic; no reuse | error |
| ADR not referenced by any feature in N months (N from manifest, default 6) | warning |
Every features/*/ has a non-empty feature.md | warning |
team.default_roles includes verifier when independence enforced | error |
Emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts: []. Feature scope → handoff in that feature's handoffs/; --project scope → handoff in .engineer/handoffs/. Any errors → human_action_needed: yes. recommended_next: resolve via clarify / feature-edit / plan, then re-run.
tracker_ref resolution