██╗ ██╗ █████╗ ██████╗ ██╗ ███╗ ███╗ ██████╗
██║ ██╔╝ ██╔══██╗ ██╔══██╗ ██║ ████╗ ████║ ██╔═══██╗
█████╔╝ ███████║ ██████╔╝ ██║ ██╔████╔██║ ██║ ██║
██╔═██╗ ██╔══██║ ██╔══██╗ ██║ ██║╚██╔╝██║ ██║ ██║
██║ ██╗ ██║ ██║ ██║ ██║ ██║ ██║ ╚═╝ ██║ ╚██████╔╝
╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═════╝
LicenseApache 2.0
version
Claude CodePlugin
★ Stars
Philosophy: You are the architect; agents are the builders

Advanced Claude Code plugin that turns PRDs (product requirements documents) into autonomous development. Think of it as plan mode on steroids, powered by context and agent orchestration.

Claude Features

10 total
Worktree Isolation

Each task executes in its own git worktree. No conflicts, no race conditions.

Mar 2026

Sub-Agents

Spawn focused child agents for parallel task execution across your codebase.

Jul 2025

Agent Teams

Coordinate multiple agents working on related tasks simultaneously.

Sep 2025

Skills

Reusable capability modules that extend agent knowledge and behavior.

Jan 2026

Hooks

Lifecycle hooks for pre/post task automation and validation steps.

Jun 2025

Model Routing

Route tasks to optimal models based on complexity and cost constraints.

Jul 2025

Commands

Custom slash commands to streamline repetitive workflows and operations.

Mar 2025

Branch Assertion

PM Agent verifies branch state before and after each operation.

Sep 2025

Loop Detection

Automatic detection of revision loops prevents infinite cycles.

Sep 2025

Crash Recovery

Execution state reconstructed from git. Resume exactly where you left off.

Sep 2025

Worktree Isolation

Each task executes in its own git worktree. No conflicts, no race conditions.

Mar 2026

Sub-Agents

Spawn focused child agents for parallel task execution across your codebase.

Jul 2025

Agent Teams

Coordinate multiple agents working on related tasks simultaneously.

Sep 2025

Skills

Reusable capability modules that extend agent knowledge and behavior.

Jan 2026

Hooks

Lifecycle hooks for pre/post task automation and validation steps.

Jun 2025

Model Routing

Route tasks to optimal models based on complexity and cost constraints.

Jul 2025

Commands

Custom slash commands to streamline repetitive workflows and operations.

Mar 2025

Branch Assertion

PM Agent verifies branch state before and after each operation.

Sep 2025

Loop Detection

Automatic detection of revision loops prevents infinite cycles.

Sep 2025

Crash Recovery

Execution state reconstructed from git. Resume exactly where you left off.

Sep 2025

Worktree Isolation

Each task executes in its own git worktree. No conflicts, no race conditions.

Mar 2026

Sub-Agents

Spawn focused child agents for parallel task execution across your codebase.

Jul 2025

Agent Teams

Coordinate multiple agents working on related tasks simultaneously.

Sep 2025

Skills

Reusable capability modules that extend agent knowledge and behavior.

Jan 2026

Hooks

Lifecycle hooks for pre/post task automation and validation steps.

Jun 2025

Model Routing

Route tasks to optimal models based on complexity and cost constraints.

Jul 2025

Commands

Custom slash commands to streamline repetitive workflows and operations.

Mar 2025

Branch Assertion

PM Agent verifies branch state before and after each operation.

Sep 2025

Loop Detection

Automatic detection of revision loops prevents infinite cycles.

Sep 2025

Crash Recovery

Execution state reconstructed from git. Resume exactly where you left off.

Sep 2025

Plan Mode Doesn't Scale

Plan mode works great for boilerplate code. The limiting factor is quadratic attention, and the workaround is harness engineering. With higher task complexity and duration, we need shared and optimized context for humans and agents.

Compound Orchestration

Click a loop to explore its commands
CONFIGURE
LOOP 1Foundation
RESEARCH
PLAN
LOOP 2Decomposition
LOOP 3Orchestration
MERGE
Human-Led

You drive this loop. KARIMO auto-detects your project config, scans your codebase for patterns, then interviews you across 5 rounds to produce a structured PRD. You decide when the plan is ready to execute.

INPUTYour codebase + your answers to the PRD interview
OUTPUTApproved PRD with task breakdown, wave plan, and dependencies
/karimo:configure
$ claude /karimo:configure --auto
→ Detected: Next.js 16, React 19, TypeScript
→ Build: npm run build Test: npm run test
→ Review provider: Greptile (threshold: 5)
→ Config saved to .karimo/config.yaml
$

Auto-detect project settings and create .karimo/config.yaml — the single source of truth for all KARIMO operations.

Scan your codebase and the web for patterns, conventions, and context before planning.

