bee:writing-skills

Apply TDD cycles to create and refine agent documentation.

2|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-writing-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bee:writing-skills
Source: https://github.com/luanrodrigues/ia-frmwrk/tree/main/default/skills/writing-skills
Command: npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-writing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating robust and reliable documentation (Skills) that agents can consistently follow, preventing rationalization and ensuring adherence to best practices.

Core Features & Use Cases

  • Test-Driven Documentation: Applies the RED-GREEN-REFACTOR cycle to Skill creation, ensuring documentation is validated against actual agent behavior.
  • Rationalization Prevention: Provides explicit strategies and tables to counter common excuses agents use to bypass rules.
  • Use Case: When developing a new Skill for code review, you would first write test scenarios where an agent fails to perform a proper review without the Skill, then write the Skill to address those failures, and finally refactor to close any loopholes.

Quick Start

Use the writing skills skill to create a new skill document following the TDD process.

Frequently Asked Questions about bee:writing-skills

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

FAQPage Schema
How do I test agent documentation against actual agent behavior?

You can test agent documentation by applying the RED-GREEN-REFACTOR cycle to skill development, writing pressure scenarios where an agent fails without the skill before writing the documentation to address those failures.

What is TDD for documentation in skill development?

TDD for documentation is a process that enforces Test-Driven Development principles for creating agent skills, requiring validation against actual agent behavior through pressure scenarios to ensure rules are reliably followed.

How do I prevent rationalization when agents follow documentation?

To prevent rationalization, you can use explicit anti-rationalization tables and red flag identification strategies during skill creation, closing loopholes by refactoring documentation to counter common excuses agents use to bypass rules.

What's the best way to create robust agent skills that resist bypassing?

The best way to create robust agent skills is to write test scenarios where an agent fails without the skill, then write the skill to address those failures, and finally refactor to close any loopholes and prevent rationalization.

Do I need any dependencies to use TDD for documentation?

No dependencies are required to use TDD for documentation. The skill operates independently with reference components to guide the creation and refinement of agent documentation through pressure scenario validation.

When do I need to apply test-driven development to agent documentation?

You need to apply TDD to agent documentation when creating new skills or refining existing ones that agents inconsistently follow, ensuring the documentation is validated against actual behavior and resistant to rationalization.