style-playbook-starter

To patch documentation skills, fix factual errors, broken references, and outdated guidance while keeping changes explicit. This patching process ensures standardized maintenance and reduces ambiguity across style-topic skills.

Enhancing style-topic skills involves adding reusable defaults and decision rules to improve consistency. This enhancement ensures standardized quality across teams without breaking existing content or duplicating guidance verbatim.

Updating topic skills requires reviewing the latest topic skill and source references before proposing changes. This update process validates alignment with current files and ensures the documentation reflects accurate, up-to-date guidance.

Yes, maintaining style-topic skills requires a dedicated SKILL.md file with a name, a three-section description, and mandatory citation of the starter playbook. Topic skills should reference this starter rather than duplicating content.

Using a standardized workflow for skill maintenance reduces drift and ambiguity across teams. It provides explicit patching, enhancing, and updating guidelines to ensure consistent quality and alignment for all style-topic skills.

You should not use a starter playbook when a topic skill lacks a dedicated SKILL.md or when updates require duplicating content verbatim instead of referencing the starter. It is strictly for maintaining or improving existing style-topic skills.