A 5-round PRD interview that produces a structured plan with tasks, waves, and dependencies. Rounds are template-driven — edit the interview skill to reshape the process.

A Real Migration, Start to Finish

Recently, we migrated an entire Framer website to a custom Next.js codebase. This can never be done in one plan mode. We migrated all the content, images, compressed them, and built new web page structures.

Key Statistics
4.5K+Lines
~2.5Hours
39+ Files
KARIMO Migration Replay
Watch the full experience on desktopTap to copy link

Git Timeline

Main

Research

/karimo:research

Investigator
DependenciesAPI DocsStandardsCompliancePatternsComponentsConventionsSchema

Create PRD

/karimo:plan

Interviewer
PRD-Feature-001
Interview Protocol|customizable

Task Briefs

/karimo:run

Brief WriterPM
PRD-Task-001PRD-Task-002PRD-Task-003PRD-Task-004PRD-Task-005PRD-Task-006PRD-Task-007PRD-Task-008PRD-Task-009PRD-Task-010PRD-Task-011PRD-Task-012

Dependency Graph

tasks.yaml

PMReviewer
W1
W2
W3
W4

Planning Phase

You are the architect. Research discovers external dependencies, standards, and internal patterns. You can layer in your own research, upload screenshots, and collect assets in a PRD folder. A structured interview captures your requirements into a PRD. Task briefs and a dependency graph are generated automatically.

How It Works

  • Research scans external deps, API docs, standards + internal patterns, components, conventions — layer in your own research and assets
  • Structured PRD interview captures requirements (~10 min via /karimo:plan)
  • Task briefs generated from research + PRD artifacts
  • Dependency graph maps execution order into parallelizable waves

Thoughtful Architecture

In plan mode, you get a single 1M-token session that is static, flat, and isolated. KARIMO expands that into progressive, compounding context through progressive disclosure, context multiplication, and compound learning. Agents only load what they need, every session builds on the last, and feedback persists across every future PRD.

DURATIONCOMPLEXITY22446688Plan ModeOpus 4.6KARIMOOpus 4.6KARIMOMythos
KARIMO

Context Compression

Each stage distills context into artifacts optimized for the next session. A 1M token window becomes a building block across multiple sessions with shared information and objectives.

Effective context10–100M effective

1M × tasks × research depth

Part 1

Progressive Disclosure

Built on the OpenViking protocol — agents load abstracts first, overviews second, and full definitions only when executing. No wasted tokens.

KARIMO_RULES.md
# KARIMO Abstracts
 
karimo-pm → orchestration
karimo-implementer → code (≤4)
karimo-implementer-opus → code (5+)
karimo-interviewer → PRD interviews
karimo-brief-writer → task briefs
karimo-reviewer → PRD validation
...22 agents total
context budget~100 / 1M

One-line summaries per agent, command, and skill. Used to verify items exist before loading more. Near-zero cost.

Agent namesCommand signaturesSkill identifiers
Part 2

Context Compression

Each stage distills context into artifacts optimized for the next session. A 1M token window becomes a building block across multiple sessions with shared information and objectives.

Scans your codebase and the web. Produces findings.md — patterns, conventions, and external context that agents would otherwise have to rediscover.

findings.mdconventionsAPI docs
Part 3

Compound Learning

At any point, run /karimo:feedback to capture issues or potential improvements. Observations move through a capture stage, then get stored as summarized learnings in the KARIMO learnings folder — patterns that work, anti-patterns to avoid, execution rules, and product-specific notes. These compound over time: every future PRD and task brief loads in relevant learnings for that specific task. Agents never repeat the same mistake twice.

Open source — contribute on GitHub to help improve KARIMO as models evolve.

Three Simple Steps

Set up your environment so AI can quickly work as a cheat sheet. Run your first research — 8 documents generated for internal and external resources. Then kick off an interview to create a PRD that gets decomposed into tasks.

Auto-detect project configInternal + external research8 generated documentsPRD interview → task decomposition
Objective

Feel the difference between prompting and orchestrating

Step 1
$ /karimo:configure
◆ Auto-detecting project...
Config: .karimo/config.yaml ✓
 
$ /karimo:research
 
◆ Scanning 847 files...
8 documents generated ✓
 
$ /karimo:plan
 
◆ Interview complete
PRD: auth-system
12 tasks across 4 waves
→ Ready to run

Frequently Asked Questions

Get started today

OPTION 1Terminal

Clone the repo and run the install script from your terminal.

$ git clone https://github.com/opensesh/KARIMO
$ bash KARIMO/.karimo/install.sh ./my-project
View on GitHub
OPTION 2Claude Code

Paste this prompt into Claude Code and it will handle the rest.

Clone github.com/opensesh/KARIMO and run the install script to set up KARIMO in this project.

Works in Claude Code CLI, desktop app, or IDE extensions.