/writing-skills
Writing Skills
TDD applied to process docs. Watch the agent fail without the skill, write the skill, watch it pass.
What it does
Skill authoring through red-green-refactor. Run a baseline pressure scenario against a subagent, document the exact rationalizations it uses, write the SKILL.md that addresses those violations, verify compliance, then refactor to close loopholes. If you didn't watch an agent fail without the skill, you don't know whether the skill teaches the right thing.
Use it when a repeated friction becomes a pattern, when a new technique deserves preservation across sessions, or when `skill-evolution` surfaces a candidate for a new or rewritten skill. Don't use it for one-off solutions, standard practices already documented elsewhere, or mechanical constraints that belong in a lint rule.
Outputs a SKILL.md with verified failure-mode coverage, the baseline test scenarios, and a note on version and what changed. Pairs with `test-driven-development` (the required background), `skill-evolution` (the feedback loop that proposes patches), and `soul-surgery` (the agent-voice counterpart to this skill-layer work).
Related skills