sop-maintenance

Enforces documentation rules for maintaining the Cognitive Lead AI SOP repository.

6|Updated May 18, 2026
One-click install
npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill sop-maintenance-mokhtarabadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sop-maintenance
Source: https://github.com/mokhtarabadi/cognitive-lead-hq/tree/main/.opencode/skills/sop-maintenance
Command: npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill sop-maintenance-mokhtarabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a standard operating procedures repository consistent is hard: stack documents drift in structure, changelogs get forgotten, and agents generate code where only documentation belongs. This Skill gives AI agents a strict, enforceable rulebook for every modification to the SOP repository. ## Core Features & Use Cases - Mandatory Document Structure: Requires every stack document to contain Project Structure, Naming Conventions, Architectural Patterns, and Testing Strategies sections in a fixed order. - Documentation Synchronization: Keeps the active task file in tasks/, DESIGN.md, and CHANGELOG.md (Keep a Changelog format) in sync whenever system-prompt.md or structural files change. - Markdown-Only Enforcement: Restricts all output to validated Markdown documentation and prohibits generating application code inside the SOP repository. - Use Case: When an agent updates a stack rule document, it must also update CHANGELOG.md, record status and architectural reasoning in the active task file, and validate Markdown formatting before marking the task complete. ## Quick Start Apply the sop-maintenance rules whenever you modify any document in this SOP repository and update the changelog and active task file accordingly.

Frequently Asked Questions about sop-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a stack document in the SOP repository?▼

Edit the Markdown file while preserving the four required sections in order: Project Structure, Naming Conventions, Architectural Patterns, and Testing Strategies. Then update CHANGELOG.md and record the changes in the active task file.

What sections must every stack document include?▼

Every stack document must include Project Structure, Naming Conventions, Architectural Patterns, and Testing Strategies, in that exact order. Documents missing any of these sections violate the repository rules.

When must CHANGELOG.md be updated?▼

CHANGELOG.md must be updated whenever system-prompt.md or any stack rule document is modified. Entries must follow the Keep a Changelog format.

Can I generate application code in the SOP repository?▼

No. The repository contains standard operating procedures only, so agents must not generate application code there. All output is limited to validated Markdown documentation.

Should I use STATE.md or TODO.md to track work?▼

No. Legacy STATE.md and TODO.md files are deprecated. All work tracking is decentralized to active task files in the tasks/ directory, which agents must read and update with final status and reasoning.