compound

To extract lessons from ticket retrospectives and post-mortems, the skill processes completed work to generate Pattern, Trap, and Decision artifacts, saving them directly into your Obsidian vault.

Documenting architectural patterns and decisions is handled by creating durable Knowledge Artifacts stored under Knowledge/Patterns and Knowledge/Decisions directories, ensuring future teams can reference established architectural truths.

Yes, Obsidian integration is core to this tool; generated knowledge artifacts are written directly into the Obsidian vault under specific Knowledge/ directories to maintain structured team knowledge.

Updating GEMINI.md with new architectural learnings happens automatically during the knowledge synthesis process, applying extracted project context and architectural truths to the file.

Yes, you can capture recurring traps and mistakes by running the extraction process on completed work, which generates specific Trap artifacts saved to the Knowledge/Traps directory to prevent repeat errors.

To start compiling team knowledge from architectural reviews, you need a completed ticket or review and an Obsidian vault configured to store the generated Pattern, Trap, and Decision artifacts.