writing-skills

Create reference guides and documentation using a test-driven development process.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/joyce820309/holo-oahu --skill writing-skills-joyce820309
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/joyce820309/holo-oahu/tree/main/.skills/superpowers/skills/writing-skills
Command: npx skills add https://github.com/joyce820309/holo-oahu --skill writing-skills-joyce820309

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires superpowers:test-driven-development, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The writing-skills Skill simplifies the creation of reference guides and documentation using a test-driven development approach, reducing errors and improving clarity.

Core Features & Use Cases

  • Test-Driven Documentation: Ensures that each skill is thoroughly tested before deployment, improving quality and reducing surprises.
  • RED-GREEN-REFACTOR Cycle: Follows a structured process of defining baseline behavior, writing the skill, and then refining it based on testing results.
  • Skill Types: Supports the creation of different types of skills, including techniques, patterns, and references.

Quick Start

Use the writing-skills Skill to create a new skill for process documentation. Start by defining the test scenarios, then write the skill document, and finally test it with the subagent.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create documentation using a test-driven development approach?

Test-driven documentation applies the RED-GREEN-REFACTOR cycle to skill creation, defining baseline behavior, writing the skill, and refining it based on testing results to reduce errors and improve clarity.

What is the RED-GREEN-REFACTOR cycle for skill creation?

The RED-GREEN-REFACTOR cycle is a structured process for skill creation: defining test scenarios first, writing the skill document to pass those tests, then refining it based on testing results.

What types of skills can I build with test-driven documentation?

Test-driven documentation supports creating different types of skills, including techniques, patterns, and references, ensuring each is thoroughly tested before deployment.

Do I need to understand test-driven development to create reference guides?

Yes, creating reference guides with this process requires an understanding of superpowers:test-driven-development, as it applies TDD principles to ensure documentation quality and reduce surprises.

What's the best way to test a skill document before deployment?

The best way to test a skill document is using a subagent to validate it against predefined test scenarios, ensuring the skill behaves correctly and reducing errors before deployment.

How do I start streamlining process documentation with test-driven development?

Start streamlining process documentation by defining test scenarios for the new skill, writing the skill document, and finally testing it with the subagent to refine the output.