writing-skills

Document writing skills with test-driven validation and iterative refinement.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills are often ad-hoc and inconsistent; this guide treats skill-writing as a disciplined, test-driven process to produce reusable, verifiable documentation.

Core Features & Use Cases

  • Establishes a repeatable pattern for documenting skills (frontmatter, sections, and iterative testing)
  • Enforces red-green-refactor-style validation of content to preempt rationalizations
  • Serves as a reference framework for creating and editing skills across teams

Quick Start

Write a new Skill by composing a SKILL.md with a YAML frontmatter containing name and description, then describe the operational workflow in the body.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write documentation using test-driven development?▼

Test-driven documentation applies red-green-refactor validation to skill-writing by documenting failing baselines, rationalizations, and iterative refinements to ensure content reliability and reuse across deployments.

What is the best way to create reusable and verifiable skill documentation?▼

The best way to create reusable skill documentation is composing a SKILL.md with YAML frontmatter containing name and description, then describing the operational workflow in the body using a disciplined, test-driven process.

How does rationalization preempting work when editing skills?▼

Rationalization preempting works by enforcing red-green-refactor-style validation of content to identify and close loopholes in skill documentation before deployment, ensuring correctness through iterative testing.

Can I use this test-driven process for both creating and editing existing skills?▼

Yes, the test-driven process applies to creating new skills, editing existing ones, and verifying their correctness before deployment, establishing a repeatable pattern for documenting skills across teams.

Do I need any dependencies to document failing baselines for skill-writing?▼

No dependencies are required to document failing baselines for skill-writing; the framework operates independently using a SKILL.md file with YAML frontmatter and an iterative refinement workflow.