levalencia Arguments
[optional: brief context about the fix]
/compound
Coordinate multiple subagents working in parallel to document a recently solved problem.
Purpose
Captures problem solutions while context is fresh, creating structured documentation in docs/solutions/ with YAML frontmatter for searchability and future reference. Uses parallel subagents for maximum efficiency.
Why "compound"? Each documented solution compounds your team's knowledge. The first time you solve a problem takes research. Document it, and the next occurrence takes minutes. Knowledge compounds.
Usage
/workflows:compound # Document the most recent fix
/workflows:compound [brief context] # Provide additional context hint
Execution Strategy: Parallel Subagents
This command launches multiple specialized subagents IN PARALLEL to maximize efficiency:
1. Context Analyzer (Parallel)
- Extracts conversation history
- Identifies problem type, component, symptoms
- Validates against solution schema
- Returns: YAML frontmatter skeleton
2. Solution Extractor (Parallel)
- Analyzes all investigation steps
- Identifies root cause
- Extracts working solution with code examples
- Returns: Solution content block
3. Related Docs Finder (Parallel)
- Searches
docs/solutions/for related documentation - Identifies cross-references and links
- Finds related GitHub issues
- Returns: Links and relationships
4. Prevention Strategist (Parallel)
- Develops prevention strategies
- Creates best practices guidance
- Generates test cases if applicable
- Returns: Prevention/testing content
5. Category Classifier (Parallel)
- Determines optimal
docs/solutions/category - Validates category against schema
- Suggests filename based on slug
- Returns: Final path and filename
6. Documentation Writer (Parallel)
- Assembles complete markdown file
- Validates YAML frontmatter
- Formats content for readability
- Creates the file in correct location
7. Optional: Specialized Agent Invocation (Post-Documentation)
Based on problem type detected, automatically invoke applicable agents:
- performance_issue →
performance-oracle - security_issue →
security-sentinel - database_issue →
data-integrity-guardian - test_failure →
cora-test-reviewer - Any code-heavy issue →
kieran-rails-reviewer+code-simplicity-reviewer
What It Captures
- Problem symptom: Exact error messages, observable behavior
- Investigation steps tried: What didn't work and why
- Root cause analysis: Technical explanation
- Working solution: Step-by-step fix with code examples
- Prevention strategies: How to avoid in future
- Cross-references: Links to related issues and docs
Preconditions
Problem has been solved (not in-progress) Solution has been verified working Non-trivial problem (not simple typo or obvious error)
What It Creates
Organized documentation:
- File:
docs/solutions/[category]/[filename].md
Categories auto-detected from problem:
- build-errors/
- test-failures/
- runtime-errors/
- performance-issues/
- database-issues/
- security-issues/
- ui-bugs/
- integration-issues/
- logic-errors/
Success Output
✓ Parallel documentation generation complete
Primary Subagent Results:
✓ Context Analyzer: Identified performance_issue in brief_system
✓ Solution Extractor: Extracted 3 code fixes
✓ Related Docs Finder: Found 2 related issues
✓ Prevention Strategist: Generated test cases
✓ Category Classifier: docs/solutions/performance-issues/
✓ Documentation Writer: Created complete markdown
Specialized Agent Reviews (Auto-Triggered):
✓ performance-oracle: Validated query optimization approach
✓ kieran-rails-reviewer: Code examples meet Rails standards
✓ code-simplicity-reviewer: Solution is appropriately minimal
✓ every-style-editor: Documentation style verified
File created:
- docs/solutions/performance-issues/n-plus-one-brief-generation.md
This documentation will be searchable for future reference when similar
issues occur in the Email Processing or Brief System modules.
What's next?
1. Continue workflow (recommended)
2. Link related documentation
3. Update other references
4. View documentation
5. Other
The Compounding Philosophy
This creates a compounding knowledge system:
- First time you solve "N+1 query in brief generation" → Research (30 min)
- Document the solution → docs/solutions/performance-issues/n-plus-one-briefs.md (5 min)
- Next time similar issue occurs → Quick lookup (2 min)
- Knowledge compounds → Team gets smarter
The feedback loop:
Build → Test → Find Issue → Research → Improve → Document → Validate → Deploy
↑ ↓
└──────────────────────────────────────────────────────────────────────┘
Each unit of engineering work should make subsequent units of work easier—not harder.
Auto-Invoke
- "that worked" - "it's fixed" - "working now" - "problem solved"
Use /workflows:compound [context] to document immediately without waiting for auto-detection.
Routes To
compound-docs skill
Applicable Specialized Agents
Based on problem type, these agents can enhance documentation:
Code Quality & Review
- kieran-rails-reviewer: Reviews code examples for Rails best practices
- code-simplicity-reviewer: Ensures solution code is minimal and clear
- pattern-recognition-specialist: Identifies anti-patterns or repeating issues
Specific Domain Experts
- performance-oracle: Analyzes performance_issue category solutions
- security-sentinel: Reviews security_issue solutions for vulnerabilities
- cora-test-reviewer: Creates test cases for prevention strategies
- data-integrity-guardian: Reviews database_issue migrations and queries
Enhancement & Documentation
- best-practices-researcher: Enriches solution with industry best practices
- every-style-editor: Reviews documentation style and clarity
- framework-docs-researcher: Links to Rails/gem documentation references
When to Invoke
- Auto-triggered (optional): Agents can run post-documentation for enhancement
- Manual trigger: User can invoke agents after /workflows:compound completes for deeper review
Related Commands
/research [topic]- Deep investigation (searches docs/solutions/ for patterns)/workflows:plan- Planning workflow (references documented solutions)