test-first-discipline
Hard discipline for behavior-changing work: write a failing test first, observe the failure, then write minimal production code; delete production code written before a failing test was observed. Distinct from test-suite-ensure (post-hoc coverage/scaffold). Referenced by PDCA execution stages. Triggers — 「测试先行」「先写失败测试」「红绿重构」「TDD 铁律」「test-first」 / test-first discipline, failing test first. Do NOT use as a name alias for tdd or test-driven-development.
How do I install this agent skill?
npx skills add https://github.com/fudesign2008/open-skills --skill test-first-disciplineIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is a procedural guideline for implementing Test-Driven Development (TDD) and does not contain any executable code or risky operations.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Test-First Discipline
Internal shared skill. Single source of truth for failing-test-first implementation order. Hosts declare it in
dependenciesand abort if missing — no silent fallback.Name note: intentionally not named
tddortest-driven-development(external skills repos). Use this name only.
Iron Law
NO PRODUCTION BEHAVIOR CODE WITHOUT A FAILING TEST OBSERVED FIRST.
- Write the failing test (or equivalent automated failing check).
- Run it and observe the failure in the current session.
- Write the minimal production code to pass.
- Re-run; then refactor if needed while staying green.
If production behavior code was written before step 2: delete it and restart from the failing test. Do not keep it as "reference" or "adapt while writing tests".
When it applies
Applies: new features, bug fixes, behavior-affecting refactors.
Exceptions (unless the user asks otherwise):
- Throwaway prototypes
- Generated code
- Pure configuration with no behavior under test
- Pure documentation
- User-explicit skip with a short recorded reason
Rationalizing "skip just this once" without an exception or user skip is forbidden.
Distinct from test-suite-ensure
| Skill | Owns |
|---|---|
test-first-discipline | Order — red before production behavior code |
test-suite-ensure | Post-hoc — stack detect, scaffold, generate/run coverage for existing logic |
A green test-suite-ensure run MUST NOT be reported as compliance with this skill. Hosts that use both: follow test-first during behavior implementation; call test-suite-ensure afterward for gaps/scaffold (advisory or mandatory per host).
Forbidden
- Claiming test-first compliance after only post-hoc test-suite-ensure
- Renaming or aliasing this skill to
tdd/test-driven-developmentinside this repository - Skipping the observed-red step for normal behavior changes without an exception or user skip
Integration guide
- Hosts: one-line pointer in the execution stage — load this skill for behavior changes; keep test-suite-ensure as the separate post-task ensure step.
- Prefer
user-invocable: false; users reach it through PDCA hosts. - Compose with
completion-evidence-discipline: the observed failing (and later passing) run must be fresh evidence when claiming red/green.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/fudesign2008/open-skills/test-first-discipline">View test-first-discipline on skillZs</a>