Compound Docs

Every time your agent solves a hard problem, that solution vanishes when the session ends. Next time: same research, same struggle, same time lost.

Compound Docs captures solved problems as structured documentation — categorized with YAML frontmatter, stored in a searchable format, queryable by your agents in future sessions.

The problem it solves: Agents (and humans) repeatedly solve the same problems. Without a capture system, institutional knowledge evaporates at session end. With Compound Docs, every solved problem becomes a reusable asset.

How it works:

• After solving a non-trivial problem, the skill prompts structured capture
• YAML frontmatter tags the document with category, tags, date, and context
• Stored in a consistent location agents know to check
• Searchable by category, tag, or keyword in future sessions

Document types:

• Technical solutions (API quirks, integration fixes, workarounds)
• Process decisions (why we chose X over Y)
• Failure post-mortems (what broke and how we fixed it)
• Configuration discoveries (non-obvious settings that matter)

Includes: capture template, frontmatter schema, storage conventions, and a retrieval pattern for agents to query accumulated docs.

The ROI compounds: the more you capture, the faster future sessions run.