Update README with 80/20 insight and fix description
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
10
README.md
10
README.md
@@ -17,7 +17,7 @@ Plan → Work → Review → Compound → Repeat
|
||||
|
||||
| Command | Purpose |
|
||||
|---------|---------|
|
||||
| `/workflows:plan` | Turn feature ideas into detailed GitHub issues |
|
||||
| `/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 |
|
||||
@@ -30,11 +30,11 @@ Each cycle compounds: plans inform future plans, reviews catch more issues, patt
|
||||
|
||||
Traditional development accumulates technical debt. Every feature adds complexity. The codebase becomes harder to work with over time.
|
||||
|
||||
Compounding engineering inverts this:
|
||||
- Document patterns as you discover them
|
||||
- Codify learnings so they're reusable
|
||||
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
|
||||
- Prefer duplication over premature abstraction
|
||||
|
||||
## Learn More
|
||||
|
||||
|
||||
Reference in New Issue
Block a user