compound-docs

Purpose: Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types). This skill captures problem solutions immediately after confirmation, creating structured documentation that serves as a searchable knowledge base for future sessions. Organization: Single-file architecture - each problem documented as one markdown file in its symptom category directory (e.g., docs/solutions/performance-issues/n-plus-one-briefs.md ). Files use YAML frontmatter for metadata and searchability. Auto-invoke after phrases: OR manual: /doc-fix command Non-trivial problems only: Skip documentation for: Extract from conversation history: Required information: Environment details: BLOCKING REQUIREMENT: If critical context is missing (module name, exact error, stage, or resolution steps), ask user and WAIT for response before proceeding to Step 3: Search docs/solutions/ for similar issues: IF similar issue found: THEN present decision options: WAIT for user response, then execute chosen action. ELSE (no similar issue found): Proceed directly to Step 4 (no user interaction needed). Format: [sanitized-symptom]-[module]-[YYYYMMDD].md Sanitization rules: Examples: CRITICAL: All docs require validated YAML frontmatter with enum validation. Validate against schema: Load schema.yaml and classify the problem against the...