writing-skills

Apply TDD principles to create and maintain agent Skill documentation.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/LISANG3/Larj --skill writing-skills-lisang3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/LISANG3/Larj/tree/main/skills/.agents/skills/writing-skills
Command: npx skills add https://github.com/LISANG3/Larj --skill writing-skills-lisang3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that process documentation (Skills) is as robust and reliable as code, preventing agents from bypassing critical steps through rationalization or oversight.

Core Features & Use Cases

  • Test-Driven Documentation: Applies the RED-GREEN-REFACTOR cycle to Skill creation and maintenance.
  • Pressure Scenario Testing: Simulates real-world agent behavior under stress to identify vulnerabilities.
  • Rationalization Countermeasures: Provides explicit strategies to close loopholes agents use to bypass rules.
  • Use Case: When creating a new Skill that enforces a critical process (like code review or security checks), use this Skill to rigorously test its effectiveness and ensure agents comply even under pressure.

Quick Start

Use the writing skills to test a new skill by running baseline scenarios before writing the 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 prevent AI agents from bypassing process documentation through rationalization?

To prevent agent rationalization, apply Test-Driven Development principles to skill creation by designing pressure scenarios that simulate stress, capturing verbatim failures, and iteratively refactoring documentation to close loopholes.

What is test-driven documentation for agent skills?

Test-driven documentation applies the RED-GREEN-REFACTOR cycle to skill creation, treating process documentation like code by requiring rigorous baseline scenario testing before writing the skill to ensure robust agent compliance.

How to test agent behavior under pressure to identify rule bypass vulnerabilities?

You test agent behavior under pressure by simulating real-world stress scenarios during skill development, capturing exact failure outputs, and refining the documentation to explicitly close the rationalization loopholes agents use to bypass rules.

Does test-driven development work for creating critical process enforcement skills?

Yes, test-driven development works for critical process enforcement skills by providing a structured lifecycle from baseline testing to refactoring, ensuring agents comply with security checks or code review rules even under pressure.

What are the limitations of using TDD for agent skill documentation?

A limitation of using TDD for agent skill documentation is the strict requirement for rigorous scenario design and iterative refinement, demanding verbatim failure capture to successfully close loopholes rather than relying on static rule lists.