writing-skills

Apply test-driven development cycles to create structured SKILL.md documentation.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/miles990/claude-starter-kit --skill writing-skills-miles990
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/miles990/claude-starter-kit/tree/main/.skillpkg/skills/writing-skills
Command: npx skills add https://github.com/miles990/claude-starter-kit --skill writing-skills-miles990

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills apply test-driven development principles to process documentation, enabling teams to create reusable, verifiable Skill units and preventing drift from ad hoc prompts.

Core Features & Use Cases

  • TDD-based Skill creation: enforce RED-GREEN-REFACTOR cycles for Skill docs.
  • Rationalization tracking: capture baseline failures and explicit counters to close loopholes.
  • Progressive disclosure patterns: organize SKILL.md with references and optional assets for scalable docs.
  • Use Case: create a new Skill, validate it with pressure scenarios, then iterate to bulletproof the documentation.

Quick Start

  • Draft SKILL.md with YAML frontmatter (name and description) and an inline body.
  • Write RED baseline test scenarios without the Skill to observe failures.
  • Implement GREEN Skill content and run evaluations to verify compliance.
  • Refactor to close new loopholes and run re-testing cycles.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use TDD methodology to write reliable process documentation?

TDD methodology creates reliable process documentation by enforcing a RED-GREEN-REFACTOR cycle, capturing baseline failures first, then implementing and refactoring Skill content to close loopholes.

What is test-driven development for skill writing and how does it prevent documentation drift?

Test-driven development for skill writing prevents documentation drift by replacing ad hoc prompts with verifiable Skill units, capturing baseline failures and rationalization tracking to ensure reusable process docs.

How do I structure SKILL.md files with progressive disclosure for scalable documentation?

Structure SKILL.md files with YAML frontmatter containing name and description, using inline bodies and optional assets to organize references for progressive disclosure and scalable skill documentation.

What's the best way to validate process docs against pressure scenarios before publishing?

Validate process docs by writing RED baseline test scenarios without the Skill to observe failures, then implementing GREEN content and running evaluations to verify compliance under pressure scenarios.

Why does my process documentation develop loopholes and drift from the original requirements?

Process documentation develops loopholes and drift when relying on ad hoc prompts, which rationalization tracking and explicit counters in a TDD cycle can capture and close during re-testing.

Can I apply quality assurance testing to skill creation for teams without coding dependencies?

Quality assurance testing applies to skill creation without coding dependencies by using structured SKILL.md frontmatter and pressure scenario evaluations to verify reliability and bulletproof documentation.