writing-skills

Apply RED-GREEN-REFACTOR cycles to validate agent process documentation under pressure scenarios.

358|11|Updated May 15, 2026
One-click install
npx skills add https://github.com/getcrew44/crew44 --skill writing-skills-getcrew44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/coding/writing-skills
Command: npx skills add https://github.com/getcrew44/crew44 --skill writing-skills-getcrew44

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing process documentation for agents often fails under pressure because models follow “common sense” or rationalize shortcuts instead of complying with the intended discipline.

Core Features & Use Cases

  • TDD for documentation: Converts documented process rules into testable compliance by treating each skill change like a RED-GREEN-REFACTOR cycle.
  • Pressure-scenario teaching: Uses realistic, failure-inducing situations (time, sunk cost, authority, exhaustion) to prove the documentation prevents the right rationalizations.
  • Compliance-focused structure: Includes rules, explicit anti-exceptions, and “red flags” that help an agent self-correct before violating the intent.
  • Discovery-optimized guidance: Emphasizes a third-person, “Use when…” YAML description optimized for skill activation and search.

Quick Start

Use writing-skills when drafting or modifying a process rule in SKILL.md and you need to verify that an agent will comply under realistic pressure, not just agree in calm conditions.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
Why do agents ignore process documentation under pressure?

Agents bypass process documentation under pressure by rationalizing shortcuts based on common sense rather than complying with intended discipline. This Skill uses a TDD-style RED-GREEN-REFACTOR cycle to verify documentation prevents rationalizations during realistic pressure scenarios.

How do I test agent compliance with process documentation?

Test agent compliance with process documentation by running a baseline without the Skill, capturing verbatim rationalizations, applying a minimal documentation fix, and re-verifying under combined pressure scenarios like sunk cost or authority pressure.

Can I apply test-driven development to writing agent skills?

You can apply test-driven development to writing agent skills by treating each documentation change as a RED-GREEN-REFACTOR cycle, converting process rules into testable compliance requirements validated against failure-inducing situations.

What pressure scenarios should I use to validate agent skills?

Validate agent skills using realistic pressure scenarios including time constraints, sunk cost, authority pressure, and exhaustion. These failure-inducing situations prove whether process documentation prevents rationalizations and maintains agent compliance.

What is the best way to structure agent skills for discovery and compliance?

Structure agent skills for discovery and compliance by using a third-person "Use when…" YAML description optimized for skill activation, alongside explicit anti-exceptions and red flags that help agents self-correct before violating process discipline.

When should I not use TDD for process documentation?

Avoid using TDD for process documentation when modifying skills that do not enforce discipline or ordering requirements across tasks and sessions, as this approach specifically targets preventing rationalization shortcuts in compliance scenarios.