compound-docs

You can document solved problems as Markdown files by capturing post-solution conversations into a deterministic template. This creates single-file documentation per problem, stored under docs/solutions/[category] with YAML frontmatter for fast indexing and cross-session retrieval.

YAML frontmatter is structured metadata placed at the top of a Markdown file. You need it for documentation capture to enforce strict indexing rules, enabling fast lookup and cross-session reference of categorized problem-solution documents.

You organize solved problem documentation by storing each distinct problem as a single Markdown file under a specific category directory, such as docs/solutions/[category]. This category-based organization enables quick lookup and cross-session reference.

The best way to capture problem-solution sessions is triggering documentation capture immediately after a solution is verified. This automatically populates a deterministic template from conversation history, enforcing strict YAML frontmatter for searchability.

Yes, you can detect common issue patterns from your categorized Markdown knowledge base. The stored solution documents support cross-references and pattern detection for common issues, building a searchable knowledge base across sessions.

You should trigger documentation capture immediately after a solution is verified in your session. This ensures the deterministic template accurately populates the document from conversation history before context is lost.