writing-skills

Create and validate skills using a RED-GREEN-REFACTOR test-driven workflow.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ilderaj/superpowering-with-files --skill writing-skills-ilderaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ilderaj/superpowering-with-files/tree/main/harness/upstream/superpowers/skills/writing-skills
Command: npx skills add https://github.com/ilderaj/superpowering-with-files --skill writing-skills-ilderaj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to create, document, and verify skills using a test-driven approach, reducing ambiguity and ensuring repeatable quality.

Core Features & Use Cases

  • Provides a structured frontmatter and a disciplined workflow (RED-GREEN-REFACTOR) for skill creation.
  • Covers best practices for progressive disclosure, keyword coverage, and cross-referencing other skills.
  • Use during new-skill creation, skill edits, and pre-deployment verification to minimize rationalization and errors.

Quick Start

Execute the RED-GREEN-REFACTOR cycle to write, test, and verify a new Skill before deployment.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How does test-driven development apply to writing process documentation?

Test-driven development for process documentation applies a RED-GREEN-REFACTOR workflow to create, validate, and verify skills before deployment, reducing ambiguity and ensuring repeatable quality.

What is the RED-GREEN-REFACTOR cycle for skill creation?

The RED-GREEN-REFACTOR cycle for skill creation is a structured workflow used to write, test, and verify new skills, enforcing progressive disclosure and required YAML frontmatter fields to minimize errors.

How do I validate YAML frontmatter when creating agent workflow skills?

You validate YAML frontmatter during skill creation and editing by enforcing required fields through a test-driven approach, ensuring proper progressive disclosure structure and tooling references for coding-agent workflows.

Can I use a test-driven approach to verify governance documentation?

Yes, the test-driven approach is applicable during the creation, editing, and verification of skills across coding-agent workflows and governance documentation, ensuring structured validation and repeatable quality.

When should I use a test-driven workflow for skill editing?

Use a test-driven workflow for skill editing during pre-deployment verification and updates to minimize rationalization and errors, ensuring that progressive disclosure and keyword coverage meet best practices.