writing-skills

Guide AI agent skill creation with a RED-GREEN-REFACTOR testing cycle.

134|27|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/projectbluefin/dakota --skill writing-skills-projectbluefin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/projectbluefin/dakota/tree/main/.opencode/skills/writing-skills
Command: npx skills add https://github.com/projectbluefin/dakota --skill writing-skills-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new and updated process documentation (Skills) are robust, effective, and prevent agents from rationalizing workarounds, by applying Test-Driven Development principles to skill authoring.

Core Features & Use Cases

  • TDD for Documentation: Enforces the RED-GREEN-REFACTOR cycle for creating and editing Skills.
  • Pressure Scenario Testing: Develops realistic scenarios with multiple pressures (time, sunk cost, authority) to test agent compliance.
  • Rationalization Countermeasures: Identifies and explicitly addresses common excuses agents use to bypass rules.
  • Use Case: Before deploying a new skill that requires agents to always perform code reviews, you would use this skill's methodology to write pressure scenarios where agents are tempted to skip reviews due to time constraints, document the rationalizations they use, and then refine the skill to explicitly block those rationalizations.

Quick Start

Follow the RED-GREEN-REFACTOR cycle to create or update any skill documentation.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply TDD methodology to write AI agent skills?

Applying TDD to AI agent skills involves a RED-GREEN-FACTOR cycle where you establish baseline testing without the skill, write minimal documentation to address failures, and refactor to close loopholes. This ensures robust, discipline-enforcing skill creation.

What is the best way to prevent AI agents from rationalizing workarounds in documentation?

To prevent agents from rationalizing workarounds, you must develop pressure scenarios with time and authority constraints, identify common excuses, and refine documentation with explicit counter-rationalizations to block those specific bypasses.

How do I test AI agent compliance under realistic pressure scenarios?

Testing AI agent compliance involves creating realistic scenarios with multiple pressures like time, sunk cost, and authority, then observing agent behavior to identify rationalizations used to bypass rules under those specific constraints.

What is the RED-GREEN-REFACTOR cycle for skill development?

The RED-GREEN-REFACTOR cycle for skill development mandates baseline testing without the skill, writing minimal skill documentation to address observed failures, and refactoring to close loopholes identified under pressure scenarios.

Can I use this TDD approach to update existing process documentation?

Yes, you can use this TDD approach to update existing process documentation by applying the RED-GREEN-REFACTOR cycle to refine skills, test them against new pressure scenarios, and enforce stricter compliance.