Skip to content

opensesh/KARIMO

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1,085 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

██╗  ██╗   █████╗   ██████╗   ██╗  ███╗   ███╗   ██████╗
██║ ██╔╝  ██╔══██╗  ██╔══██╗  ██║  ████╗ ████║  ██╔═══██╗
█████╔╝   ███████║  ██████╔╝  ██║  ██╔████╔██║  ██║   ██║
██╔═██╗   ██╔══██║  ██╔══██╗  ██║  ██║╚██╔╝██║  ██║   ██║
██║  ██╗  ██║  ██║  ██║  ██║  ██║  ██║ ╚═╝ ██║  ╚██████╔╝
╚═╝  ╚═╝  ╚═╝  ╚═╝  ╚═╝  ╚═╝  ╚═╝  ╚═╝     ╚═╝   ╚═════╝

License Version Claude Code


What is KARIMO?

KARIMO is a framework and Claude Code plugin for PRD-driven autonomous development. Think of it as plan mode on steroids — leveraging native worktree isolation, sub-agents, and model routing.

Philosophy: You are the architect, agents are the builders, automated review is the optional inspector.


How It Works

┌──────────┐   ┌──────┐   ┌─────┐   ┌───────┐   ┌─────────────┐   ┌─────────────┐   ┌─────────┐   ┌───────┐
│ RESEARCH │──▸│ PLAN │──▸│ RUN │──▸│ TASKS │──▸│ AUTO-REVIEW │──▸│ ORCHESTRATE │──▸│ INSPECT │──▸│ MERGE │
└──────────┘   └──────┘   └─────┘   └───────┘   └─────────────┘   └─────────────┘   └─────────┘   └───────┘
      │            │                    │              │                 │              │
      └────────────┘                    └──────────────┘                 └──────────────┘
          Loop 1                             Loop 2                           Loop 3
          Human                              Claude                        Configurable
Step What Happens
Research Discover patterns, libraries, gaps — creates PRD folder
Plan Structured interview captures requirements
Run Generate task briefs from research + PRD
Tasks → Auto-Review Claude validates briefs against codebase
Orchestrate → Inspect Execute in waves, review each PR
Merge Final PR to main

Strategic Looping

KARIMO has three strategic loops with increasing automation:

Loop Stages Driver What Happens
1 Research ↔ Plan You Iterate until PRD captures requirements
2 Tasks ↔ Auto-Review Claude Built-in validation before execution starts
3 Orchestrate ↔ Inspect Configurable Manual, Claude Code Review, or Greptile

Loop 1 — Human-Driven: /karimo:research/karimo:plan — You iterate until PRD is ready

Loop 2 — Claude Built-In: /karimo:run generates briefs → auto-review validates → you approve

Loop 3 — Review Automation: Each wave creates PRs → inspect (your choice of tooling) → merge

After all waves complete → /karimo:merge creates final PR to main.


Orchestration

Tasks execute in waves with automatic parallelization:

Wave 1: [task-1a, task-1b] ─── parallel, PRs to main
              ↓ (wait for merge)
Wave 2: [task-2a, task-2b] ─── parallel, PRs to main
              ↓ (wait for merge)
Wave 3: [task-3a] ─────────── final task
Feature How It Works
Worktree isolation Claude Code's native isolation: worktree
Branch assertion 4-layer validation prevents commits to wrong branches (v7.6.0)
Loop detection Semantic fingerprinting catches stuck tasks (v7.7.0)
Orphan cleanup Git-native detection and removal of abandoned worktrees (v7.7.0)
Incremental PRD commits PRD sections committed after each interview round for traceability (v7.7.0)
Enhanced merge reports PR descriptions show markdown vs code breakdown for transparency (v7.7.0)
Asset management Store and track visual context (mockups, screenshots, diagrams) throughout PRD lifecycle (v7.8.0)
Model routing Sonnet for simple tasks, Opus for complex, auto-escalation on failures
22 agents 16 coordination + 6 task agents (details)
Crash recovery Git state reconstruction via /karimo:dashboard --reconcile

