writing-skills

Create and verify process documentation with test-driven iterative refinement.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps ensure process documentation is accurate, verified, and resistant to rationalizations that may compromise clarity or compliance.

Core Features & Use Cases

  • Test-driven documentation: Applies principles similar to TDD for creating reliable, understandable skills.
  • Rationalization countermeasures: Guides users to explicitly address agent excuses and loopholes.
  • Use Case: When developing a complex process guide, use this Skill to structure tests, gather failure patterns, and iterate to bulletproof instructions.

Quick Start

Use the writing skills to create a process documentation for data validation workflows.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I verify procedural correctness in process documentation?

Verifying procedural correctness in process documentation requires applying test-driven principles to structure tests, gather failure patterns, and iteratively refine instructions for robustness and compliance.

What is test-driven development for documentation?

Test-driven development for documentation is an approach applying disciplined testing and rationalization addressing to create and verify process guides, ensuring clarity and resistance to agent excuses.

How do I address rationalizations and loopholes in process guides?

Addressing rationalizations in process guides involves explicitly identifying agent excuses and loopholes, then applying iterative refinement to bulletproof instructions and maintain procedural compliance.

What is the best way to structure tests for complex process documentation?

Structuring tests for complex process documentation involves applying test-driven development principles to gather failure patterns, verify procedural correctness, and iteratively refine instructions for clarity.

Does test-driven documentation work for data validation workflows?

Test-driven documentation works for data validation workflows by guiding the creation of process documentation through disciplined testing, rationalization addressing, and iterative refinement to ensure compliance.

When should I use a test-driven approach for documentation?

Use a test-driven approach for documentation when developing complex process guides that require verified accuracy, procedural correctness, and resistance to rationalizations that may compromise clarity or compliance.