dae_codex

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.

Use as a thin compatibility skill when the user asks for the old mutate command; delegate to atdd-mutate for mutation testing and differential mutation workflow.

Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path.

Check changed feature code against charter architecture rules: layering, cycles, forbidden patterns, names, and size.

Checkpoint 3 bridge that turns ACs into Gherkin specs and hands off to the ATDD acceptance pipeline workflow.

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".

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".

Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers — "engineer plugin -> discover-acs skill", "engineer plugin -> acceptance-criteria skill", "discover ACs", "what must this feature do", "figure out acceptance criteria".

Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "engineer plugin -> discuss skill", "engineer plugin -> discuss skill <slug>", "I have an idea about", "should we build", "let's think about".

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".

Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers — "engineer plugin -> feature-init skill", "create a feature", "start a new feature", "init a feature".

Survey DAE project state at session start and recommend the next task; read-only advisory.

Use to bring a project into the DAE methodology, or to check an onboarded project for gaps. Triggers — "engineer plugin -> onboard skill", "onboard this project", "set up DAE here", "adopt the methodology", or when a DAE skill fails because no manifest exists.

Use when a feature has ACs and specs and needs an architecture plan before implementation. Triggers — "engineer plugin -> plan skill", "plan this feature", "plan the implementation", "design the architecture".

Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "engineer plugin -> prime-context skill", "prime context", "load context before we start", "get up to speed on feature X".

Use to propagate DAE state — turning handoff summaries into visible progress. Triggers — "engineer plugin -> progress-log skill", "sync progress", "update the tracker", "reconcile the tracker", "refresh feature status".

Use after a feature's code is implemented and passing, to clean up the changed code before verification. Triggers — "engineer plugin -> refine skill", "refine this code", "clean up the feature", "refactor what we built".

Re-anchor an in-flight DAE feature after compaction, interruption, or uncertainty about checkpoint and next action.

Use at the end of a work session on a DAE feature, so the next session picks up cleanly. Triggers — "engineer plugin -> session-summary skill", "wrap up the session", "write the session log", "I'm stopping for the day".