superpowers-writing-skills

Generate SKILL.md documentation with YAML frontmatter and RED-GREEN-REFACTOR testing.

13|6|Updated Feb 23, 2013
One-click install
npx skills add https://github.com/abhinav/home --skill superpowers-writing-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-writing-skills
Source: https://github.com/abhinav/home/tree/main/.claude/skills/superpowers-writing-skills
Command: npx skills add https://github.com/abhinav/home --skill superpowers-writing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills are often under-tested and prone to rationalizations. This Skill applies a Test-Driven Development approach to skill documentation, running subagent-style tests to validate guidance before deployment and iterating until it remains bulletproof.

Core Features & Use Cases

  • TDD for skills: Baseline RED tests, GREEN implementation, REFACTOR to close holes.
  • Subagent-based testing: Uses pressure scenarios and rationalization tables to surface weaknesses.
  • Iterative quality: Supports multiple cycles until the skill holds under pressure.

Quick Start

Create a new skill under .claude/skills/your-skill, add SKILL.md with frontmatter and content, and run the built-in test campaigns (see examples/CLAUDE_MD_TESTING.md) to verify compliance and iterate.

Frequently Asked Questions about superpowers-writing-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply test-driven development to skill documentation?

Test-driven skill creation starts with RED tests that pressure your documentation against edge cases, then GREEN implementation that satisfies those tests, and REFACTOR cycles that close gaps. This Skill automates that RED-GREEN-REFACTOR loop using subagent scenarios to validate guidance before deployment, ensuring skills remain bulletproof under real-world pressure.

What structure should a skill documentation file have?

A skill requires YAML frontmatter with name and description, followed by SKILL.md with Frontmatter, Overview, When to Use, Core Pattern, Quick Reference, Implementation, and Common Mistakes sections. This structure ensures compliance with Claude search optimization guidelines and supports the test-driven validation cycles this Skill enforces.

How do I test my skill documentation for weaknesses before deployment?

Run built-in test campaigns that execute subagent-style pressure scenarios against your skill, surfacing rationalizations and gaps through iterative cycles. The Skill applies rationalization tables to expose flaws in your guidance until it withstands scrutiny, then validates compliance before you deploy.

Can I use this approach to improve existing skills?

Yes. This Skill applies test-driven development to creating new skills, editing existing ones, or verifying skills before deployment. Run the same RED-GREEN-REFACTOR cycles on established skills to tighten documentation and close holes that testing reveals.

What makes test-driven skill documentation different from standard writing?

Standard skill writing often contains untested rationalizations and weak spots. Test-driven skill documentation runs subagent pressure scenarios that exercise your guidance against real constraints, then iterates until it holds solid—preventing deployment of skills that fail under stress.

Do I need prior experience with test-driven development to use this Skill?

No prior TDD experience required. This Skill automates the RED-GREEN-REFACTOR pattern for skill documentation, guiding you through baseline tests, implementation validation, and refactor cycles with subagent-based pressure scenarios built into the workflow.