メニュー
Use when a single DAE artifact has ambiguities to resolve. Triggers — "engineer plugin -> clarify skill", "clarify this spec", "resolve ambiguities", "this is vague — tighten it".
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 | clarify |
| description | Use when a single DAE artifact has ambiguities to resolve. Triggers — "engineer plugin -> clarify skill", "clarify this spec", "resolve ambiguities", "this is vague — tighten it". |
Resolve ambiguities in one DAE artifact through an iterative interview. A cross-cutting quality gate — runs on any artifact at any pipeline stage.
The clarify pattern is also embedded inside artifact-producing skills for their own in-flight ambiguities; this standalone skill is for ad-hoc cleanup after the fact.
On any one of: feature.md, acs.md, spec.md, plan.md, CHARTER.md. Invoked as engineer plugin -> clarify skill <slug> <artifact> or engineer plugin -> clarify skill <path>.
Not for: cross-artifact contradictions (consistency-check); changing what a feature does (feature-edit); resolutions that cascade across files (clarify the source here, then feature-edit).
${PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md); locate the target artifact. Also load its parent contract for grounding (feature.md for acs/spec/plan; CHARTER.md for feature.md).consistency-check). If none found, say so and stop.feature-edit (which owns cascade).Emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null. If downstream staleness flagged: human_action_needed: yes, recommended_next: "engineer plugin -> feature-edit skill to propagate".