writing-skills

Create process documentation with test-driven pressure scenarios and iterative refinement.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ndriyo/primepm --skill writing-skills-ndriyo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ndriyo/primepm/tree/main/.agents/skills/writing-skills
Command: npx skills add https://github.com/ndriyo/primepm --skill writing-skills-ndriyo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guarantees that process documentation is verified by agents through test-driven methods, preventing overlooked instructions and ensuring compliance.

Core Features & Use Cases

  • Test-Driven Documentation: Guides the creation of process docs that agents must fail and then pass through iterations.
  • Pressure Scenario Testing: Enables writing pressure scenarios to observe agent failures and address loopholes.
  • Use Case: When authoring a new Workflow Skill, use this to simulate agent behavior, identify rationalizations, and bulletproof instructions before deployment.

Quick Start

Use this writing skill to validate your process documentation by creating pressure scenarios. Observe agent failures, modify the instructions, and repeat until agents follow the documentation under pressure.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test process documentation for agent compliance?

Process documentation is verified through test-driven development by creating pressure scenarios where agents fail, capturing rationalizations, and iteratively refining instructions until agents follow them under pressure.

What are pressure scenarios in test-driven documentation?

Pressure scenarios in test-driven documentation are simulated edge cases designed to observe agent failures, expose instruction loopholes, and capture rationalizations to bulletproof process documentation before deployment.

How do I stop agents from rationalizing and skipping instructions?

To stop agents from rationalizing and skipping instructions, write pressure scenarios that trigger agent failures, capture those rationalizations, and iteratively modify process documentation until agent compliance is achieved.

When do I need test-driven development for process documentation?

Test-driven development for process documentation is needed when authoring a new Workflow Skill to simulate agent behavior, identify rationalizations, and bulletproof instructions to ensure compliance before deployment.

What is the best way to bulletproof agent instructions before deployment?

The best way to bulletproof agent instructions before deployment is to simulate agent behavior using pressure scenarios, observe failures, modify the documentation, and repeat iterations until agents follow instructions under pressure.

Does test-driven documentation work for authoring workflow skills?

Yes, test-driven documentation works for authoring workflow skills by guiding the creation of process docs that agents must fail and then pass through iterative refinement, preventing overlooked instructions and ensuring compliance.