012a638d31
The /workflows:plan skill was producing inconsistent plan filenames (sometimes gibberish, sometimes descriptive) because it lacked explicit rules for converting issue titles to filenames. Changes: - Step 2: Added instruction to convert title to kebab-case filename with example transformation (feat: Add User Auth → feat-add-user-auth.md) - Output Format: Replaced vague <issue_title> placeholder with clear pattern and good/bad examples Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Compound Engineering Plugin
A Claude Code plugin that makes each unit of engineering work easier than the last.
Install
/plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin
/plugin install compound-engineering
Workflow
Plan → Work → Review → Compound → Repeat
| Command | Purpose |
|---|---|
/workflows:plan |
Turn feature ideas into detailed implementation plans |
/workflows:work |
Execute plans with worktrees and task tracking |
/workflows:review |
Multi-agent code review before merging |
/workflows:compound |
Document learnings to make future work easier |
Each cycle compounds: plans inform future plans, reviews catch more issues, patterns get documented.
Philosophy
Each unit of engineering work should make subsequent units easier—not harder.
Traditional development accumulates technical debt. Every feature adds complexity. The codebase becomes harder to work with over time.
Compound engineering inverts this. 80% is in planning and review, 20% is in execution:
- Plan thoroughly before writing code
- Review to catch issues and capture learnings
- Codify knowledge so it's reusable
- Keep quality high so future changes are easy
Learn More
- Full component reference - all agents, commands, skills
- Compound engineering: how Every codes with agents
- The story behind compounding engineering