writing-skills

Apply test-driven development to Skill documentation with RED, GREEN, and REFACTOR phases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills helps teams codify proven techniques for skill creation and validation, turning tacit best practices into tested, deployable references.

Core Features & Use Cases

  • TDD-driven Skill creation: captures failing baseline tests, writes minimal Skill, then refactors to close loopholes.
  • Collaborative governance: enables consistent documentation across teams and reusable patterns for future projects.

Quick Start

Run a baseline RED test for a new Skill and capture agent rationalizations before writing the Skill.

Frequently Asked Questions about 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 documentation captures failing RED baseline tests before writing the minimal Skill, then refactors to close loopholes. This enforces a structured workflow with YAML frontmatter, rationalization tables, and a deployment checklist for reliable validation.

What is a RED baseline test when creating new skills?

A RED baseline test captures agent rationalizations and expected failures before writing the Skill. Running it first ensures the minimal GREEN Skill and subsequent REFACTOR tightening directly address documented edge cases and deployment readiness criteria.

How do I validate skills readiness for deployment?

Validate deployment readiness by running structured workflow checks including YAML frontmatter verification, rationalization table review, red flag detection, and a final deployment checklist. This ensures the minimal Skill passes GREEN tests before release.

Can I use flowcharts for rationalizations testing in skill-writing?

Yes, flowcharts support skills-testing by mapping agent decision paths and rationalizations. Combined with subagent tooling references, they help visualize and tighten Skill logic during the REFACTOR phase to close documentation loopholes.

Does skill-writing work without dependencies?

Skill-writing operates with zero dependencies, using internal subagent tooling references for testing instead. The structured workflow relies on YAML frontmatter and rationalization tables rather than external libraries for validation.

Why does my skill documentation need a rationalization table?

A rationalization table documents agent reasoning during baseline tests, exposing edge cases and red flags. It provides structured traceability during the REFACTOR phase, ensuring the minimal Skill closes loopholes before deployment.