By everyinc
Run a knowledge compounding cycle: brainstorm ideas from notes or meetings, plan strategies informed by past work and learnings, execute tasks in dependency batches, review plans for data accuracy and strategic alignment, then extract and save key insights to a knowledge base for smarter future sessions.
npx claudepluginhub everyinc/compound-knowledge-plugin --plugin compound-knowledgeSearch docs/knowledge/ for saved learnings that are relevant to the current topic. Returns insights, corrections, playbooks, and patterns from past sessions. This is the agent that closes the compounding loop.
Search plans/ and docs/solutions/ for related past work. Returns structured findings of what was decided, what data was used, and what worked. Use when /kw:plan needs to ground a new plan in prior context.
After a new learning is extracted, search docs/knowledge/ for entries that the new learning contradicts or supersedes. Returns candidates for update or removal. Prevents knowledge base from accumulating contradictions.
Use this agent when you need to verify that numbers, metrics, and data claims in knowledge work artifacts are accurate, sourced, and fresh. This includes checking that every number has a cited source, comparison baselines are explicit, data matches canonical definitions, and known caveats are acknowledged. <example>Context: The user has a plan that references conversion rates and revenue numbers.\nuser: "Check the data in this brief before I send it to the team"\nassistant: "I'll use the data-accuracy-reviewer agent to verify all numbers and sources"\n<commentary>Since the brief contains data claims, use the data-accuracy-reviewer to verify sources, freshness, and accuracy.</commentary></example><example>Context: The user is reviewing a strategy doc with metrics.\nuser: "Are these numbers right?"\nassistant: "Let me run the data-accuracy-reviewer to check every data claim against its source"\n<commentary>The user is specifically asking about data accuracy, which is this reviewer's specialty.</commentary></example>
Use this agent when you need to review knowledge work artifacts (plans, briefs, strategy docs, campaign proposals) for strategic alignment. This includes checking whether goals are explicit, hypotheses are falsifiable, success metrics are measurable, scope is proportional to impact, and the work serves stated objectives. <example>Context: The user has just created a plan with /workflows:plan.\nuser: "Review this plan before I share it with leadership"\nassistant: "I'll use the strategic-alignment-reviewer agent to check strategic alignment"\n<commentary>Since the user wants to validate a plan before sharing with stakeholders, use the strategic-alignment-reviewer to ensure goals, hypotheses, and metrics are sound.</commentary></example><example>Context: The user has written a campaign brief.\nuser: "Does this brief make sense strategically?"\nassistant: "Let me run the strategic-alignment-reviewer agent to evaluate this brief"\n<commentary>The user is asking about strategic soundness, which is exactly what this reviewer checks.</commentary></example>
Brain dump and compile knowledge before structuring a plan. Use when starting any non-trivial knowledge work — after a meeting, when tackling a new problem, or when you need to pull together what you know before planning.
Extract and save learnings from a completed knowledge work session. Saves to docs/knowledge/ so future plans automatically find them.
Gut-check what you know and don't know before proceeding. Use at any point to assess confidence, surface gaps, and decide whether to proceed or dig deeper.
Research past work and structure a knowledge work plan. Use when starting strategy docs, campaign plans, content briefs, research synthesis, or operational playbooks.
Multi-reviewer quality check for knowledge work. Runs strategic alignment and data accuracy reviewers on plans, briefs, and strategy docs.
Execute a knowledge work plan. Break it into tasks, do the work, and track what happened. Use after planning to actually produce the deliverables.
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
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Three lenses for clarity: vague requirements → specs (vague), strategy blind spots → 4-quadrant playbook (unknown), content vs form → leverage shift (metamedium)
Entrepreneur OS core: AUDHD executive function, voice enforcement, and research mode
PM 코치 - 업무 소통 최적화. 요청/수신/보고 세 가지 모드로 명확한 소통 지원. 두서없는 지시를 구조화된 업무 정의서로 변환.
Execution skills — briefings, meeting processing, stakeholder comms, and idea stress-testing to keep you sharp.
Generate research-backed knowledge systems from natural conversation. 15 kernel primitives, 26 commands, 249 research claims, 3 presets.