cc-master-skillsmithlisted

# cc-master-skillsmith — TDD for cc-master skill discipline > **This is a project-internal dev tool, not a distributed plugin skill.** It lives in > `.claude/skills/` (used by cc-master's own contributors), NOT in `skills/` (which ships to > plugin users). End users installing cc-master never see it; it exists only to forge *this repo's* > skills. This is the meta-skill: how cc-master writes and edits its own skills. It exists because a skill that *enforces discipline* — "the conductor never plays an instrument," "no production code without a failing test," "trust only the endpoint, not a green gate" — is itself a piece of behavior under test. You cannot know whether the prose actually changes an agent's behavior until you have watched an agent **fail without it**. **Writing a discipline skill IS test-driven development applied to prose.** The pressure scenario is the test. The agent's verbatim rationalization is the failing output. The skill section that kills that rationalization is the production code. > **REQUIRED BACKGROUND:** This skill adapts the RED-GREEN-REFACTOR cycle from > `superpowers:test-driven-development` and the subagent pressure-testing format > from `superpowers:writing-skills`. If you have not internalized those, read them > first — this skill assumes them and only adds the cc-master-specific contract. --- ## The Iron Law ``` NO DISCIPLINE SKILL — NEW OR EDITED — WITHOUT A FAILING PRESSURE BASELINE FIRST ``` The same Iron Law as TDD, mapped onto p