| name | superpowers-core |
| description | Core behavioral discipline applied across ALL phases — brainstorming alternatives before deciding, planning before doing, strict test-driven development, and adversarial self-review. Use this whenever you are about to make a non-trivial decision, write code, or evaluate work. This is the default working style for the whole SDLC; other skills defer to it for HOW to think and work. |
Superpowers Core (behavioral spine)
Adapted from the obra/superpowers methodology. This is how every phase works, not a
phase itself. Phase skills call into these disciplines.
Brainstorm before deciding
Before any significant choice, generate at least 2–3 distinct options. State the trade-offs
of each. Pick one and justify it in one or two sentences. A single-option proposal is a
signal you haven't explored the space — go back and widen it.
Plan before doing
Restate the goal, list the steps, identify the riskiest step, and confirm the approach
before writing code or files. For multi-step work, write the plan down where the next
session can find it (memory checkpoint + .sdlc/state.json).
TDD micro-workflow (the canonical loop)
- Red — write one failing test that captures the next slice of behavior. Run it.
- Green — minimum code to pass. Run it.
- Refactor — improve structure, keep green.
Repeat in the smallest viable increments. Never write code with no failing test driving it
(unless the constitution downgrades TDD for this repo).
Adversarial review
When reviewing (yours or others'): actively try to break it. Look for unhandled edge cases,
missing tests, silent failures, and acceptance criteria not actually met. Assume there is a
bug and go find it.
Discovery
At session start, you are reminded which skills exist (SessionStart hook). When a task
matches a skill's description, trigger it — don't reinvent its logic inline. Prefer
composing skills over ad-hoc work.
Примітка (UK)
Це не фаза, а стиль роботи для всіх фаз: спершу розглянь кілька варіантів, склади план,
працюй строго test-first (Red→Green→Refactor) і перевіряй роботу вороже — шукай, де вона
ламається. Інші скіли звертаються сюди за тим, ЯК думати й працювати.
