ce-compound

Coordinate subagents to document solved problems into a searchable knowledge base.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-compound-bradliebs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-compound
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/ce-compound
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-compound-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documenting a recently solved problem to compound your team's knowledge.

Core Features & Use Cases

  • Coordinates parallel subagents to generate structured documentation in docs/solutions/ with YAML frontmatter for searchability and future reference.
  • Produces a discoverable knowledge store that accelerates onboarding and cross-team learning.
  • Supports discoverability checks and overlap assessments to avoid duplication.

Quick Start

Document the most recent fix by running ce-compound with optional context, then review the generated doc.

Frequently Asked Questions about ce-compound

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document solved problems to build a searchable team knowledge base?

You can document solved problems by coordinating parallel subagents to extract solutions and generate structured files with YAML frontmatter in docs/solutions/. This creates a searchable, categorized knowledge base for cross-referencing related issues and patterns.

What's the best way to automate knowledge management from resolved technical issues?

Automating knowledge management from resolved issues involves orchestrating phase analysis, solution extraction, and related docs search. This process produces discoverable documentation that accelerates onboarding and cross-team learning while avoiding duplication through overlap assessments.

How does extracting solutions from solved problems prevent documentation duplication?

Extracting solutions from solved problems prevents duplication by running discoverability checks and overlap assessments against existing docs/solutions/ files. This cross-referencing ensures new structured documentation does not replicate related issues and patterns already captured.

Can I use YAML frontmatter to categorize team learning documentation for future reference?

Yes, you can use YAML frontmatter to categorize team learning documentation for future reference. Generated solution files in docs/solutions/ include this frontmatter to ensure searchability and enable cross-referencing with related issues and patterns across the knowledge base.

Do I need any specific dependencies to coordinate subagents for knowledge compound tasks?

No specific dependencies are required to coordinate subagents for knowledge compound tasks. The advanced orchestration of phase analysis, solution extraction, and related docs search operates independently to generate structured documentation in docs/solutions/.

Why should I structure technical fixes into a categorized knowledge store instead of ad hoc notes?

Structuring technical fixes into a categorized knowledge store instead of ad hoc notes compounds team knowledge over time. The generated docs/solutions/ directory provides a discoverable, searchable repository that accelerates onboarding and cross-team learning through cross-referenced related issues and patterns.