Compound

To document a root cause analysis for future search, you capture the symptom, root cause, resolution, and affected components into YAML frontmatter, generating a structured learnings document under a designated docs directory.

Creating a knowledge base from postmortem incident learning involves writing structured markdown files with YAML frontmatter that detail the original symptom, root cause, resolution, and prevention strategies for repeatability guardrails.

You capture build break investigations and runtime bug resolutions as institutional memory by providing the full context and error messages to generate a timestamped markdown file with structured metadata.

Yes, generating workflow gotcha documentation requires extracting the symptom, root cause, resolution, affected components, and optional citations into YAML frontmatter to ensure the output is structured for fast discovery.

Yes, you can use YAML frontmatter to prevent repeating test failure analysis by including a dedicated prevention section in the generated learnings document that explains how to avoid the same failure mode again.

You should save operational gotchas and test failure analysis to a structured path like docs/compound/{category}/{slug}-{YYYY-MM-DD}.md to ensure they are organized and easily discoverable by future tasks.