writing-skills

Apply RED-GREEN-REFACTOR cycles to validate SKILL.md documentation.

69|19|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/alffei/skill_share --skill writing-skills-alffei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/alffei/skill_share/tree/main/superpowers-antigravity/skills/writing-skills
Command: npx skills add https://github.com/alffei/skill_share --skill writing-skills-alffei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills apply a test-driven development approach to Skill documentation, ensuring that skill metadata and guidance are verifiable, reusable, and deployed with confidence.

Core Features & Use Cases

  • RED-GREEN-REFACTOR for SKILL.md: Apply baseline failure tests, then implement minimal skill content and close loopholes.
  • Pressure scenario validation: Create and run pressure scenarios with subagents to surface rationalizations and ensure compliance.
  • Documentation discipline: Enforce YAML frontmatter constraints, consistent descriptions, and concise structure to improve discovery and loading efficiency.

Quick Start

Draft a minimal SKILL.md following the template, then perform RED-GREEN-REFACTOR testing with baseline scenarios and refactor until no new rationalizations appear.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
What is test-driven writing for skill documentation?▼

Test-driven writing for skill documentation applies RED-GREEN-REFACTOR cycles to SKILL.md files, ensuring metadata and guidance are verifiable, reusable, and deployed with confidence through baseline failure testing and iterative refinement.

How do I validate SKILL.md files using pressure scenarios?▼

You validate SKILL.md files by creating and running pressure scenarios with subagents to surface rationalizations, ensuring compliance and closing loopholes through iterative refactoring until no new rationalizations appear.

Can I use test-driven writing to enforce YAML frontmatter constraints in documentation?▼

Yes, test-driven writing enforces YAML frontmatter constraints, consistent descriptions, and concise structure in SKILL.md files to improve documentation discipline, discovery, and loading efficiency.

What is the best way to start writing a SKILL.md file with TDD?▼

The best way to start is drafting a minimal SKILL.md following a template, then performing RED-GREEN-REFACTOR testing with baseline scenarios and refactoring the content until no new rationalizations appear.

Why does my skill documentation fail under pressure scenario validation?▼

Skill documentation fails under pressure scenario validation when subagents surface rationalizations and loopholes, indicating the SKILL.md content lacks the precision needed for reliable compliance and requires iterative refactoring.

Do I need a specific framework to apply RED-GREEN-REFACTOR cycles to skill docs?▼

No specific framework is required, as the approach applies standard RED-GREEN-REFACTOR cycles directly to SKILL.md authoring and validation, using pressure scenarios and subagents to capture rationalizations and refine content.