compound-lite
Capture Compound Engineering learnings into docs/solutions/ after non-trivial work. Use when finishing a PR, repeating a correction, or when the user shares Superpowers vs GSD vs Compound Engineering. Do not install the full EveryInc plugin by default.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- compound-lite
- description
- Capture Compound Engineering learnings into docs/solutions/ after non-trivial work. Use when finishing a PR, repeating a correction, or when the user shares Superpowers vs GSD vs Compound Engineering. Do not install the full EveryInc plugin by default.
03 SKILL.md 正文
Compound Engineering lite
Article: https://theaiengineer.substack.com/p/superpowers-vs-gsd-vs-compound-engineering
Compound Engineering sits on top of Superpowers or OpenGSD. It does not replace their checkpoints. The durable idea is the fourth step: write what you learned so the next agent reads it.
When to use
- After merging (or finishing) non-trivial work
- When the same correction appears twice
- When the CEO pastes Compound Engineering / Every CE references
Steps
- Copy
templates/compound/SOLUTION.md→docs/solutions/<slug>.md - Fill Problem, What worked, Prevention, Evidence (no placeholders)
- Prefer Prevention as a gate, skill, or AGENTS.md / CLAUDE.md bullet
- Verify:
python3 scripts/compound_gate.py --json --slug <slug>→ready=true - Commit the solution note with the fix PR when possible
Do not
- Install the full 33-skill plugin unless CEO explicitly asks
- Run parallel reviewer farms on every commit (token burn)
- Claim “compounded” without a gate-green
docs/solutions/file - Confuse this with PlayerZero hawk metrics (
docs/AGENT_COMPOUNDING_ROI.md)
04 同仓库更多 Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
workflow-economics-lite
Escape AI pilot purgatory: require completion-loop workflows with one owner, baseline, economic metric, system-of-record integration, and audit trail. Block orphan chatbots and interest-as-ROI claims.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
value-center-lite
Apply InfoQ Rohrer value-center / VSM five questions (agency + coherence). Use when planning work, shipping releases, or auditing agent autonomy claims. Fail closed on product-only slogans without WQTU/paywall value.
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback