writing-skills

Write skill documentation using a RED-GREEN-REFACTOR workflow that requires baseline testing, failure documentation, and re-verification before deployment. This approach codifies proven techniques into a structured SKILL.md while reducing drift and rationalization.

The red-green-refactor workflow for skill creation is a testing process that identifies proven techniques, documents failure scenarios to surface rationalizations, and hardens skills through re-verification before deployment. It structures knowledge into a SKILL.md with YAML frontmatter.

Structure a SKILL.md file for progressive disclosure by including YAML frontmatter with name and description fields, followed by a well-organized body. The structure must support deployment checks and pass pressure-scenario testing to ensure guardrails are documented.

Yes, you can edit existing skills using pressure-scenario testing to surface rationalizations and validate guardrails. The workflow applies to both new skill creation and editing existing skills, requiring re-verification before deployment to maintain documentation standards.

Skill documentation drifts without deployment checks because proven techniques are not codified against baseline tests, allowing rationalization to erode guardrails. A structured SKILL.md with a deployment-ready checklist and governance patterns prevents this drift.

Yes, you need YAML frontmatter with name and description fields to deploy a tested skill guide. The SKILL.md body must also be well-organized to support progressive disclosure and pass deployment checks after the red-green-refactor workflow.