Skip to content

docs(writing-plans): add explicit TDD sub-skill requirements #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alexrexi wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(writing-plans): add explicit TDD sub-skill requirements #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions skills/writing-plans/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,18 @@ Assume they are a skilled developer, but know almost nothing about our toolset o

**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md`

## Required Sub-Skills

Plans follow strict TDD. Before executing any task from a plan:

- **REQUIRED:** `superpowers:test-driven-development` - Every task uses RED-GREEN-REFACTOR. If you haven't read this skill, read it first. It covers:
- The Iron Law: no production code without a failing test first
- How to verify tests fail for the right reason
- Common rationalizations and red flags
- When to delete code and start over

- **REQUIRED:** `superpowers:testing-anti-patterns` - Prevents testing mock behavior instead of real code

## Bite-Sized Task Granularity

**Each step is one action (2-5 minutes):**
Expand Down