メニュー
Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or removed. Triggers — "engineer plugin -> feature-edit skill", "change feature X to", "the ACs need updating", "revise the plan", "scope changed".
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 | feature-edit |
| description | Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or removed. Triggers — "engineer plugin -> feature-edit skill", "change feature X to", "the ACs need updating", "revise the plan", "scope changed". |
Intent-driven editing of an in-flight feature. The human describes what should now be true; this skill figures out which files and tools to touch and orchestrates the change, including the downstream cascade.
The cascade-owning skill — clarify and refine deliberately stay single-artifact and route multi-artifact propagation here. Mixed mode: the agent proposes an edit plan, the human confirms before any write.
Any time an existing feature's artifacts must change. checkpoint: null.
Not for: a brand-new capability (discuss); within-one-artifact ambiguity, no behavior change (clarify); validating consistency (consistency-check); cleaning up code (refine).
${PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md); locate the feature (slug, branch, or search feature.md titles/outcomes).discuss. Stop.feature.md; a behavior → acs.md; a GWT detail → spec.md; architecture/phasing → plan.md.feature.md → acs.md → spec.md → plan.md); upstream problems are surfaced, never auto-propagated. Per downstream artifact, classify by blast radius: small/mechanical → feature-edit edits directly; substantial → invoke the owning skill (discover-acs / atdd plugin atdd skill / plan) in edit-pass mode..build/spec.json after any spec.md change; re-run affected test streams if code exists. If regeneration reveals an upstream problem, stop and surface it.progress.md (affected checkpoint rows) and the tracker via the driver.Emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts lists every artifact edited. recommended_next: typically "re-run engineer plugin -> consistency-check skill".