Workflows for knowledge work that compounds over time
npx claudepluginhub everyinc/compound-knowledge-pluginKnowledge compounds. Brainstorm, plan, review, execute, and save what you learn — so the next cycle starts smarter. 6 skills, 5 agents.
Share bugs, ideas, or general feedback.
Workflows for knowledge work that compounds over time. The knowledge work equivalent of Compound Engineering.
Read the story: How to Build a Command Center That Keeps You Sane
/kw:brainstorm --> Brain dump, pull references, find the shape
/kw:plan --> Structure into an actionable plan
/kw:confidence --> Gut-check what you know vs. don't (callable at any point)
/kw:review --> Strategic alignment + data accuracy check
/kw:work --> Execute the plan, produce deliverables
/kw:compound --> Save learnings for next time
Each cycle makes the next one faster. /kw:plan searches docs/knowledge/ for past learnings saved by /kw:compound. Knowledge compounds.
Inside a Claude Code session:
/plugin marketplace add EveryInc/compound-knowledge-plugin
/plugin install compound-knowledge
Brainstorm something. A problem, a campaign, notes from a meeting:
/kw:brainstorm I need to figure out our Q2 content strategy
When you're ready to commit to a direction:
/kw:plan
After any meaningful session, save what you learned:
/kw:compound
Next time you brainstorm or plan something related, those learnings surface automatically.
Start here. Paste a meeting transcript, brain dump raw thoughts, or describe a problem. Auto-searches your knowledge base and past plans for relevant context, then extracts key decisions, open questions, constraints, and tensions.
Structure a brainstorm into an actionable plan. Launches parallel research agents to find past work and saved learnings. Outputs a Pyramid Principle plan (lead with the answer) in three detail tiers — Quick for gut checks, Standard for most plans, Deep for multi-quarter strategies.
Callable at any point in the loop. Pauses to honestly assess what Claude knows and doesn't know — in plain language, not a table. Produces a "confident about / less confident about / my recommendation" breakdown, then offers specific actions to close gaps.
Two reviewers check your work in parallel:
Findings are merged and grouped P1 (blocks shipping) / P2 (should fix) / P3 (nice to have).
Execute a plan. Break it into tasks, group by dependency, run independent tasks in parallel. Writes execution log back to the plan file so /kw:compound has concrete material to learn from.
Extract 1-3 learnings from a session. Checks for stale knowledge that the new learning contradicts. Saves to docs/knowledge/ with searchable YAML frontmatter.
/kw:plan searches docs/knowledge/ — finds past insights/kw:compound saves what you learned to docs/knowledge/No configuration needed. Works with any project that has a plans/ directory.
The knowledge files are plain markdown, git-tracked, and greppable:
# docs/knowledge/trial-conversion-timing.md
---
type: insight
tags: [trials, conversion, campaigns]
confidence: high
created: 2026-02-15
source: Q1 trial campaign analysis
---
# Trial Conversion Timing
Extended trial periods (30 days vs 7 days) increase conversion rate but
delay revenue recognition. Net positive after 60 days.
| Type | Count | Description |
|---|---|---|
| Skills | 6 | brainstorm, plan, confidence, review, work, compound |
| Review Agents | 2 | strategic-alignment, data-accuracy |
| Research Agents | 3 | past-work-researcher, knowledge-base-researcher, stale-knowledge-checker |
The plugin reads your project's CLAUDE.md for:
If your project doesn't have a CLAUDE.md, the workflows still work — they just won't have project-specific context.
MIT