skills.rest
cpp-for-everything
cpp-for-everythingOFFICIAL
Explore all skills by this author →
GitHub

writing-skills

Apply test-driven development cycles to create and verify Skill documentation.

1|Updated Mar 8, 2024
Search Tags:#documentation#quality#rationalization#checklists#flowcharts#test-driven-development#skill-writing
One-click install
npx skills add https://github.com/cpp-for-everything/ORM --skill writing-skills-cpp-for-everything
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/cpp-for-everything/ORM/tree/main/.windsurf/skills/writing-skills
Command: npx skills add https://github.com/cpp-for-everything/ORM --skill writing-skills-cpp-for-everything

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and maintaining Skill documentation without discipline leads to drift, inconsistent discovery, and untested updates. This skill provides a rigorous, test-driven approach to crafting, editing, and verifying Skills so they remain accurate, auditable, and reusable.

Core Features & Use Cases

  • Enforces a RED-GREEN-REFACTOR lifecycle for Skill documentation, including baseline testing and refactoring.
  • Tracks rationalizations and creates red-flag and countermeasures to prevent bypass.
  • Supports progressive disclosure patterns and cross-skill references to keep context lean.
  • Applies consistent naming, frontmatter requirements, and deployment checks to ensure quality.

Quick Start

Run a RED baseline test, then implement the GREEN skill and re-test to verify compliance.

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 writing documentation?▼

Test-driven documentation applies RED-GREEN-REFACTOR cycles to skill writing by running a RED baseline test, implementing the GREEN skill, and refactoring to verify compliance and reusability.

What is a RED baseline test in skill documentation?▼

A RED baseline test in skill documentation is the initial failure check run before implementing a skill, ensuring that mandatory checklists, frontmatter requirements, and cross-skill references are enforced.

How do I track rationalizations to prevent bypassing skill checklists?▼

Track rationalizations by documenting red flags and countermeasures during the skill writing process, enforcing mandatory checklists and deployment checks to prevent bypass and ensure quality.

Does writing skills require any specific frameworks or dependencies?▼

Writing skills requires no external dependencies or frameworks, relying entirely on internal frontmatter requirements, mandatory checklists, and cross-skill references to enforce documentation quality.

What's the best way to maintain reusable and auditable skill documentation?▼

The best way to maintain reusable skill documentation is applying test-driven development with RED-GREEN-REFACTOR cycles, rationalization tracking, and progressive disclosure patterns to keep context lean.

Why does skill documentation drift and lose consistency over time?▼

Skill documentation drifts when writing and updating lacks discipline, causing inconsistent discovery and untested updates that a rigorous test-driven approach with deployment checks prevents.

Related Skills

Explore More Content & Communication Skills→
alexsandrocruzalexsandrocruz
6

writing-skills

Validate Claude skill documentation using test-driven development with subagents.

Community
Intermediate
SatanaCSharpSatanaCSharp

create-skill

Create Skill units with standardized YAML frontmatter and optional resources.

Community
Intermediate
asadbek21coderasadbek21coder

red-green-tdd

Enforce Red-Green-Refactor TDD cycles with gate-based development steps.

Community
Advanced
stabilefrisurstabilefrisur

writing-skills

Create and validate agent Skills documentation using test-driven development.

Community
Advanced