superpowers-writing-skills

Create test-driven Skill documentation with structured frontmatter and sectioning.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/family3253/skill --skill superpowers-writing-skills-family3253
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-writing-skills
Source: https://github.com/family3253/skill/tree/main/skills/superpowers-writing-skills
Command: npx skills add https://github.com/family3253/skill --skill superpowers-writing-skills-family3253

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a robust framework for writing Skills using test-driven development, ensuring consistency, discoverability, and reliability in Skill deployment.

Core Features & Use Cases

  • Frontmatter discipline: enforces name/description fields and a compact metadata surface for quick discovery.
  • TDD-based creation flow: aligns RED-GREEN-REFACTOR with Skill documentation to prevent rationalizations and ensure test coverage.
  • Progressive disclosure patterns: encourages linking to heavy references and tooling, keeping the core SKILL.md lightweight.

Quick Start

Create a new Skill by populating the frontmatter name and description, then craft the three-section guide and add a minimal example to validate the workflow.

Frequently Asked Questions about superpowers-writing-skills

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

FAQPage Schema
How do I write test-driven documentation for Skill creation?

Test-driven documentation for Skill creation applies the RED-GREEN-REFACTOR cycle to draft and validate Skill units, preventing rationalizations and ensuring reliable test coverage for your content.

What is the best way to structure frontmatter for skill documentation?

The best way to structure frontmatter for skill documentation is keeping metadata concise with strict name and description fields, ensuring a compact surface for quick discovery and verifier-friendly validation.

How does progressive disclosure work for workflow documentation?

Progressive disclosure in workflow documentation encourages linking to heavy references and tooling externally, keeping the core SKILL.md lightweight while maintaining comprehensive validation guidelines.

Can I use test-driven development to edit existing skills?

Yes, you can use test-driven development to edit existing Skills by applying standardized sectioning and frontmatter constraints to validate updates and ensure ongoing CSO guideline compliance.

Why does my Skill documentation fail frontmatter validation?

Skill documentation fails frontmatter validation when metadata lacks concise name and description fields or violates CSO guidelines, which test-driven writing enforces through standardized sectioning checks.