writing-skills

Write reusable process documentation using test-first RED, GREEN, REFACTOR workflows.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Smooth-Operation/household-expense-tracker --skill writing-skills-smooth-operation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Smooth-Operation/household-expense-tracker/tree/main/.claude/skills/meta/writing-skills
Command: npx skills add https://github.com/Smooth-Operation/household-expense-tracker --skill writing-skills-smooth-operation

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill standardizes how teams capture and share knowledge by codifying processes into reusable, testable documentation. It helps prevent knowledge drift and accelerates onboarding.

## Core Features & Use Cases

  • Baseline-first Writing: Document baseline scenarios (RED) before describing a skill to validate need.
  • GREEN/REFACTOR Iteration: Write the skill with test-first principles, then validate and refine with real scenarios.
  • Structured Skill Types: Disciplines, Techniques, Patterns, and References to organize knowledge.

Use Case: A developer documents a common debugging workflow to be reused across teams, ensuring consistency.

### Quick Start Provide a living example: a quick prompt to start a skills-writing task.

  • "Draft a new skill documenting how to create a reusable testing strategy starting from a RED baseline, then GREEN implementation, followed by REFACTOR checks."

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write reusable process documentation for my team?

Process documentation using test-first practices applies a baseline RED, GREEN, REFACTOR workflow to codify knowledge into reusable skills. You write baseline scenarios first, implement the skill, then validate and refine it with real scenarios to prevent knowledge drift.

What is the RED GREEN REFACTOR workflow for process documentation?

The RED GREEN REFACTOR workflow for process documentation requires writing baseline scenarios first to validate need, implementing the skill with test-first principles, and refining the documentation through real scenario validation. This prevents knowledge drift across project repositories.

How does test-driven development apply to knowledge management?

Test-driven development applies to knowledge management by codifying processes into structured skill types like Disciplines, Techniques, Patterns, and References. This test-first documentation approach ensures captured knowledge remains testable, reusable, and standardized across project repositories.

How do I prevent knowledge drift in team documentation?

Prevent knowledge drift in team documentation by codifying processes into reusable, testable skills using a baseline RED, GREEN, REFACTOR workflow. Validating documentation against real scenarios ensures standardization and consistency across projects and onboarding materials.

Can I organize process documentation into different skill types?

You can organize process documentation into structured skill types including Disciplines, Techniques, Patterns, and References. This structured classification standardizes knowledge capture and ensures consistency across teams and documentation repositories.

What is the best way to standardize technical onboarding documentation?

The best way to standardize technical onboarding documentation is codifying workflows into reusable skills using test-first practices. Applying a baseline RED, GREEN, REFACTOR workflow ensures new team members receive validated, consistent process documentation.