spurpower-writing-skills

Standardize agent skill documentation using a Test-Driven Development cycle.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill spurpower-writing-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spurpower-writing-skills
Source: https://github.com/getspur/spur/tree/main/.claude/skills/spurpower-writing-skills
Command: npx skills add https://github.com/getspur/spur --skill spurpower-writing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent or ineffective documentation by applying Test-Driven Development (TDD) to the creation of process guides, ensuring agents actually comply with the rules defined.

Core Features & Use Cases

  • TDD for Documentation: Provides a framework to write failing pressure scenarios before drafting documentation, ensuring the skill addresses real agent rationalizations.
  • Loophole Closing: Includes systematic methods to identify and block agent rationalizations, ensuring rules are followed under pressure.
  • Use Case: When you need to create a new agent skill that requires strict adherence to a workflow, use this to ensure the documentation is robust, testable, and resistant to shortcuts.

Quick Start

Use the spurpower-writing-skills framework to define a new skill by first running a baseline pressure scenario to observe agent failure.

Frequently Asked Questions about spurpower-writing-skills

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

FAQPage Schema
How do I apply TDD principles to process documentation for AI agents?

To apply TDD to process documentation, you write failing baseline pressure scenarios that expose agent rationalizations, then draft documentation rules to close those loopholes. This ensures your workflow guides are testable and robust against shortcuts.

What is a pressure scenario in test-driven documentation?

A pressure scenario is a baseline test case designed to trigger AI agent rationalizations and shortcuts. Running it before finalizing documentation helps identify workflow loopholes so you can systematically close them in your reference guides.

How do I stop AI coding agents from taking shortcuts and rationalizing skipped steps?

You stop agent rationalizations by executing baseline pressure scenarios to observe failure modes, then systematically adding rules to your documentation that block those specific shortcuts. This enforces strict adherence to the defined workflow.

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

Use a test-driven approach for creating agent skills when you need strict adherence to a complex workflow. It ensures your reusable techniques and reference guides are robust, testable, and resistant to agent rationalizations under pressure.

Does test-driven documentation require any specific testing frameworks or dependencies?

No external testing frameworks or dependencies are required. The test-driven documentation process runs baseline pressure scenarios directly against the agent to identify rationalizations and mitigate them before finalizing your reference guides.