skill-contract-generator

To generate an evolution contract, select a target skill's SKILL.md and run the contract generator to insert a dedicated contract section and produce a detailed references/contract.md with full specifications.

A skill evolution contract defines what can change, what must remain stable, and how knowledge should be extracted. It separates stable general knowledge from mutable project-specific details to guide updates.

Separating stable and mutable details is achieved by defining update rules and knowledge-extraction boundaries within a formal evolution contract, which distinguishes general knowledge from project-specific configurations.

Yes, governance rules can be applied to creating new skills or formalizing updates across projects. The contract generator defines evolution boundaries and guides governance workflows for skill documentation.

No external dependencies are required to formalize skill evolution boundaries. The contract generator operates independently to insert concise contracts into SKILL.md and generate detailed reference documentation.

The best way to guide skill-updater workflows is to generate a detailed references/contract.md file that defines update rules, stable elements, and mutable project-specific details to direct the documentation updates.