![\"Claude](\"docs/images/claude-harness-logo-with-text.png\"){kind=logo}
\n\n \n
\n Plan. Work. Review. Ship.
\n Turn Claude Code into a disciplined development partner.\n
\n ![\"Version\"](\"https://img.shields.io/badge/version-2.20.8-blue.svg\"){kind=icon}
\n ![\"License\"](\"https://img.shields.io/badge/License-MIT-green.svg\"){kind=icon}
\n ![\"Claude](\"https://img.shields.io/badge/Claude_Code-v2.1+-purple.svg\"){kind=icon}
\n ![\"Skills\"](\"https://img.shields.io/badge/Skills-45-orange.svg\"){kind=icon}
\n
\n English | 日本語\n
\n\n---\n\n## Why Harness?\n\nClaude Code is powerful—but sometimes it needs structure.\n\n| Without Harness | With Harness |\n|-----------------|--------------|\n| Jumps into code immediately | Plans first, then executes |\n| Reviews only when asked | Auto-reviews every change |\n| Forgets past decisions | SSOT files preserve context |\n| `rm -rf` runs without warning | Dangerous commands blocked |\n| One task at a time | Parallel workers |\n\n**Three commands. One workflow. Production-ready code.**\n\n```mermaid\ngraph LR\n A[Your Idea] --> B[\"/plan-with-agent\"]\n B --> C[\"Plans.md\"]\n C --> D[\"/work\"]\n D --> E[\"Code + Self-Review\"]\n E --> F[\"/harness-review\"]\n F --> G[\"Ship It\"]\n```\n\n---\n\n## Requirements\n\n- **Claude Code v2.1+** ([Install Guide](https://docs.anthropic.com/claude-code))\n- **Node.js 18+** (for safety hooks)\n\n---\n\n## Install in 30 Seconds\n\n```bash\n# Start Claude Code in your project\nclaude\n\n# Add the marketplace & install\n/plugin marketplace add Chachamaru127/claude-code-harness\n/plugin install claude-code-harness@claude-code-harness-marketplace\n\n# Initialize your project\n/harness-init\n```\n\nThat's it. Start with `/plan-with-agent`.\n\n---\n\n## Codex CLI Setup\n\nCodex reads MCP servers from your **global** `~/.codex/config.toml`. Let the\nharness manage the single `[mcp_servers.harness]` block there:\n\n```bash\n/path/to/claude-code-harness/scripts/setup-codex.sh\n```\n\nClaude Code users can run `/setup codex` to apply it without leaving the session.\n\n> **Do not copy `config.toml` into a repo-local `.codex/`.** Codex merges a\n> project-local `.codex/config.toml` with the global one on the same\n> `[mcp_servers.harness]` key. If the two disagree on transport (stdio\n> `command` vs http `url`), Codex refuses to start with\n> `url is not supported for stdio`. Keep the harness MCP server defined only in\n> the global config.\n\nProject-scoped files that are safe to copy: `codex/AGENTS.md` into your project\nroot, and `codex/.codex/rules/` for harness rules. These contain no MCP server\ndefinition, so they never collide with the global config.\n\nUse `$plan-with-agent`, `$work`, `$harness-review` to run the workflow.\n\n## Unified Memory Setup (Claude/Codex/OpenCode shared)\n\n```bash\n# from your project\n/path/to/claude-code-harness/scripts/harness-mem setup\n```\n\nThis wires platform adapters, starts `harness-memd`, and runs smoke + search quality checks.\n\n---\n\n## 🪄 TL;DR: Work All\n\n**Don't want to read all this?** Just type:\n\n```\n/work all\n```\n\n**One command. Harness does the rest.** Plan → Parallel Implementation → Review → Commit.\n\n```mermaid\ngraph LR\n A[\"/work all\"] --> B[\"Generate Plan\"]\n B --> C[\"Parallel Implementation\"]\n C --> D[\"Self-Review\"]\n D --> E[\"Quality Gate\"]\n E --> F[\"Auto-Commit\"]\n```\n\n| Before | After |\n|--------|-------|\n| `/plan-with-agent` → `/work` → `/harness-review` → `git commit` | `/work all` |\n| 4 commands | **1** |\n\n> ⚠️ **Experimental**: Once you approve the plan, Claude runs to completion. Quality gate blocks commit if issues found.\n\n---\n\n## The Core Loop (Details)\n\n### 1. Plan\n\n```bash\n/plan-with-agent\n```\n\n> \"I want a login form with email validation\"\n\nHarness creates `Plans.md` with clear acceptance criteria.\n\n### 2. Work\n\n```bash\n/work # Auto-detect parallelism\n/work --parallel 5 # 5 workers simultaneously\n```\n\nEach worker implements, self-reviews, and reports.\n\n### 3. Review\n\n```bash\n/harness-review\n```\n\n| Perspective | Focus |\n|-------------|-------|\n| Security | Vulnerabilities, injection, auth |\n| Performance | Bottlenecks, memory, scaling |\n| Quality | Patterns, naming, maintainability |\n| Accessibility | WCAG compliance, screen readers |\n\n---\n\n## Safety First\n\nHarness protects your codebase with hooks:\n\n| Protected | Action |\n|-----------|--------|\n| `.git/`, `.env`, secrets | Write blocked |\n| `rm -rf`, `sudo`, `--force` | Confirmation required |\n| `git status`, `npm test` | Auto-allowed |\n| Test tampering | Warning triggered |\n\n---\n\n## 45 Skills, Zero Config\n\nSkills auto-load based on context. Use slash commands or natural language.\n\n| Say This | Skill |\n|----------|-------|\n| \"implement login\" | `impl` |\n| \"review this code\" | `harness-review` |\n| \"fix the build error\" | `verify` |\n| \"add Stripe payments\" | `auth` |\n| \"deploy to Vercel\" | `deploy` |\n\n### Key Commands\n\n| Command | What It Does |\n|---------|--------------|\n| `/plan-with-agent` | Ideas → `Plans.md` |\n| `/work` | Execute tasks in parallel |\n| `/harness-review` | 4-perspective review |\n| `/harness-init` | Initialize project |\n| `/sync-status` | Check progress |\n| `/memory` | Manage SSOT files |\n\n---\n\n## Who Is This For?\n\n| You Are | Harness Helps You |\n|---------|-------------------|\n| **Developer** | Ship faster with built-in QA |\n| **Freelancer** | Deliver review reports to clients |\n| **Indie Hacker** | Move fast without breaking things |\n| **VibeCoder** | Build apps with natural language |\n| **Team Lead** | Enforce standards across projects |\n\n---\n\n## Architecture\n\n```\nclaude-code-harness/\n├── skills/ # 45 skill definitions\n├── agents/ # 8 sub-agents (parallel workers)\n├── hooks/ # Safety & automation\n├── scripts/ # Guard scripts\n└── templates/ # Generation templates\n```\n\n---\n\n## Advanced Features\n\n