Strengthen the test-driven-development skill's outside-in workflow

[stevepolitodesign]

Run the affected test after every change and let the failure dictate the next move, and write a new failing test at each layer you drop into (e.g. a request spec before building a controller) rather than treating lower layers as covered by the feature spec.

Changes

• skills/test-driven-development/SKILL.md — Reframed the outside-in flow as a stack of failing tests:
  • New One Change, One Run section: run the affected test after every change; the failure dictates the next move.
  • New Drop Down by Writing the Next Failing Test section + a test-type ladder (feature/system → request/controller → model/unit). Each layer you drop into gets its own failing test first.
  • Demoted "just build it" to Build Directly Only for Inert Glue (route lines, empty classes) — driven by a failing test one layer up.
  • Rewrote the feature example to descend feature spec → request spec → model spec; reinforced via Red-Green-Refactor intro, Repeat, the verification checklist, Red Flags, and the rationalizations table.
• skills/test-driven-development/examples/outside-in-testing.md — Added a note flagging that the reproduced article shows the looser approach and pointing to the stricter discipline.
• NEWS.md — Added an entry under [Unreleased].

Note: version in .claude-plugin/plugin.json is intentionally left at 1.0.0 to be bumped separately.

🤖 Generated with Claude Code