SkillsAdd

fudesign2008/open-skills

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.

First seen Jul 29, 2026

Installation

$ npx skills add fudesign2008/open-skills --skill test-first-discipline
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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 — 「测试?

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
clanker-discipline Similar name
gbasin/clanker-discipline

Catches state bloat, grab-bag models, and mutation ambiguity from AI coding agents. Use when re…

5.7K installs
principle-type-system-discipline Similar name
cursor/plugins

Apply when designing types, reviewing a function signature, or writing code in any statically-t…

2K installs

Also in this package

Other skills from fudesign2008/open-skills · top by installs.

npx skills add fudesign2008/open-skills
jira-fix-workflow 73 solve-workflow 71 opsx-solve-workflow 69 opsx-jira-fix-workflow 68 typescript-check 67 android-webview-debug 67 jira-read 66 git-commit 66 opsx-jira-fix-batch 65 think-big 64

Browse all from fudesign2008/open-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,973 B
  • docs SUMMARY.md 537 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 31 installs

SKILL.md

Test-First Discipline

Internal shared skill. Single source of truth for failing-test-first implementation order. Hosts declare it in dependencies and abort if missing — no silent fallback.

Name note: intentionally not named tdd or test-driven-development (external skills repos). Use this name only.

Iron Law

NO PRODUCTION BEHAVIOR CODE WITHOUT A FAILING TEST OBSERVED FIRST.

  1. Write the failing test (or equivalent automated failing check).
  2. Run it and observe the failure in the current session.
  3. Write the minimal production code to pass.
  4. 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-development inside 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.