Can I update existing documentation instead of creating new files?

Yes, during the capture process, the skill searches for similar existing documentation and provides options to update an existing entry or create a new doc with a cross-reference.

Where are the documentation files stored within my project?

All documentation is stored in a structured directory format under docs/solutions/, organized by categories such as performance-issues, compilation-errors, or logic-bugs.

What is the benefit of the YAML validation gate?

The validation gate ensures every piece of documentation follows a strict schema, making the knowledge base consistent, searchable, and machine-readable for future AI-driven development sessions.

How does Compound Docs detect when to document a problem?

The skill automatically monitors for confirmation phrases like 'that worked' or 'it's fixed' during conversation, but can also be manually triggered via the /doc-fix command.

What happens after the documentation is successfully created?

Users are presented with a decision menu to either continue their workflow, promote the fix to a 'Critical Pattern' in Required Reading, or link it to other related technical issues.

Compound Docs

Name: Compound Docs
Author: 8b-is

by8b-is

学習とドキュメンテーション

Captures solved problems as categorized, searchable documentation with validated YAML frontmatter for institutional knowledge building.

概要

Compound Docs is a specialized Claude Code skill designed to transform ephemeral problem-solving into durable institutional knowledge. By following a rigorous 7-step capture process, it documents technical resolutions, validates metadata against a strict YAML schema, and organizes files into specific symptom-based categories. This skill ensures that complex debugging sessions, root cause analyses, and non-obvious fixes are preserved and easily retrievable, effectively building a self-improving technical knowledge base directly within your repository for use in future development sessions.

主な機能

Smart category mapping based on enum-validated problem types
Automated problem capture triggered by confirmation phrases or manual commands
0 GitHub stars
Interactive post-capture menu for promoting solutions to 'Required Reading' or skill sets
Strict YAML frontmatter validation to ensure consistent, searchable metadata
Automated cross-referencing and critical pattern detection for recurring issues

ユースケース

Identifying and standardizing recurring technical patterns into critical project documentation
Building a searchable 'lessons learned' database for distributed engineering teams
Preserving non-obvious bug fixes and root cause analyses during intensive debugging

概要

主な機能

Smart category mapping based on enum-validated problem types
Automated problem capture triggered by confirmation phrases or manual commands
0 GitHub stars
Interactive post-capture menu for promoting solutions to 'Required Reading' or skill sets
Strict YAML frontmatter validation to ensure consistent, searchable metadata
Automated cross-referencing and critical pattern detection for recurring issues

ユースケース

Identifying and standardizing recurring technical patterns into critical project documentation
Building a searchable 'lessons learned' database for distributed engineering teams
Preserving non-obvious bug fixes and root cause analyses during intensive debugging