writing-skills

Document skills using a test-driven RED-GREEN-REFACTOR workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills often lack explicit testing and structure, leading to unclear guidance and inconsistent quality; this Skill enforces a test-driven approach to documenting skills to ensure reliability and reusability.

Core Features & Use Cases

  • Enforces a RED-GREEN-REFACTOR workflow for skill creation and edits.
  • Provides concise frontmatter templates and progressive-disclosure patterns to minimize token cost and maximize discoverability.
  • Guides reviewers through deployment readiness, risk assessment, and iterative improvement.

Quick Start

Create a new writing-skills SKILL.md following the template and run the RED-GREEN-REFACTOR workflow to validate it before deployment.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I document Codex and Copilot skills using a test-driven approach?

To document skills using a test-driven approach, apply a RED-GREEN-REFACTOR workflow that validates effective skill creation, enforces YAML frontmatter with concise triggers, and outputs structured searchable metadata before deployment across Codex and Copilot workflows.

What is the RED-GREEN-REFACTOR workflow for skill authoring?

The RED-GREEN-REFACTOR workflow for skill authoring enforces writing tests for skill behavior first, making documentation pass those tests, and then refining the output to minimize token cost and maximize discoverability before deployment.

How do I structure SKILL.md frontmatter to ensure deployment readiness?

To ensure deployment readiness, structure SKILL.md frontmatter with required name and description fields, keep triggers concise, and use progressive-disclosure patterns to guide reviewers through iterative risk assessment and improvement.

Does the TDD skill documentation process work for editing existing skills?

Yes, the TDD skill documentation process applies to editing existing skills by validating changes through the RED-GREEN-REFACTOR workflow to verify readiness and maintain consistent quality before redeployment across Codex and Copilot.

Why does my skill documentation lack consistent quality and clear guidance?

Skill documentation lacks consistent quality when it misses explicit testing and structure, a problem solved by enforcing a test-driven approach with concise frontmatter templates and progressive-disclosure patterns for reliability.