ce-compound

Coordinate parallel subagents to document solved problems into Markdown artifacts.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-compound-kinginyellows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-compound
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/RESEARCH/upstream-snapshots/e5b397c9d1883354f03e338dd00f98be3da39f9f/plugins/compound-engineering/skills/ce-compound
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-compound-kinginyellows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates multiple subagents to document a recently solved problem and compound your team's knowledge.

Core Features & Use Cases

  • Parallel subagents coordination to generate structured documentation
  • Standard templates and frontmatter for discoverable, searchable results
  • Auto memory and session-history integration to enrich docs

Quick Start

Spawn parallel subagents to document the most recent solution and store the results in docs/solutions under the appropriate category.

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 solved engineering problems?

Automate documentation for solved engineering problems by coordinating parallel subagents that extract session history and auto memory to generate structured Markdown artifacts with standardized frontmatter.

What is the best way to create searchable knowledge docs from workflow sessions?

Create searchable knowledge docs from workflow sessions by orchestrating multiple subagents to apply standard templates, generating durable Markdown files with discoverable frontmatter stored in categorized solution directories.

How does subagent orchestration work for team knowledge documentation?

Subagent orchestration for team knowledge documentation works by spawning parallel agents to process phase-level outputs, integrating auto memory and session history to enrich the final standardized Markdown artifact.

Does this documentation orchestration approach support existing research workflows?

This documentation orchestration approach supports existing research and engineering workflows by integrating auto memory and session-history data to produce consistent, traceable documentation across multiple sessions without dependencies.

How do I ensure consistent frontmatter across multiple team documentation sessions?

Ensure consistent frontmatter across multiple team documentation sessions by using orchestrated subagents that apply standard templates to generate phase-level outputs, yielding a final searchable Markdown artifact with uniform metadata.