writing-skills
Writing Skills
Overview
Writing skills IS Test-Driven Development applied to process documentation.
Skills use a 3-tier progressive disclosure model:
- Frontmatter (always loaded, ~30 tokens) --
name+descriptiononly - SKILL.md body (loaded on trigger, <=150 lines) -- Quick Start, core principles, reference table
references/(loaded on demand, unlimited) -- detailed guides, examples, checklists
This skill demonstrates the pattern it teaches: core workflow here, deep detail in references/.
REQUIRED: superpowers-bd:test-driven-development, superpowers-bd:rule-of-five-plans
Quick Start
- Confirm need -- Is this a repeated failure pattern? (Not one-off, not project-specific, not already documented)
- Set up --
skills/skill-name/SKILL.md+references/directory if content exceeds <=150 line budget
More from schlenks/superpowers-bd
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
10dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
9brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
8epic-verifier
Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch
8rule-of-five-tests
Use when writing 50+ lines of test code, adding test suites, or before claiming test work complete - apply 5 focused passes (Draft, Coverage, Independence, Speed, Maintainability) to catch issues single-shot generation misses
8systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8