writing-skills

Create and verify agent skills using a RED-GREEN-REFACTOR cycle.

7|1|Updated Mar 15, 2017
One-click install
npx skills add https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD --skill writing-skills-henquewl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD/tree/main/.opencode/skills/superpowers/skills/writing-skills
Command: npx skills add https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD --skill writing-skills-henquewl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent or ineffective process documentation by applying Test-Driven Development (TDD) principles to the creation of agent skills.

Core Features & Use Cases

  • TDD for Documentation: Provides a structured RED-GREEN-REFACTOR cycle for writing and verifying skills.
  • Bulletproofing: Includes techniques to close loopholes and prevent agent rationalization.
  • Use Case: Use this when you need to create a new skill that requires strict adherence to rules, ensuring the agent complies even under high-pressure scenarios.

Quick Start

Use the writing-skills skill to guide the creation of a new documentation unit by running a baseline 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 use TDD to write process documentation for AI agents?

Apply a structured RED-GREEN-REFACTOR cycle to write and verify agent skills. This TDD approach standardizes process documentation creation and enforces strict rule adherence by explicitly closing loopholes.

What is the best way to prevent AI agents from bypassing rules in complex procedural guides?

Use explicit loophole closure during the documentation process. This bulletproofing technique ensures agent compliance and prevents rationalization when the agent operates under high-pressure scenarios.

How do I test agent compliance before deploying complex procedural guides?

Run a baseline pressure scenario first to test agent compliance. This verifies that discipline-enforcing documentation holds up and the agent adheres to rules in challenging situations.

Does this TDD documentation approach work for high-pressure agent scenarios?

Yes, this TDD documentation approach is specifically designed for high-pressure agent scenarios. It requires strict adherence to the RED-GREEN-REFACTOR cycle and explicit loophole closure to ensure agents comply under stress.

Why does my agent ignore process documentation during execution?

Agents ignore process documentation due to unclosed loopholes allowing rationalization. Applying a TDD framework with explicit loophole closure bulletproofs instructions and enforces strict compliance under pressure.