What problem does it solve? Teams lose repeatable operational knowledge when deployment steps, runbooks, and procedures live only in chat history or individual memory. This Skill formalizes those workflows into reusable, project-linked SOP documents that agents and humans can discover and follow. ## Core Features & Use Cases - SOP Creation: Create SOPs via ch_create_sop with title, content, category, and metadata linking them to repos, audiences, and environments. - SOP Discovery & Reading: List all project SOPs with ch_list_sops (showing status, priority, staleness) and read full markdown content with ch_read_sop. - Lifecycle & Chaining: Track draft/active/archived states, automatic staleness detection when referenced code changes, and chain SOPs with triggers and after metadata. - Use Case: Document a production deployment process once, then let any agent find it, follow it step by step, and automatically trigger the post-release notes SOP when finished. ## Quick Start Ask the assistant to create an SOP for your production deployment process and link it to your repository.