writing-skills

Apply RED-GREEN-REFACTOR testing to agent Skill documentation.

3|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/pedropaulovc/agent-plugins --skill writing-skills-pedropaulovc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/pedropaulovc/agent-plugins/tree/main/plugins/superpowers/skills/writing-skills
Command: npx skills add https://github.com/pedropaulovc/agent-plugins --skill writing-skills-pedropaulovc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents low-quality, under-tested skill documentation by forcing a RED-GREEN-REFACTOR discipline for process guidance, so agents reliably follow the rules instead of rationalizing them away under pressure.

Core Features & Use Cases

  • Test-driven documentation: Treats pressure scenarios as “tests” so the Skill proves compliance, not just clarity.
  • Loophole hardening: Captures baseline rationalizations and adds explicit negations, red flags, and counters to keep behavior consistent under stress.
  • Discovery-optimized authoring: Enforces strong Skill metadata practices (especially the description field) for search relevance and activation accuracy.
  • Skill testing methodology: Provides pressure scenario design patterns, rationalization tables, and verification steps before deployment.

Quick Start

Use this Skill to validate and harden a new or edited Skill by running pressure scenarios that fail without the Skill, then updating the documentation until the same scenarios pass.

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 skills to ensure they resist rationalization under pressure?

Pressure testing agent skills involves running realistic decision scenarios that fail without the skill, then updating documentation until the same scenarios pass. This test-driven discipline proves reliable compliance instead of just surface clarity.

What is test-driven documentation for skill authoring?

Test-driven documentation treats pressure scenarios as tests, applying a RED-GREEN-REFACTOR discipline to process guidance. This ensures agents follow rules reliably instead of rationalizing them away under stress.

How do I harden skill metadata for better discovery and activation accuracy?

Harden skill metadata by enforcing strong practices in the YAML frontmatter and description fields. This optimizes search relevance and guarantees correct agent activation during skill authoring.

How do I close loopholes in agent skill documentation?

Close loopholes by capturing baseline rationalizations and adding explicit negations, red flags, and counters. This keeps agent behavior consistent and prevents rationalization during stressful decision scenarios.

When should I use a test-driven approach for writing skills?

Use test-driven skill authoring when creating new skills, editing existing skills, or verifying that skills activate correctly. It ensures YAML correctness and description-driven discovery before deployment.

Can I use RED-GREEN-REFACTOR testing for YAML frontmatter and skill metadata?

Yes, applying RED-GREEN-REFACTOR testing validates YAML frontmatter correctness and description-driven metadata. This methodology verifies that skills activate accurately and resist rationalization before deployment.