writing-skills

Apply the RED-GREEN-REFACTOR cycle to create and maintain agent skills.

1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/LazyNinja435/astrai --skill writing-skills-lazyninja435
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/LazyNinja435/astrai/tree/main/.ai/skills/dev/writing-skills
Command: npx skills add https://github.com/LazyNinja435/astrai --skill writing-skills-lazyninja435

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • TDD for Documentation: Provides a structured RED-GREEN-REFACTOR cycle to ensure skills are tested before deployment.
  • Rationalization Prevention: Includes techniques to identify and counter agent excuses for skipping steps or violating rules.
  • Use Case: Use this when you need to create a new skill that enforces a complex workflow, ensuring that agents comply even under high-pressure scenarios like tight deadlines or conflicting priorities.

Quick Start

Use the writing-skills framework to create a new skill by first running a baseline pressure scenario to document agent failures.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply TDD to process documentation?

TDD for process documentation uses a RED-GREEN-REFACTOR cycle to verify agent behavior against written guides before deployment. You run a baseline pressure scenario, document agent failures, and iteratively refine the documentation until compliance is verified.

What is the best way to prevent agents from skipping steps in complex workflows?

Preventing agents from skipping steps requires discipline-enforcing skills built with rationalization prevention techniques. By testing documentation against high-pressure operational scenarios like tight deadlines, you identify and counter agent excuses for violating rules before deployment.

When do I need TDD for agent skills?

You need TDD for agent skills when creating discipline-enforcing workflows that must remain compliant under high-pressure operational scenarios. It ensures your process documentation is tested against actual agent behavior, preventing rationalization and step-skipping during tight deadlines or conflicting priorities.

How do I start creating a compliant agent skill?

Start creating a compliant agent skill by running a baseline pressure scenario to document agent failures. This initial test exposes where the agent rationalizes skipping steps, providing the exact requirements needed to build documentation that enforces the workflow.

Does TDD for documentation work under high-pressure operational scenarios?

TDD for documentation is specifically designed for high-pressure operational scenarios like tight deadlines and conflicting priorities. The framework tests discipline-enforcing skills against these exact pressures to ensure agents comply with complex workflows rather than rationalizing step-skipping.

Why does my agent skip workflow steps under pressure?

Agents skip workflow steps under pressure due to rationalization, where conflicting priorities or tight deadlines excuse rule violations. This TDD framework counters rationalization by testing process documentation against baseline pressure scenarios before deployment, ensuring strict compliance.