Getting Started

Prerequisites

Tool Check Install
Claude Code claude --version claude.ai/code
GitHub CLI gh auth status brew install gh && gh auth login
Git 2.5+ git --version Included on macOS/Linux

Install

curl -sL https://raw.githubusercontent.com/opensesh/KARIMO/main/.karimo/remote-install.sh | bash

Update

.karimo/update.sh

What's Preserved Across Updates

Updated Preserved
Agents, commands, skills, templates config.yaml, learnings/, prds/*
KARIMO_RULES.md, VERSION Your content in CLAUDE.md

Full walkthrough: Getting Started


Core Commands

Command What it does
/karimo:research "feature" Start here — Creates PRD folder + runs research
/karimo:plan --prd {slug} Interactive PRD creation (~10 min)
/karimo:run --prd {slug} Brief generation → review → execution
/karimo:merge --prd {slug} Final PR to main
/karimo:dashboard Monitor progress
/karimo:feedback Capture learnings
/karimo:doctor Diagnose issues

Full reference: COMMANDS.md


Adoption Phases

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 ($15-25/PR)
Phase 3 CLI dashboard with velocity metrics via /karimo:dashboard

Details: PHASES.md


Context Architecture

KARIMO uses layered context management for efficient token usage:

Layer Size Purpose
L1 Overviews ~2K tokens Discover all items in category
L2 Full Definitions Variable Complete content for execution

Key files:

  • .claude/agents.overview.md — All agents at a glance
  • .claude/agents/karimo/*.md — Full agent definitions
  • .claude/skills.overview.md — All skills with agent mapping
  • .karimo/learnings/ — Categorized project learnings
  • .karimo/findings/ — Cross-PRD pattern index

Details: Context Architecture

Compound Learning

KARIMO has a two-tier knowledge system that makes agents smarter over time:

Tier Scope Created By Storage
Findings Per-PRD Worker agents (automatic) .karimo/prds/{slug}/findings.md
Learnings Project-wide User via /karimo:feedback .karimo/learnings/

Findings are task-to-task communication during a single PRD execution:

.karimo/prds/{slug}/
├── findings.md          # Aggregated discoveries from all tasks
└── briefs/
    └── {task}/findings.md  # Per-task discoveries (in worktree)

When a worker discovers something downstream tasks need (new API, gotcha, pattern), it writes to findings.md. The PM Agent propagates these to dependent task briefs. Findings are ephemeral — they exist for one PRD cycle.

Learnings are permanent project wisdom captured via /karimo:feedback:

.karimo/learnings/
├── index.md             # Navigation + stats
├── patterns/            # Positive practices to replicate
├── anti-patterns/       # Mistakes to avoid
├── project-notes/       # Project-specific context
└── execution-rules/     # Mandatory guidelines

Learnings are read by all agents before task execution. They prevent the same mistake from happening twice.

Promotion path: Findings that appear in 3+ PRDs can be promoted to learnings via /karimo:feedback --from-metrics.

Details: Compound Learning


Documentation

Document Description
Getting Started Installation walkthrough
Commands Full command reference
Architecture System design + agent details
Phases Adoption phases explained
Safeguards Code integrity & security

Configuration lives in .karimo/config.yaml — run /karimo:configure after install.


FAQ

Can I run without automated review? Yes. Review is optional (Phase 2). PRD interviews, execution, and PRs all work out of the box.

Having issues? Run /karimo:doctor to diagnose. Still stuck? hello@opensession.co


Contributing

See CONTRIBUTING.md

License

Apache 2.0


Built with Claude Code by Open Session

About

Autonomous development framework for Claude Code. Product design-driven orchestration with sub-agents and agent teams. Phased adoption from PRD execution to automated review.

Topics

Resources

License

Contributing

Stars

Watchers

Forks

Packages

 
 
 

Contributors