writing-skills

Create and validate Skills using a RED-GREEN-REFACTOR cycle.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Phife726/ds_agent --skill writing-skills-phife726
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Phife726/ds_agent/tree/main/writing-skills
Command: npx skills add https://github.com/Phife726/ds_agent --skill writing-skills-phife726

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to authoring and validating Skills using test-driven development principles, enabling consistent, reusable process documentation.

Core Features & Use Cases

  • Red-Green-Refactor workflow: baseline testing, minimal Skill creation, and iterative hardening against rationalizations.
  • Progressive disclosure guidelines: organizes content to load heavy references only when needed.
  • Quality checks and deployment discipline: mandatory testing before deployment and documentation patterns.

Quick Start

Write a baseline failing scenario, then create a minimal Skill to fix it and re-test with full verification.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply test-driven development to skill authoring and process documentation?

Test-driven skill authoring uses a RED-GREEN-REFACTOR cycle: write a baseline failing scenario, create a minimal Skill to pass it, then iteratively tighten loopholes in the process documentation.

What is the best way to validate skills against rationalizations before deployment?

The best way to validate skills is mandatory testing using progressive disclosure guidelines and iterative hardening checks, ensuring full verification of process documentation before deployment.

How does a RED-GREEN-REFACTOR workflow work for creating reusable process documentation?

The RED-GREEN-REFACTOR workflow for process documentation starts with baseline testing, proceeds to minimal Skill creation to pass tests, and ends with iterative refinement to ensure alignment with TDD principles.

Do I need to follow progressive disclosure guidelines when generating skills with TDD principles?

Yes, progressive disclosure is required when generating skills with TDD principles to organize content efficiently and load heavy references only when needed during the validation workflow.

Why does test-driven skill generation require explicit testing strategies across teams?

Test-driven skill generation requires explicit testing strategies to ensure consistent quality checks, prevent rationalization loopholes, and maintain alignment with best-practices guidelines across teams.

Can I use flowcharts to map out the baseline testing phase of skill creation?

Yes, flowcharts can be used to map baseline testing scenarios in skill creation, providing visual structure to the RED-GREEN-REFACTOR cycle and ensuring comprehensive documentation of testing strategies.