evolving-skill-creator

To turn evolving workflows into reusable documentation, you create a SKILL.md file with YAML frontmatter defining the name and description, then add a tasks directory to capture steps, scripts, and iteration learnings.

Codifying ad-hoc team workflows into structured templates involves creating a minimal directory structure with a SKILL.md file and optional scripts, references, and assets folders to organize repeatable planning and capture learnings.

You structure a directory for iterative task learnings by creating a root SKILL.md file alongside a tasks/evolving_skill/ directory, using optional scripts, references, and assets folders to support workflow expansion.

You do not need specific dependencies to create an evolving skill template; it requires only a minimal directory structure with a SKILL.md file containing YAML frontmatter and an initial workflow body.

Yes, you can use YAML frontmatter to enable workflow discovery by defining the name and description fields within your SKILL.md file, making the evolving workflow easier to find and reuse.

You should not use this evolving skill approach for static, unchanging processes that do not benefit from iterative refinement, as its core purpose is capturing learnings and improving future executions of complex tasks.