Claude Code harness engineering plugin — plan mode on steroids. Product design-driven agent orchestration with sub-agents and agent teams, tuned for developers and designers shipping real features. Phased adoption from PRD execution to automated review, code review, and CI-friendly agent teams
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Why custom? Claude Code provides foundations (worktrees, sub-agents, hooks) but doesn't coordinate task dependencies, detect stuck loops, or recover from crashes. KARIMO adds these as a coordination layer.
| Phase | What You Get |
|-------|--------------|
| Phase 1 | PRD interviews, agent execution, worktrees, PRs — works out of the box |
| Phase 2 | Automated review via Greptile ($30/mo) or Claude Code Review |
| Phase 3 | CLI dashboard with velocity metrics |
If you previously used .karimo/update.sh to sync files into your project's .claude/plugins/karimo/, it continues to work but is no longer the recommended path. Plugin-managed installs benefit from Claude Code's built-in update, reload, and scope management.
Your First Feature
/karimo:research "feature-name" # Creates PRD folder + runs research
/karimo:plan --prd {slug} # Interactive PRD creation (~10 min)
/karimo:run --prd {slug} # Execute tasks in waves
/karimo:merge --prd {slug} # Final PR to main
Yes. Review is optional (Phase 2). PRD interviews, execution, and PRs all work out of the box.
No. KARIMO supports two modes configured via /karimo:configure: feature branch mode (tasks branch from a feature branch) or main mode (tasks branch directly from main). Choose what fits your workflow.
Yes, but be careful when running multiple feature branches with worktrees simultaneously. Typically when a feature branch and work trees are kicked off for a PRD, you only want to be doing research and planning on main. With Claude Opus 4.6, we've seen occasional conflicts. For best results, let one orchestration complete before starting another.
No. You can use manual review, Claude Code Review, or any other review mechanism. Greptile is one option for automated review in Phase 2, but it's entirely optional.
Yes — modularity was a core design goal. Nearly every decision point is configurable:
| Aspect | Options |
|--------|---------|
| Review gates | Manual, Claude Code Review, Greptile, or skip entirely |
| Branch strategy | PRs to main directly, or PRs to a feature branch first |
| Model routing | Sonnet for speed, Opus for complexity, or always escalate |
| Boundaries | never_touch files agents can't modify, require_review files that get flagged |
| Templates | PRD structure, task briefs, commit messages — all editable |
| Agents & skills | Modify behavior, add domain-specific skills, or create new agents |
| Research tools | Firecrawl, other MCP servers, or your own integrations |
| Learnings | Project-specific patterns and anti-patterns agents learn from |
Run /karimo:configure to customize, or edit .karimo/config.yaml directly.
Yes. We use Firecrawl MCP for deeper web research capability. You can integrate any MCP servers or tools that fit your workflow.
Yes. You can modify your local installation directly or fork the repository for more extensive customization. Agent definitions, templates, and skills are all editable.
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
