writing-skills

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

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/tridigitals/ispmanagement --skill writing-skills-tridigitals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/tridigitals/ispmanagement/tree/main/.roo/skills/writing-skills
Command: npx skills add https://github.com/tridigitals/ispmanagement --skill writing-skills-tridigitals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills standardize the creation of reusable, well-documented techniques and patterns by applying a test-driven approach to process documentation.

Core Features & Use Cases

  • Enforces a RED-GREEN-REFACTOR lifecycle for skill creation (baseline testing, minimal skill, counters, and red flags).
  • Provides structured frontmatter requirements (name & description) and a progressive disclosure pattern.
  • Includes guidance for documenting rationalizations, cross-references, and deployment readiness.
  • Supports quick-start instructions and keyword-rich discovery.

Quick Start

Write a minimal SKILL.md following the TDD flow and run the skill-testing workflow to validate it.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I document reusable skills using a test-driven approach?

You document reusable skills using a test-driven approach by applying a RED-GREEN-REFACTOR lifecycle to process documentation, enforcing baseline testing, minimal skill creation, counters, and red flags to ensure quality and repeatability.

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

The RED-GREEN-REFACTOR workflow for skill creation is a test-driven lifecycle that establishes baseline testing, builds a minimal skill, implements counters, and flags issues to verify reusable guidance before deployment.

How do I validate skill deployments across teams?

You validate skill deployments across teams by enforcing structured YAML frontmatter with a name and description, running skill-testing workflows, and checking deployment readiness alongside rationalization tracking.

Does writing reusable process documentation require YAML frontmatter?

Yes, writing reusable process documentation requires YAML frontmatter containing a name and description to enforce structure, support progressive disclosure, and enable keyword-rich discovery for skill validation.

What is the best way to track rationalizations when editing existing skills?

The best way to track rationalizations when editing existing skills is to document them structurally alongside cross-references and red flags, ensuring the modified guidance remains test-verified and deployment-ready.

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

You should avoid a test-driven approach for skill documentation when creating disposable or one-off instructional content that does not require repeatability, deployment readiness checks, or cross-team validation.