writing-skills

Apply test-driven development to create, edit, and validate Skill documentation.

Updated Jul 14, 2025
One-click install
npx skills add https://github.com/woodrowpearson/mids-hero-web --skill writing-skills-woodrowpearson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/woodrowpearson/mids-hero-web/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/woodrowpearson/mids-hero-web --skill writing-skills-woodrowpearson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills provide a disciplined approach to creating and maintaining Skill documentation by applying test-driven development to process documentation, ensuring clarity, consistency, and repeatable quality.

Core Features & Use Cases

  • Structured frontmatter discipline: Ensures every Skill has a consistent name/description payload.
  • Red-Green-Refactor workflow: Guides writing, testing, and refinement cycles for Skills.
  • Quality gates: Includes rationalization checks, red flags, and progressive disclosure patterns to prevent sloppy Skill docs.

Quick Start

Use the writing-skills to draft a new SKILL.md for a discipline-enforcing Skill and start the RED-GREEN-REFACTOR cycle.

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 process documentation?

Test-driven development for process documentation enforces a RED-GREEN-REFACTOR cycle to write, test, and refine Skills. It ensures consistent frontmatter, validates patterns through subagent testing, and applies quality gates to prevent sloppy documentation.

What is the best way to maintain consistency in Skill documentation across teams?

Maintaining Skill documentation consistency requires structured frontmatter discipline and rationalization checks. By applying progressive disclosure patterns and quality gates, teams can enforce repeatable quality and prevent red flags in workflow references.

How does the RED-GREEN-REFACTOR cycle work for writing and editing Skills?

The RED-GREEN-REFACTOR cycle for writing Skills guides you to draft documentation, validate it through subagent testing, and refine the content. This enforces clarity and repeatable quality for patterns and references across teams.

Do I need subagent testing to validate my Skill documentation?

Subagent testing is required to validate Skill documentation reliability. It acts as a quality gate within the RED-GREEN-REFACTOR cycle, ensuring that structured frontmatter, workflows, and references function correctly before deployment.

What quality assurance checks prevent sloppy Skill documentation?

Quality assurance checks for Skill documentation include rationalization checks, red flag detection, and progressive disclosure patterns. These gates enforce structured frontmatter discipline and ensure repeatable quality during the RED-GREEN-REFACTOR cycle.

Can I use test-driven development to validate existing workflow patterns and references?

You can use test-driven development to validate existing workflow patterns and references by running them through subagent testing and rationalization checks. This enforces clarity and consistency when editing and validating Skills across teams.