compound-eng-compound-docsDocument solved problems for team reuse. Provides process knowledge for /ia-compound. Use when documenting a resolved issue, writing up lessons learned, capt...
Install via ClawdBot CLI:
clawdbot install iliaal/compound-eng-compound-docsGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 9, 2026
An SRE documents a critical production outage caused by a database connection leak. Using the 7-step process, they capture symptoms, root cause (unclosed connections), solution (implement connection pooling), and prevention (add monitoring). The document is stored under 'availability' category and linked to similar past incidents.
A backend developer resolves a slow checkout due to an N+1 query. By following the process, they document the symptom, investigation (profiling queries), root cause, solution (eager loading), and include code examples. The file is added to 'performance-issues' with cross-references to three similar cases.
A data analyst fixes a misconfigured ETL pipeline causing incorrect revenue reports. They document the issue under 'data-quality', including tricky parsing logic and a validation script. The YAML frontmatter is validated and the file is created with a link to the related skill.
A security engineer resolves a vulnerability in OAuth token validation. They document the finding under 'security', detailing the investigation, fix (add signature check), and prevention (add unit tests). The process auto-detects the pattern as critical (third similar issue) and promotes to Required Reading.
Offer a managed, AI-assisted documentation platform that uses the compound-docs process to help teams capture and reuse problem-solving knowledge. Subscription-based, with tiered storage and analytics.
Integrate compound-docs as a plugin for CI/CD pipelines, IDEs, or incident management tools (PagerDuty, Jira). License per-seat or per-repository, with additional charges for cross-referencing and pattern detection.
Provide expert-led workshops and implementation services to help organizations adopt the compound-docs methodology. Deliverables include process customization, template setup, and team onboarding.
💬 Integration Tip
To integrate, add the compound-docs process to your team's incident response workflow and trigger documentation via the 'auto-invoke' phrases in your chat or ticketing tool.
Scored May 9, 2026
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
Audit, clean, and optimize Clawdbot's vector memory (LanceDB). Use when memory is bloated with junk, token usage is high from irrelevant auto-recalls, or setting up memory maintenance automation.
Enable and configure Moltbot/Clawdbot memory search for persistent context. Use when setting up memory, fixing "goldfish brain," or helping users configure memorySearch in their config. Covers MEMORY.md, daily logs, and vector search setup.
Local memory management for agents. Compression detection, auto-snapshots, and semantic search. Use when agents need to detect compression risk before memory loss, save context snapshots, search historical memories, or track memory usage patterns. Never lose context again.
You MUST use this for gathering contexts before any work. This is a Knowledge management for AI agents. Use `brv` to store and retrieve project patterns, dec...