doc-enforce

To automatically document design decisions and prevent knowledge loss, this Skill categorizes discussion content into design considerations, decisions, solutions, or ADRs and stores them as markdown files under the appropriate docs/ path.

An ADR records architectural design decisions and trade-offs. You should generate ADRs when critical design choices are discussed to ensure important considerations and solutions are captured as standardized markdown notes for easy retrieval.

Structuring docs for knowledge management involves categorizing content into design considerations, decisions, or solutions. This Skill automatically classifies discussions, checks for duplicates against existing docs, and stores notes in standardized templates.

Yes, you can trigger automatic documentation generation by requesting '/doc' or 'documentation'. The Skill monitors for design steps and important trade-offs, automatically proposing records and saving them as markdown files to prevent knowledge loss.

The best way to manage duplicate design notes is to automatically check existing files before saving. This Skill verifies redundancy against current docs, categorizes the new content, and applies standardized templates to maintain a clean knowledge base.

No specific dependencies are required to categorize and store markdown files. The Skill reads the SKILL.md frontmatter for identity and uses optional scripts, references, or assets as needed to support automated generation and validation.