ce:compound

Convert solved problems into Markdown docs with validated frontmatter and cross-references.

6|Updated Jan 29, 2023

Search Tags:#automation #documentation #docs #knowledge-management #team-learning #agent-orchestration

Ready to run

npx skills add https://github.com/rethinkhealth/glion --skill ce-compound-rethinkhealth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce:compound
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/ce-compound
Command: npx skills add https://github.com/rethinkhealth/glion --skill ce-compound-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures tacit engineering knowledge by transforming recently solved problems into shareable documentation, accelerating team learning and reducing repeat investigations.

Core Features & Use Cases

Orchestrates a multi-phase workflow that gathers context, root-cause analysis, and working solutions from specialized subagents.
Writes or updates a single comprehensive Markdown document under docs/solutions, including frontmatter, cross-references, and version history.
Automatically refreshes existing docs when overlap is detected, preserving history and adding a last_updated timestamp.

Quick Start

Run the compound workflow to document the most recent fix.

Frequently Asked Questions about ce:compound

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

FAQPage Schema

How do I automate documentation for recently solved engineering problems?▼

You can automate documentation for solved problems by orchestrating parallel subagents to draft root-cause analyses and working solutions, which then compile into a single comprehensive Markdown document.

What is the best way to capture tacit engineering knowledge into team docs?▼

Capturing tacit engineering knowledge into team docs is best achieved through an automated workflow that transforms recent fixes into shareable Markdown files, accelerating team learning and reducing repeat investigations.

How does agent orchestration work for generating root-cause analysis documents?▼

Agent orchestration for root-cause analysis works by coordinating parallel subagents that simultaneously gather context, analyze causes, and draft solutions, merging their outputs into a validated Markdown document.

Can I automatically update existing Markdown documentation when a similar problem is solved?▼

Yes, you can automatically update existing Markdown documentation by detecting content overlap, which refreshes the file while preserving version history and adding a last_updated timestamp.

Does this documentation workflow require specific folder structures for knowledge management?▼

This documentation workflow requires a specific folder structure, writing or updating the comprehensive Markdown knowledge artifacts directly under the docs/solutions directory path.

How do I structure Markdown frontmatter for cross-referenced team learning solutions?▼

You structure Markdown frontmatter for cross-referenced solutions by using validated metadata fields within the generated document, ensuring the durable artifact is suitable for search and reuse across projects.