Implement a behavior change by writing a failing test first, then minimum code.
npx skills add https://github.com/MathieuDoyon/mission --skill mission-tdd
Please help me install this Agent Skill. Skill: mission-tdd Source: https://github.com/MathieuDoyon/mission/tree/main/.claude/skills/mission-tdd Command: npx skills add https://github.com/MathieuDoyon/mission --skill mission-tdd
mission-tdd helps developers implement a single behavior change safely and correctly by forcing a failing test first, then the minimum code needed to pass it.
Ask an orchestrator to invoke mission-tdd to implement “the next missing behavior X with verification,” and let it produce a mission-report with test-first results.
High-intent search queries and answers about installing and using this skill.
Test-driven behavior change is implemented by writing a failing test first, then applying only the minimum code required to pass it. This one-change-per-invocation discipline avoids unrelated refactors and ensures the behavior gap is safely closed with verification.
The best way to verify a behavior gap is using test-first development to turn the proposed behavior into a failing test, adding the smallest code change to pass it, and running the closest related test group to catch regressions before reporting back.
Yes, focused test commands are run to verify the new behavior, and the closest related test group is re-run to catch regressions. This verification discipline ensures small single-scope upgrades maintain existing functionality during mid-mission iterations.
Test-first development is needed for mid-mission iterations when an existing plan or review identifies a concrete behavior gap requiring verification. It produces a structured mission-report containing acceptance criteria, edited file paths, and test results.
No specific framework is required, but an orchestrator can invoke the test-first behavior change process. You ask the orchestrator to implement the next missing behavior with verification, and it produces a mission-report with test-first results and recommended next routing.
The limitation is that it strictly maintains one-change-per-invocation discipline, meaning it is not suitable for large refactors. It is designed exclusively for small, single-scope upgrades and mid-mission behavior verification tasks.
duthahoCoordinate feature development from spec through test-first implementation and review.
atholaGenerate phased, dependency-ordered implementation tasks from specifications and plans.
RobinNorbergRun bounded iterative improvement loops with evaluator-driven logs and cron reruns.
kimprobablyGuide developers through Red-Green-Refactor with failing tests before production code.
