integrate-skill

Automating the integration of external skills into project guidelines involves parsing SKILL.md files to generate standardized guideline sections, code templates with a .template suffix, and spec index updates. This process ensures consistent documentation and reduces manual guidance drift across frontend and backend workflows.

The best way to update documentation when adopting new skills is to automate the generation of guideline sections and code examples within the .trellis/spec/ directory. This ensures seamless integration and maintains standardized documentation across frontend and backend contexts without manual editing.

Parsing SKILL.md generates code templates and spec index entries by extracting skill definitions and validating inputs to create standardized guideline sections. It produces code example templates with a .template suffix and automatically updates the corresponding indexes in the .trellis/spec/ documentation structure.

Yes, this integration approach supports both frontend and backend workflow documentation. It guides seamless integration into .trellis/spec/ documentation, ensuring standardized guidelines, examples, and index entries are consistently applied across different project contexts.

No, you do not need to manually create .template files when adding external skills to guidelines. The automation parses SKILL.md to generate code example templates with a .template suffix and updates spec indexes automatically, validating inputs to ensure correct documentation structure.