Skill Forge

To automate workflow documentation, you capture a proven task sequence and forge it into a new Skill unit. This enforces YAML frontmatter with mandatory name and description fields, plus a structured body for Trigger, Protocol, Guardrails, and Verification.

The required structure for a new skill template includes YAML frontmatter with a mandatory name and description, followed by a structured body format covering Trigger, Protocol, Guardrails, and Verification sections to ensure living documentation.

For automated skill governance, create a new skill folder under .agent/skills/[skill-name-kebab-case]/ and add a SKILL.md file. Commit the changes to maintain living documentation and notify the user that the skill was forged.

No dependencies are required to extract workflows into reusable skills. The process operates independently to capture successful task sequences, enforce YAML frontmatter, and generate structured documentation for future automation.

You should update an existing skill instead of retrying a failed workflow whenever the task sequence changes. Governance and maintenance guidance encourages modifying the SKILL.md file directly to keep skills current and ensure living documentation.

The best way to turn tacit know-how into living documentation is to crystallize successful, repeatable work into new, reusable Skill units. This formal mechanism captures workflows with standardized templates and enforced structure.