atdd

Plugin atdd from marketplace disciplined-agentic-engineering in swingerman/engineer. Commands read from the repo's manifest — yesterday.

Skills (3)

• atdd-mutate

  Use to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs. Triggers — "/mutate", "/kill-mutants", "run mutation testing", "mutate my code", "kill mutants", "check test quality", "fi

• atdd-team

  Use to orchestrate a team-based ATDD workflow — six phases (spec writing, spec review, pipeline generation, implementation, refine, verify & harden) each handled by a fresh agent so no role erodes across a long-running feature. Triggers — "build a feature with a team", "use ATDD with agents", "creat

• atdd

  Use to drive feature work through the Acceptance Test Driven Development workflow — Given/When/Then specs before code, a project-specific test pipeline, and two parallel test streams (acceptance + unit). Triggers — "/atdd", "build a feature", "implement a feature", "add functionality", "start develo

Slash commands (4)

• /atdd:atdd

  Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.

• /atdd:kill-mutants

  Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.

• /atdd:mutate

  Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.

• /atdd:spec-check

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

Subagents (2)

• pipeline-builder

  Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test generator", "update the pipeline", "create acceptance test infrastructure", or when the ATDD skill reaches step 3 (pipeline generation). Examples:

• spec-guardian

  Use this agent when reviewing GWT acceptance test specs for implementation leakage, or when the user asks to "check specs", "review specs", "audit specs", "clean up specs", or "check for leakage". Also invoked by the /spec-check command and as part of the ATDD workflow. Examples: <example> Context:

Hooks (2)

• PreToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/check-specs-exist.sh

• Stop

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/stop-reminder.sh

Similar plugins