doc-enforce

Categorize discussion content into design decisions, solutions, or ADRs and store them under docs/ paths.

1|Updated Feb 21, 2026

Search Tags:#documentation #adr #docs #knowledge-management #md #design-decisions

Ready to run

npx skills add https://github.com/kssumin/claude-playground --skill doc-enforce

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-enforce
Source: https://github.com/kssumin/claude-playground/tree/main/.claude/skills/doc-enforce
Command: npx skills add https://github.com/kssumin/claude-playground --skill doc-enforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

중요한 결정·설계 고민·지식을 .md 파일로 강제 기록한다. 대화에서 논의되고 소멸되는 지식을 방지한다. 사용자가 "/doc" 또는 "문서화" 같은 요청으로 문서화를 촉진할 때, 중요한 결정과 교훈을 즉시 남길 수 있도록 돕습니다.

Core Features & Use Cases

주제/의도의 분석에 따라 설계 고민, 결정 기록, 솔루션, ADR 등 적합한 문서 타입으로 자동 분류하고 저장 위치를 제안합니다.
기존 문서와의 중복 여부를 점검하고, 템플릿에 맞춘 문서를 생성하여 표준화를 촉진합니다.
/design 스텝과 중요한 트레이드오프가 논의될 때 자동으로 기록 제안을 트리거하고 위키/노션 언급 시 저장 방향을 보강합니다.

Quick Start

Record critical decisions and design insights as .md notes immediately in the appropriate docs/ path when decisions arise.

Frequently Asked Questions about doc-enforce

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

FAQPage Schema

How do I automatically document design decisions and prevent knowledge loss in markdown?▼

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.

What is an ADR and when should I record it in my project docs?▼

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.

How do I structure docs and categorize knowledge management files for a software project?▼

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.

Can I trigger automatic documentation generation during design trade-off discussions?▼

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.

What is the best way to manage duplicate design consideration notes in a docs folder?▼

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.

Does this documentation tool require specific dependencies to categorize and store markdown files?▼

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.