writing-skills

Write and validate agent documentation skills using a RED-GREEN-REFACTOR process.

Updated May 5, 2026
One-click install
npx skills add https://github.com/XCmiaow/cc-deploy --skill writing-skills-xcmiaow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/XCmiaow/cc-deploy/tree/main/skills/writing-skills
Command: npx skills add https://github.com/XCmiaow/cc-deploy --skill writing-skills-xcmiaow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents agent instructions from becoming untestable, ambiguous guidance by enforcing a test-driven loop for documentation-based skills.

Core Features & Use Cases

  • TDD-adapted skill engineering: Uses RED-GREEN-REFACTOR to ensure skills actually change agent behavior under pressure, not just sound correct.
  • Pressure scenario testing with subagents: Defines discipline-verification scenarios that capture real rationalizations and failure modes.
  • Compliance hardening: Closes loopholes by adding explicit negations, foundational principles, rationalization tables, and red-flag stop conditions.

Quick Start

Use the writing-skills Skill when you need to create or edit a documentation skill and you want to verify the agent complies by running a baseline “without-skill” pressure scenario first.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test agent documentation to ensure compliance under pressure?

Test agent documentation compliance by running baseline pressure scenarios without the skill, then apply a RED-GREEN-REFACTOR loop to verify instructions change agent behavior under time, sunk-cost, authority, or exhaustion pressure.

What is test-driven development for skill authoring?

Test-driven development for skill authoring adapts the RED-GREEN-REFACTOR process to documentation, ensuring skills enforce discipline rather than providing untestable, ambiguous guidance that agents rationalize away.

How do I close rationalization loopholes in agent instructions?

Close rationalization loopholes in agent instructions by iteratively refactoring documentation to add explicit negations, foundational principles, rationalization tables, and red-flag stop conditions that address observed violations.

How do I verify a skill changes agent behavior without just sounding correct?

Verify a skill changes agent behavior by defining discipline-verification scenarios with subagents that capture real failure modes, requiring a baseline test without the skill before making minimal documentation changes.

Can I use test-driven skill engineering for editing existing documentation?

Yes, test-driven skill engineering applies when creating, editing, or verifying skills, using the RED-GREEN-REFACTOR loop to iteratively close new loopholes while maintaining existing compliance.