ce-compound

Document solved problems as searchable YAML-frontmatter markdown files in docs/solutions.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-compound-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-compound
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-compound
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-compound-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Solved problems and hard-won fixes disappear when a conversation ends, forcing teams to re-research the same issues. This Skill captures a recently solved problem as structured, searchable documentation so the next occurrence takes minutes instead of hours. ## Core Features & Use Cases - Parallel research subagents: A Context Analyzer, Solution Extractor, Related Docs Finder, and optional Session Historian gather evidence, detect duplicate or overlapping docs, and surface related GitHub issues before anything is written. - Schema-validated output: Produces one markdown file in docs/solutions/ with YAML frontmatter validated against a canonical schema (bug track vs knowledge track), plus a parser-safety validation script that catches silent YAML corruption. - Two execution modes: Full mode with cross-referencing, overlap detection, and specialized reviewer agents, or a lightweight single-pass mode for simple fixes and tight context budgets. - Use Case: After fixing an N+1 query bug in a Rails app, run the skill to produce docs/solutions/performance-issues/n-plus-one-brief-generation.md with symptoms, root cause, the verified fix, and prevention strategies, cross-linked to related docs. ## Quick Start Ask the assistant to run /ce-compound to document the problem you just solved in this session.

Frequently Asked Questions about ce-compound

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

FAQPage Schema
How do I document a bug fix so my team can find it later?

Run /ce-compound after solving and verifying a fix. It extracts the problem, symptoms, root cause, and solution from the conversation, then writes a categorized markdown file with searchable YAML frontmatter under docs/solutions/.

What is the difference between full mode and lightweight mode in ce-compound?

Full mode launches parallel research subagents that cross-reference existing docs, detect duplicates, and optionally search session history. Lightweight mode is a single-pass write with no subagents, suited for simple fixes or sessions nearing context limits.

Does ce-compound prevent duplicate solution documentation?

Yes, in full mode the Related Docs Finder scores overlap across five dimensions. High overlap triggers an update to the existing doc instead of creating a new one; lightweight mode skips this check and relies on ce-compound-refresh later.

What frontmatter fields are required in docs/solutions files?

Both tracks require module, date, problem_type, component, and severity. Bug-track docs additionally require symptoms, root_cause, and resolution_type, with enum values defined in references/schema.yaml.

Why does YAML frontmatter validation fail on some solution docs?

Unquoted values containing ' #' or ': ' are silently misparsed by strict YAML parsers. Run scripts/validate-frontmatter.py on the file; it names the offending fields so you can quote the values and re-validate.