Compounding Knowledge

Agent Delegation

You MUST delegate the identification of architectural truths, patterns, and long-term design consequences to the software-architect sub-agent. They are the authority on how these lessons influence the system's technical direction.

Workflow

Phase 1: The Retrospective

Analyze the work done for the ticket. Identify:

1. •The "Trap": What was harder than expected? What "bit" us?
2. •The "Pattern": What new design pattern did we establish?
3. •The "Decision": What architectural choice did we make that binds us?

Interactive Step: Ask the user for their perspective on what should be remembered and what new patterns were established.

Phase 2: Knowledge Crystalization

Formulate Knowledge Artifacts:

1. •Pattern: A reusable code structure or standard.
   • •Path: Knowledge/Patterns/<Name>.md
2. •Trap: A warning about a specific system behavior or "gotcha."
   • •Path: Knowledge/Traps/<Name>.md
3. •Decision: An architectural record (ADR-lite).
   • •Path: Knowledge/Decisions/<Name>.md

Phase 4: Project Synthesis (GEMINI.md)

After storing artifacts in Obsidian, synthesize the new knowledge to update the GEMINI.md file in the project root. This file serves as the long-term project context for future agent sessions.

1. •Read the current GEMINI.md (create it if it doesn't exist).
2. •Append or integrate new patterns, conventions, or "traps" identified in this session.
3. •Ensure the information is structured for maximum utility in future prompts.

Constraints

• •GEMINI.md UPDATES ONLY — No changes to source code. Analysis and context documentation only.
• •TRUTH ONLY — Document actual occurrences and decisions.
• •USE OBSIDIAN — Knowledge artifacts must be stored in the Obsidian vault.