@howlil/ez-agents 3.0.0 → 3.4.1

package/README.md

@@ -2,891 +2,472 @@
 
 # EZ Agents
 
-**ez-agents** — *Meta-prompting & Agent Orchestration, but ez*
+**Turn AI coding assistants into reliable development teammates.**
 
-**English** · [简体中文](README.zh-CN.md)
-
-**An independent fork of EZ Agents (Get Shit Done) with multi-model support (Qwen, Kimi, OpenAI, Claude) and enhanced reliability features.**
-
-**Solves context rot — with added security, error handling, and cross-platform support.**
-
-[![GitHub forks](https://img.shields.io/github/forks/howlil/ez-agents?style=for-the-badge&logo=github&color=blue)](https://github.com/howlil/ez-agents/network)
-[![GitHub stars](https://img.shields.io/github/stars/howlil/ez-agents?style=for-the-badge&logo=github&color=yellow)](https://github.com/howlil/ez-agents/stargazers)
+[![npm](https://img.shields.io/npm/v/@howlil/ez-agents?style=for-the-badge&logo=npm)](https://www.npmjs.com/package/@howlil/ez-agents)
 [![License](https://img.shields.io/badge/license-MIT-blue?style=for-the-badge)](LICENSE)
-
-<br>
+[![GitHub stars](https://img.shields.io/github/stars/howlil/ez-agents?style=for-the-badge&logo=github)](https://github.com/howlil/ez-agents/stargazers)
 
 ```bash
 npm install -g git+https://github.com/howlil/ez-agents.git
 ```
 
-**Works on Mac, Windows, and Linux.**
-
-<br>
-
-**Original EZ Agents (Get Shit Done) by** [TÂCHES](https://github.com/glittercowboy/ez-agents) | **EZ Agents Fork by** [@howlil](https://github.com/howlil)
-
-<br>
-
-*"If you know clearly what you want, this WILL build it for you. No bs."*
-
-*"I've done SpecKit, OpenSpec and Taskmaster — this has produced the best results for me."*
+**Works with:** Claude Code · OpenCode · Gemini CLI · Codex · Copilot · Qwen · Kimi
 
-*"By far the most powerful addition to my Claude Code. Nothing over-engineered. Literally ez mode activated."*
-
-<br>
-
-[Features](#-whats-new-in-ez-agents) · [Install](#install) · [Commands](#commands) · [Multi-Model](#multi-model-support) · [User Guide](docs/USER-GUIDE.md)
+[Quick Start](#quick-start) · [How It Works](#how-it-works) · [Commands](#commands) · [Setup](#setup) · [Docs](docs/)
 
 </div>
 
 ---
 
-## 🚀 What's New in EZ Agents
-
-> **Note:** This is an **independent fork** of EZ Agents (Get Shit Done). Not affiliated with the original EZ Agents project.
->
-> **Original EZ Agents (Get Shit Done):** [glittercowboy/ez-agents](https://github.com/glittercowboy/ez-agents) by TÂCHES
->
-> **This Fork:** [howlil/ez-agents](https://github.com/howlil/ez-agents) with multi-model support & enhancements
-
-**EZ Agents** adds **multi-model support** and **enterprise-grade reliability** to EZ Agents (Get Shit Done).
-
-### Why This Fork Exists
+> **What is this?** EZ Agents adds structure to AI coding. Instead of asking Claude to "build a login system" and hoping for the best, you get a repeatable workflow: plan it out, build it in pieces, verify it works. Every change is committed with context, so you (or your team) can pick up where the AI left off.
 
-I needed EZ Agents (Get Shit Done) to work with multiple AI providers (not just Anthropic) and run reliably on Windows. This fork adds:
+---
 
-- 🌍 **Multi-Model**: Qwen (Alibaba), Kimi (Moonshot), OpenAI, and Anthropic
-- 🔒 **Security**: Command injection prevention, path validation, audit logging
-- 🛡️ **Error Handling**: Retry with backoff, circuit breaker for failing operations
-- 🪟 **Windows Support**: Cross-platform file utilities (no Unix dependencies)
-- 🔄 **Easy Updates**: `ez-agents-update` command to stay current
+## Why EZ Agents Exists
 
-### Features Comparison
+AI coding tools are great at writing code. But real development work needs more than that:
 
-| Feature | Original EZ Agents (Get Shit Done) | EZ Agents Fork |
-|---------|------------------------------|-----------|
-| **Multi-Model** | Anthropic only | ✓ Anthropic, Qwen, Kimi, OpenAI |
-| **Security** | Basic | ✓ Command allowlist, path validation, audit log |
-| **Error Handling** | Basic | ✓ Retry with backoff, circuit breaker |
-| **Cross-Platform** | Unix commands | ✓ Pure JavaScript (Windows-safe) |
-| **Git Safety** | Direct calls | ✓ Atomic commits, branch automation |
-| **Update Command** | Manual npm | ✓ `ez-agents-update` |
-| **Credential Storage** | Plain text | ✓ System keychain (keytar) |
+- **Context gets lost** between sessions
+- **No one reviews** whether the code actually fits the plan
+- **Important decisions** about architecture happen implicitly
+- **Testing is an afterthought**
 
-### 17 New Libraries
+EZ Agents fixes this by adding a lightweight orchestration layer. Think of it as a project manager for your AI assistants.
 
-```
-ez-agents/bin/lib/
-├── safe-exec.cjs         # Command injection prevention (allowlist + validation)
-├── safe-path.cjs         # Path traversal prevention
-├── auth.cjs              # Secure credential storage (keytar + fallback)
-├── audit-exec.cjs        # Command audit logging (.planning/logs/)
-├── git-utils.cjs         # Safe git operations (atomic commits)
-├── fs-utils.cjs          # Cross-platform file utils (find/grep/head/tail replacement)
-├── retry.cjs             # Exponential backoff retry logic
-├── circuit-breaker.cjs   # Prevent cascading failures
-├── model-provider.cjs    # Multi-model API abstraction
-├── assistant-adapter.cjs # AI assistant abstraction (Claude/OpenCode/Gemini/Codex)
-├── logger.cjs            # Centralized logging (ERROR/WARN/INFO/DEBUG)
-├── health-check.cjs      # Environment validation
-├── timeout-exec.cjs      # Command timeout with fallback
-├── file-lock.cjs         # Concurrent write protection
-├── temp-file.cjs         # Secure temp file handling
-├── index.cjs             # Central library export
-└── update.js             # ez-agents-update command
-```
+---
 
-### Multi-Model Support
+## Quick Start
 
-Configure different AI providers per agent:
+### 1. Install
 
-```json
-// .planning/config.json
-{
-  "provider": {
-    "default": "alibaba",
-    "anthropic": {
-      "api_key": "env:ANTHROPIC_API_KEY",
-      "models": { "opus": "claude-3-opus-20240229", "sonnet": "claude-3-sonnet-20240229" }
-    },
-    "alibaba": {
-      "api_key": "env:DASHSCOPE_API_KEY",
-      "models": { "high": "qwen-max", "balanced": "qwen-plus" }
-    },
-    "moonshot": {
-      "api_key": "env:MOONSHOT_API_KEY",
-      "models": { "high": "moonshot-v1-128k" }
-    },
-    "openai": {
-      "api_key": "env:OPENAI_API_KEY",
-      "models": { "high": "gpt-4-turbo-preview" }
-    }
-  },
-  "agent_overrides": {
-    "ez-planner": { "provider": "alibaba", "model": "qwen-max" },
-    "ez-executor": { "provider": "anthropic", "model": "sonnet" },
-    "ez-verifier": { "provider": "moonshot", "model": "balanced" }
-  }
-}
+```bash
+npm install -g git+https://github.com/howlil/ez-agents.git
 ```
 
-### Quick Commands
+### 2. Setup for Your AI Tool
 
 ```bash
-# Install EZ Agents
-npm install -g ez-agents
-
-# Setup (Claude Code)
+# For Claude Code
 ez-agents --claude --global
 
-# Update
-ez-agents-update
-
-# Force update
-ez-agents-update --force
+# For OpenCode
+ez-agents --opencode --global
 
-# Check version
-ez-agents --version
+# For Gemini CLI
+ez-agents --gemini --global
 
-# Help
+# See all options
 ez-agents --help
 ```
 
-### Install
-
-**⚠️ Important: Use one of the methods below. Do NOT use `npx github:howlil/ez-agents` as it may fail.**
-
-**Option 1: Install from GitHub (Recommended)**
+### 3. Start a Project
 
 ```bash
-# Install globally from GitHub
-npm install -g git+https://github.com/howlil/ez-agents.git
-
-# Then run installer
-ez-agents --claude --global
+# In your project directory
+/ez:new-project
 ```
 
-**Option 2: Use npx (No Installation)**
+You'll answer a few questions about what you're building, then EZ Agents generates a roadmap. From there, you work through phases:
 
 ```bash
-# Run installer directly without installing
-npx @howlil/ez-agents --claude --global
+/ez:discuss-phase 1    # Lock in how you want it built
+/ez:plan-phase 1       # Break it into specific tasks
+/ez:execute-phase 1    # Build it (one task per commit)
+/ez:verify-work 1      # Check it actually works
 ```
 
-**Option 3: Install from npm**
+---
 
-```bash
-# Install from npm registry
-npm install -g @howlil/ez-agents
+## How It Works
 
-# Then use
-ez-agents --claude --global
-ez-agents-update
-```
+### The Workflow
+
+```
+┌─────────────────┐
+│  Start Project  │
+│  /ez:new-project│
+└────────┬────────┘
+         │
+         ▼
+┌─────────────────────────────────────────────────┐
+│  For Each Phase:                                │
+│                                                 │
+│  1. /ez:discuss-phase  → Decide HOW to build   │
+│  2. /ez:plan-phase     → Break into tasks      │
+│  3. /ez:execute-phase  → Build (one commit/task)│
+│  4. /ez:verify-work    → Test it works         │
+└─────────────────────────────────────────────────┘
+         │
+         ▼
+┌─────────────────────────┐
+│  /ez:audit-milestone    │
+│  /ez:complete-milestone │
+└─────────────────────────┘
+```
+
+### Parallel Execution with Git Commits
+
+Setiap task dijalankan secara paralel (jika tidak ada dependensi), dengan fresh context dan atomic commit:
+
+```
+Phase 1: Foundation
+│
+├─ Wave 1 (Parallel) ───────────────────────────┐
+│  ┌─────────────────┐  ┌─────────────────┐     │
+│  │ Task 1.1:       │  │ Task 1.2:       │     │
+│  │ Database Schema │  │ Next.js Setup   │     │
+│  │                 │  │                 │     │
+│  │ Fresh 200K ctx  │  │ Fresh 200K ctx  │     │
+│  │     ↓           │  │     ↓           │     │
+│  │ git commit      │  │ git commit      │     │
+│  │ "feat: schema"  │  │ "feat: setup"   │     │
+│  └─────────────────┘  └─────────────────┘     │
+└────────────────────────────────────────────────┘
+         │
+         ▼
+├─ Wave 2 (Depends on Wave 1) ──────────────────┐
+│  ┌─────────────────┐                          │
+│  │ Task 1.3:       │                          │
+│  │ Auth Endpoints  │  ← Needs schema + setup  │
+│  │                 │                          │
+│  │ Fresh 200K ctx  │                          │
+│  │     ↓           │                          │
+│  │ git commit      │                          │
+│  │ "feat: auth"    │                          │
+│  └─────────────────┘                          │
+└────────────────────────────────────────────────┘
+```
+
+**Keuntungan:**
+- **Fresh context per task** — AI tidak kehilangan context karena window penuh
+- **Atomic commits** — Setiap commit = satu task, mudah di-revert jika ada masalah
+- **Parallel execution** — Task independen jalan barengan, lebih cepat
+- **Clean git history** — Commit message deskriptif, jelas apa yang berubah
+
+### What Makes It Different
+
+| Problem | Without EZ Agents | With EZ Agents |
+|---------|------------------|----------------|
+| **Lost context** | "What was I working on again?" | STATE.md tracks decisions, blockers, next steps |
+| **Vague plans** | "Build the API" | Specific tasks: "Create POST /users endpoint with validation" |
+| **No verification** | Code written, but does it work? | Each phase has explicit verification criteria |
+| **Messy git history** | "WIP", "fix", "asdf" | One commit per task, meaningful messages |
+| **Scope creep** | Features added ad-hoc | ROADMAP.md tracks what's in/out of scope |
 
-**Option 4: Install from Local Source (Development)**
+---
 
-```bash
-# Clone the repository
-git clone https://github.com/howlil/ez-agents.git
-cd ez-agents
+## Features
 
-# Install globally from local directory
-npm install -g .
+### Core
 
-# Then use
-ez-agents --claude --global
-```
+- **Multi-Model Support** — Use Qwen, Kimi, OpenAI, or Anthropic. Mix providers per task.
+- **Wave Execution** — Independent tasks run in parallel; dependent tasks wait their turn
+- **Context Engineering** — PROJECT.md, STATE.md, SUMMARY.md preserve decisions across sessions
+- **Atomic Commits** — Each task gets its own commit with context about what changed and why
+- **Milestone Tracking** — Version releases with requirements audit and git tagging
 
----
+### Built for Production
 
-**Installation Commands Reference:**
+- **Security** — Command injection prevention, path validation, audit logging
+- **Cross-Platform** — Pure JavaScript. Works on Windows, macOS, Linux (no Unix dependencies)
+- **Error Handling** — Retry logic with backoff, circuit breaker for failing operations
+- **Git Safety** — Atomic commits, branch automation, merge strategies
+
+### For Existing Codebases
 
 ```bash
-# Install EZ Agents globally
-npm install -g git+https://github.com/howlil/ez-agents.git
+# Analyze what you have
+/ez:map-codebase
 
-# Setup for Claude Code (global)
-ez-agents --claude --global
+# Then plan what to add
+/ez:new-project
+```
 
-# Setup for Claude Code (local project)
-ez-agents --claude --local
+Parallel agents analyze your stack, architecture, conventions, and pain points. The output: structured docs that inform the roadmap.
 
-# Setup for all runtimes (Claude, OpenCode, Gemini, Codex, Copilot)
-ez-agents --all --global
+---
 
-# Update EZ Agents
-ez-agents-update
+## Commands
 
-# Force reinstall
-ez-agents-update --force
+### Starting Out
 
-# Check version
-ez-agents --version
+| Command | What It Does |
+|---------|-------------|
+| `/ez:new-project` | Initialize: answer questions, get research, requirements, and roadmap |
+| `/ez:map-codebase` | Analyze existing codebase (before `/ez:new-project`) |
+| `/ez:quick` | Small task without full phase workflow (bug fixes, config changes) |
 
-# Help
-ez-agents --help
+### Phase Workflow
 
-# Uninstall
-ez-agents --all --global --uninstall
-```
+| Command | What It Does |
+|---------|-------------|
+| `/ez:discuss-phase [N]` | Clarify implementation approach before planning |
+| `/ez:plan-phase [N]` | Research domain, create task breakdown, define verification |
+| `/ez:execute-phase [N]` | Build the plan (parallel waves, one commit per task) |
+| `/ez:verify-work [N]` | Manual testing with auto-diagnosis of failures |
 
-I'm a solo developer. I don't write code — Claude Code does.
+### Managing Scope
 
-Other spec-driven development tools exist; BMAD, Speckit... But they all seem to make things way more complicated than they need to be (sprint ceremonies, story points, stakeholder syncs, retrospectives, Jira workflows) or lack real big picture understanding of what you're building. I'm not a 50-person software company. I don't want to play enterprise theater. I'm just a creative person trying to build great things that work.
+| Command | What It Does |
+|---------|-------------|
+| `/ez:add-phase` | Append new phase to roadmap |
+| `/ez:insert-phase [N]` | Insert urgent work between existing phases |
+| `/ez:remove-phase [N]` | Remove a phase and renumber |
+| `/ez:progress` | See where you are and what's next |
 
-So I built EZ Agents. The complexity is in the system, not in your workflow. Behind the scenes: context engineering, XML prompt formatting, subagent orchestration, state management. What you see: a few commands that just work.
+### Wrapping Up
 
-The system gives Claude everything it needs to do the work *and* verify it. I trust the workflow. It just does a good job.
+| Command | What It Does |
+|---------|-------------|
+| `/ez:audit-milestone` | Verify all requirements are met |
+| `/ez:complete-milestone` | Archive milestone, create git tag |
+| `/ez:new-milestone` | Start next version cycle |
 
-That's what this is. No enterprise roleplay bullshit. Just an incredibly effective system for building cool stuff consistently using Claude Code.
+### Utilities
 
-— **TÂCHES**
+| Command | What It Does |
+|---------|-------------|
+| `/ez:resume-work` | Restore context from last session |
+| `/ez:settings` | Configure workflow, model profile, git strategy |
+| `/ez:update` | Update EZ Agents (with changelog preview) |
+| `/ez:help` | Show all commands |
 
 ---
 
-Vibecoding has a bad reputation. You describe what you want, AI generates code, and you get inconsistent garbage that falls apart at scale.
+## Setup
 
-EZ Agents fixes that. It's the context engineering layer that makes Claude Code reliable. Describe your idea, let the system extract everything it needs to know, and let Claude Code get to work.
+### Prerequisites
 
----
-
-## Who This Is For
+- Node.js >= 16.7.0
+- One of: Claude Code, OpenCode, Gemini CLI, Codex, Copilot, Qwen Code, Kimi Code
 
-People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
+### Installation Options
 
----
-
-## Getting Started
+**From GitHub (Recommended)**
 
 ```bash
-npx ez-agents
+npm install -g git+https://github.com/howlil/ez-agents.git
+ez-agents --claude --global
 ```
 
-The installer prompts you to choose:
-1. **Runtime** — Claude Code, OpenCode, Gemini, Codex, Copilot, or all
-2. **Location** — Global (all projects) or local (current project only)
-
-Verify with:
-- Claude Code / Gemini: `/ez:help`
-- OpenCode: `/ez-help`
-- Codex: `$ez-help`
-
-> [!NOTE]
-> Codex installation uses skills (`skills/ez-*/SKILL.md`) rather than custom prompts.
-
-### Staying Updated
-
-EZ Agents evolves fast. Update periodically:
+**From npm**
 
 ```bash
-ez-agents-update
+npm install -g @howlil/ez-agents
+ez-agents --claude --global
 ```
 
-<details>
-<summary><strong>Non-interactive Install (Docker, CI, Scripts)</strong></summary>
+**Development Install**
 
 ```bash
-# Claude Code
-ez-agents --claude --global   # Install to ~/.claude/
-ez-agents --claude --local    # Install to ./.claude/
-
-# OpenCode (open source, free models)
-ez-agents --opencode --global # Install to ~/.config/opencode/
-
-# Gemini CLI
-ez-agents --gemini --global   # Install to ~/.gemini/
-
-# Codex (skills-first)
-ez-agents --codex --global    # Install to ~/.codex/
-ez-agents --codex --local     # Install to ./.codex/
-
-# All runtimes
-ez-agents --all --global      # Install to all directories
+git clone https://github.com/howlil/ez-agents.git
+cd ez-agents
+npm install -g .
+ez-agents --claude --local
 ```
 
-Use `--global` (`-g`) or `--local` (`-l`) to skip the location prompt.
-Use `--claude`, `--opencode`, `--gemini`, `--codex`, or `--all` to skip the runtime prompt.
+### Updating
 
-</details>
+```bash
+ez-agents-update
+```
 
-<details>
-<summary><strong>Development Installation</strong></summary>
+Shows changelog before installing. If you have local modifications, they're backed up and can be reapplied with `/ez:reapply-patches`.
 
-Clone the repository and run the installer locally:
+---
 
-```bash
-git clone https://github.com/howlil/ez-agents.git
-cd ez-agents
-node bin/install.js --claude --local
-```
+## Configuration
 
-Installs to `./.claude/` for testing modifications before contributing.
+EZ Agents stores settings in `.planning/config.json`. You configure this during `/ez:new-project` or adjust later with `/ez:settings`.
 
-</details>
+### Key Settings
 
-### Recommended: Skip Permissions Mode
+| Setting | Options | Default | What It Does |
+|---------|---------|---------|-------------|
+| `mode` | `interactive`, `yolo` | `interactive` | `yolo` skips confirmation prompts |
+| `model_profile` | `quality`, `balanced`, `budget` | `balanced` | Controls which model tier each agent uses |
+| `granularity` | `coarse`, `standard`, `fine` | `standard` | How many phases (3-5, 5-8, or 8-12) |
 
-EZ Agents is designed for frictionless automation. Run Claude Code with:
+### Model Profiles
 
-```bash
-claude --dangerously-skip-permissions
-```
+| Agent | `quality` | `balanced` | `budget` |
+|-------|-----------|------------|----------|
+| Planner | Opus | Opus | Sonnet |
+| Executor | Opus | Sonnet | Sonnet |
+| Researcher | Opus | Sonnet | Haiku |
+| Verifier | Sonnet | Sonnet | Haiku |
 
-> [!TIP]
-> This is how EZ Agents is intended to be used — stopping to approve `date` and `git commit` 50 times defeats the purpose.
+**When to use each:**
+- **quality** — Critical work, complex decisions, you have quota
+- **balanced** — Day-to-day development (the default for a reason)
+- **budget** — High-volume work, familiar domains, prototyping
 
-<details>
-<summary><strong>Alternative: Granular Permissions</strong></summary>
+### Multi-Provider Setup
 
-If you prefer not to use that flag, add this to your project's `.claude/settings.json`:
+Different providers for different tasks:
 
 ```json
 {
-  "permissions": {
-    "allow": [
-      "Bash(date:*)",
-      "Bash(echo:*)",
-      "Bash(cat:*)",
-      "Bash(ls:*)",
-      "Bash(mkdir:*)",
-      "Bash(wc:*)",
-      "Bash(head:*)",
-      "Bash(tail:*)",
-      "Bash(sort:*)",
-      "Bash(grep:*)",
-      "Bash(tr:*)",
-      "Bash(git add:*)",
-      "Bash(git commit:*)",
-      "Bash(git status:*)",
-      "Bash(git log:*)",
-      "Bash(git diff:*)",
-      "Bash(git tag:*)"
-    ]
+  "provider": {
+    "default": "alibaba",
+    "anthropic": {
+      "api_key": "env:ANTHROPIC_API_KEY"
+    },
+    "alibaba": {
+      "api_key": "env:DASHSCOPE_API_KEY"
+    }
+  },
+  "agent_overrides": {
+    "ez-planner": { "provider": "alibaba", "model": "qwen-max" },
+    "ez-executor": { "provider": "anthropic", "model": "sonnet" }
   }
 }
 ```
 
-</details>
-
 ---
 
-## How It Works
-
-> **Already have code?** Run `/ez:map-codebase` first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then `/ez:new-project` knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.
+## Project Structure
 
-### 1. Initialize Project
+After running `/ez:new-project`, you'll have:
 
 ```
-/ez:new-project
+.planning/
+  PROJECT.md           # What you're building and why
+  REQUIREMENTS.md      # Scoped requirements with IDs
+  ROADMAP.md           # Phase breakdown with status
+  STATE.md             # Current decisions, blockers, next steps
+  config.json          # Your configuration
+  phases/
+    01-phase-name/
+      01-01-PLAN.md    # Tasks to execute
+      01-01-SUMMARY.md # What was built and why
+      CONTEXT.md       # Your implementation preferences
+      RESEARCH.md      # Domain research
+      VERIFICATION.md  # Test results
 ```
 
-One command, one flow. The system:
-
-1. **Questions** — Asks until it understands your idea completely (goals, constraints, tech preferences, edge cases)
-2. **Research** — Spawns parallel agents to investigate the domain (optional but recommended)
-3. **Requirements** — Extracts what's v1, v2, and out of scope
-4. **Roadmap** — Creates phases mapped to requirements
-
-You approve the roadmap. Now you're ready to build.
-
-**Creates:** `PROJECT.md`, `REQUIREMENTS.md`, `ROADMAP.md`, `STATE.md`, `.planning/research/`
+**Note:** You can add `.planning/` to `.gitignore` if you don't want planning docs in your repo. Set `commit_docs: false` in `/ez:settings`.
 
 ---
 
-### 2. Discuss Phase
-
-```
-/ez:discuss-phase 1
-```
+## Example: Building a Task App
 
-**This is where you shape the implementation.**
+Let's say you want to build "a task management app with team collaboration."
 
-Your roadmap has a sentence or two per phase. That's not enough context to build something the way *you* imagine it. This step captures your preferences before anything gets researched or planned.
+### 1. Initialize
 
-The system analyzes the phase and identifies gray areas based on what's being built:
-
-- **Visual features** → Layout, density, interactions, empty states
-- **APIs/CLIs** → Response format, flags, error handling, verbosity
-- **Content systems** → Structure, tone, depth, flow
-- **Organization tasks** → Grouping criteria, naming, duplicates, exceptions
-
-For each area you select, it asks until you're satisfied. The output — `CONTEXT.md` — feeds directly into the next two steps:
+```bash
+/ez:new-project
+```
 
-1. **Researcher reads it** — Knows what patterns to investigate ("user wants card layout" → research card component libraries)
-2. **Planner reads it** — Knows what decisions are locked ("infinite scroll decided" → plan includes scroll handling)
+You answer questions:
+- Tech stack? → "Next.js + PostgreSQL"
+- Auth method? → "Email + OAuth (Google, GitHub)"
+- First milestone? → "MVP: user accounts, create/edit tasks, share with team"
 
-The deeper you go here, the more the system builds what you actually want. Skip it and you get reasonable defaults. Use it and you get *your* vision.
+EZ Agents generates research, requirements, and a roadmap with ~6 phases.
 
-**Creates:** `{phase_num}-CONTEXT.md`
+### 2. Phase 1: Foundation
 
----
+```bash
+/ez:discuss-phase 1
+```
 
-### 3. Plan Phase
+You clarify: "Use Next.js App Router, Prisma for DB, next-auth for OAuth."
 
-```
+```bash
 /ez:plan-phase 1
 ```
 
-The system:
-
-1. **Researches** — Investigates how to implement this phase, guided by your CONTEXT.md decisions
-2. **Plans** — Creates 2-3 atomic task plans with XML structure
-3. **Verifies** — Checks plans against requirements, loops until they pass
-
-Each plan is small enough to execute in a fresh context window. No degradation, no "I'll be more concise now."
-
-**Creates:** `{phase_num}-RESEARCH.md`, `{phase_num}-{N}-PLAN.md`
-
----
-
-### 4. Execute Phase
+Research runs (auth patterns, Prisma schema design). Plan is created:
+- Task 1: Database schema (users, tasks, teams)
+- Task 2: Next.js setup with next-auth
+- Task 3: User model and auth endpoints
 
-```
+```bash
 /ez:execute-phase 1
 ```
 
-The system:
-
-1. **Runs plans in waves** — Parallel where possible, sequential when dependent
-2. **Fresh context per plan** — 200k tokens purely for implementation, zero accumulated garbage
-3. **Commits per task** — Every task gets its own atomic commit
-4. **Verifies against goals** — Checks the codebase delivers what the phase promised
-
-Walk away, come back to completed work with clean git history.
-
-**How Wave Execution Works:**
-
-Plans are grouped into "waves" based on dependencies. Within each wave, plans run in parallel. Waves run sequentially.
-
-```
-┌────────────────────────────────────────────────────────────────────┐
-│  PHASE EXECUTION                                                   │
-├────────────────────────────────────────────────────────────────────┤
-│                                                                    │
-│  WAVE 1 (parallel)          WAVE 2 (parallel)          WAVE 3      │
-│  ┌─────────┐ ┌─────────┐    ┌─────────┐ ┌─────────┐    ┌─────────┐ │
-│  │ Plan 01 │ │ Plan 02 │ →  │ Plan 03 │ │ Plan 04 │ →  │ Plan 05 │ │
-│  │         │ │         │    │         │ │         │    │         │ │
-│  │ User    │ │ Product │    │ Orders  │ │ Cart    │    │ Checkout│ │
-│  │ Model   │ │ Model   │    │ API     │ │ API     │    │ UI      │ │
-│  └─────────┘ └─────────┘    └─────────┘ └─────────┘    └─────────┘ │
-│       │           │              ↑           ↑              ↑      │
-│       └───────────┴──────────────┴───────────┘              │      │
-│              Dependencies: Plan 03 needs Plan 01            │      │
-│                          Plan 04 needs Plan 02              │      │
-│                          Plan 05 needs Plans 03 + 04        │      │
-│                                                                    │
-└────────────────────────────────────────────────────────────────────┘
-```
-
-**Why waves matter:**
-- Independent plans → Same wave → Run in parallel
-- Dependent plans → Later wave → Wait for dependencies
-- File conflicts → Sequential plans or same plan
-
-This is why "vertical slices" (Plan 01: User feature end-to-end) parallelize better than "horizontal layers" (Plan 01: All models, Plan 02: All APIs).
-
-**Creates:** `{phase_num}-{N}-SUMMARY.md`, `{phase_num}-VERIFICATION.md`
-
----
+Three tasks, three commits. Each task gets fresh context.
 
-### 5. Verify Work
-
-```
+```bash
 /ez:verify-work 1
 ```
 
-**This is where you confirm it actually works.**
-
-Automated verification checks that code exists and tests pass. But does the feature *work* the way you expected? This is your chance to use it.
+You test: Can register? Can login? Can connect to DB? All pass.
 
-The system:
+### 3. Repeat for Each Phase
 
-1. **Extracts testable deliverables** — What you should be able to do now
-2. **Walks you through one at a time** — "Can you log in with email?" Yes/no, or describe what's wrong
-3. **Diagnoses failures automatically** — Spawns debug agents to find root causes
-4. **Creates verified fix plans** — Ready for immediate re-execution
-
-If everything passes, you move on. If something's broken, you don't manually debug — you just run `/ez:execute-phase` again with the fix plans it created.
-
-**Creates:** `{phase_num}-UAT.md`, fix plans if issues found
-
----
-
-### 6. Repeat → Complete → Next Milestone
-
-```
+```bash
 /ez:discuss-phase 2
 /ez:plan-phase 2
 /ez:execute-phase 2
 /ez:verify-work 2
-...
-/ez:complete-milestone
-/ez:new-milestone
-```
-
-Loop **discuss → plan → execute → verify** until milestone complete.
-
-If you want faster intake during discussion, use `/ez:discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one.
-
-Each phase gets your input (discuss), proper research (plan), clean execution (execute), and human verification (verify). Context stays fresh. Quality stays high.
-
-When all phases are done, `/ez:complete-milestone` archives the milestone and tags the release.
-
-Then `/ez:new-milestone` starts the next version — same flow as `new-project` but for your existing codebase. You describe what you want to build next, the system researches the domain, you scope requirements, and it creates a fresh roadmap. Each milestone is a clean cycle: define → build → ship.
-
----
-
-### Quick Mode
-
-```
-/ez:quick
-```
-
-**For ad-hoc tasks that don't need full planning.**
-
-Quick mode gives you EZ Agents guarantees (atomic commits, state tracking) with a faster path:
-
-- **Same agents** — Planner + executor, same quality
-- **Skips optional steps** — No research, no plan checker, no verifier
-- **Separate tracking** — Lives in `.planning/quick/`, not phases
-
-Use for: bug fixes, small features, config changes, one-off tasks.
-
-```
-/ez:quick
-> What do you want to do? "Add dark mode toggle to settings"
 ```
 
-**Creates:** `.planning/quick/001-add-dark-mode-toggle/PLAN.md`, `SUMMARY.md`
-
----
-
-## Why It Works
-
-### Context Engineering
-
-Claude Code is incredibly powerful *if* you give it the context it needs. Most people don't.
-
-EZ Agents handles it for you:
-
-| File | What it does |
-|------|--------------|
-| `PROJECT.md` | Project vision, always loaded |
-| `research/` | Ecosystem knowledge (stack, features, architecture, pitfalls) |
-| `REQUIREMENTS.md` | Scoped v1/v2 requirements with phase traceability |
-| `ROADMAP.md` | Where you're going, what's done |
-| `STATE.md` | Decisions, blockers, position — memory across sessions |
-| `PLAN.md` | Atomic task with XML structure, verification steps |
-| `SUMMARY.md` | What happened, what changed, committed to history |
-| `todos/` | Captured ideas and tasks for later work |
-
-Size limits based on where Claude's quality degrades. Stay under, get consistent excellence.
-
-### XML Prompt Formatting
-
-Every plan is structured XML optimized for Claude:
-
-```xml
-<task type="auto">
-  <name>Create login endpoint</name>
-  <files>src/app/api/auth/login/route.ts</files>
-  <action>
-    Use jose for JWT (not jsonwebtoken - CommonJS issues).
-    Validate credentials against users table.
-    Return httpOnly cookie on success.
-  </action>
-  <verify>curl -X POST localhost:3000/api/auth/login returns 200 + Set-Cookie</verify>
-  <done>Valid credentials return cookie, invalid return 401</done>
-</task>
-```
-
-Precise instructions. No guessing. Verification built in.
-
-### Multi-Agent Orchestration
-
-Every stage uses the same pattern: a thin orchestrator spawns specialized agents, collects results, and routes to the next step.
-
-| Stage | Orchestrator does | Agents do |
-|-------|------------------|-----------|
-| Research | Coordinates, presents findings | 4 parallel researchers investigate stack, features, architecture, pitfalls |
-| Planning | Validates, manages iteration | Planner creates plans, checker verifies, loop until pass |
-| Execution | Groups into waves, tracks progress | Executors implement in parallel, each with fresh 200k context |
-| Verification | Presents results, routes next | Verifier checks codebase against goals, debuggers diagnose failures |
-
-The orchestrator never does heavy lifting. It spawns agents, waits, integrates results.
-
-**The result:** You can run an entire phase — deep research, multiple plans created and verified, thousands of lines of code written across parallel executors, automated verification against goals — and your main context window stays at 30-40%. The work happens in fresh subagent contexts. Your session stays fast and responsive.
-
-### Atomic Git Commits
-
-Each task gets its own commit immediately after completion:
+### 4. Complete Milestone
 
 ```bash
-abc123f docs(08-02): complete user registration plan
-def456g feat(08-02): add email confirmation flow
-hij789k feat(08-02): implement password hashing
-lmn012o feat(08-02): create registration endpoint
-```
-
-> [!NOTE]
-> **Benefits:** Git bisect finds exact failing task. Each task independently revertable. Clear history for Claude in future sessions. Better observability in AI-automated workflow.
-
-Every commit is surgical, traceable, and meaningful.
-
-### Modular by Design
-
-- Add phases to current milestone
-- Insert urgent work between phases
-- Complete milestones and start fresh
-- Adjust plans without rebuilding everything
-
-You're never locked in. The system adapts.
-
----
-
-## Commands
-
-### Core Workflow
-
-| Command | What it does |
-|---------|--------------|
-| `/ez:new-project [--auto]` | Full initialization: questions → research → requirements → roadmap |
-| `/ez:discuss-phase [N] [--auto]` | Capture implementation decisions before planning |
-| `/ez:plan-phase [N] [--auto]` | Research + plan + verify for a phase |
-| `/ez:execute-phase <N>` | Execute all plans in parallel waves, verify when complete |
-| `/ez:verify-work [N]` | Manual user acceptance testing ¹ |
-| `/ez:audit-milestone` | Verify milestone achieved its definition of done |
-| `/ez:complete-milestone` | Archive milestone, tag release |
-| `/ez:new-milestone [name]` | Start next version: questions → research → requirements → roadmap |
-
-### Navigation
-
-| Command | What it does |
-|---------|--------------|
-| `/ez:progress` | Where am I? What's next? |
-| `/ez:help` | Show all commands and usage guide |
-| `/ez:update` | Update EZ Agents with changelog preview |
-| `/ez:join-discord` | Join the EZ Agents Discord community |
-
-### Brownfield
-
-| Command | What it does |
-|---------|--------------|
-| `/ez:map-codebase [area]` | Analyze existing codebase before new-project |
-
-### Phase Management
-
-| Command | What it does |
-|---------|--------------|
-| `/ez:add-phase` | Append phase to roadmap |
-| `/ez:insert-phase [N]` | Insert urgent work between phases |
-| `/ez:remove-phase [N]` | Remove future phase, renumber |
-| `/ez:list-phase-assumptions [N]` | See Claude's intended approach before planning |
-| `/ez:plan-milestone-gaps` | Create phases to close gaps from audit |
-
-### Session
-
-| Command | What it does |
-|---------|--------------|
-| `/ez:pause-work` | Create handoff when stopping mid-phase |
-| `/ez:resume-work` | Restore from last session |
-
-### Utilities
-
-| Command | What it does |
-|---------|--------------|
-| `/ez:settings` | Configure model profile and workflow agents |
-| `/ez:set-profile <profile>` | Switch model profile (quality/balanced/budget) |
-| `/ez:add-todo [desc]` | Capture idea for later |
-| `/ez:check-todos` | List pending todos |
-| `/ez:debug [desc]` | Systematic debugging with persistent state |
-| `/ez:quick [--full] [--discuss]` | Execute ad-hoc task with EZ Agents guarantees (`--full` adds plan-checking and verification, `--discuss` gathers context first) |
-| `/ez:health [--repair]` | Validate `.planning/` directory integrity, auto-repair with `--repair` |
-
-<sup>¹ Contributed by reddit user OracleGreyBeard</sup>
-
----
-
-## Configuration
-
-EZ Agents stores project settings in `.planning/config.json`. Configure during `/ez:new-project` or update later with `/ez:settings`. For the full config schema, workflow toggles, git branching options, and per-agent model breakdown, see the [User Guide](docs/USER-GUIDE.md#configuration-reference).
-
-### Core Settings
-
-| Setting | Options | Default | What it controls |
-|---------|---------|---------|------------------|
-| `mode` | `yolo`, `interactive` | `interactive` | Auto-approve vs confirm at each step |
-| `granularity` | `coarse`, `standard`, `fine` | `standard` | Phase granularity — how finely scope is sliced (phases × plans) |
-
-### Model Profiles
-
-Control which Claude model each agent uses. Balance quality vs token spend.
-
-| Profile | Planning | Execution | Verification |
-|---------|----------|-----------|--------------|
-| `quality` | Opus | Opus | Sonnet |
-| `balanced` (default) | Opus | Sonnet | Sonnet |
-| `budget` | Sonnet | Sonnet | Haiku |
-
-Switch profiles:
-```
-/ez:set-profile budget
+/ez:audit-milestone     # Checks all requirements are met
+/ez:complete-milestone  # Archives, tags v1.0
 ```
 
-Or configure via `/ez:settings`.
-
-### Workflow Agents
-
-These spawn additional agents during planning/execution. They improve quality but add tokens and time.
-
-| Setting | Default | What it does |
-|---------|---------|--------------|
-| `workflow.research` | `true` | Researches domain before planning each phase |
-| `workflow.plan_check` | `true` | Verifies plans achieve phase goals before execution |
-| `workflow.verifier` | `true` | Confirms must-haves were delivered after execution |
-| `workflow.auto_advance` | `false` | Auto-chain discuss → plan → execute without stopping |
-
-Use `/ez:settings` to toggle these, or override per-invocation:
-- `/ez:plan-phase --skip-research`
-- `/ez:plan-phase --skip-verify`
-
-### Execution
-
-| Setting | Default | What it controls |
-|---------|---------|------------------|
-| `parallelization.enabled` | `true` | Run independent plans simultaneously |
-| `planning.commit_docs` | `true` | Track `.planning/` in git |
-
-### Git Branching
-
-Control how EZ Agents handles branches during execution.
-
-| Setting | Options | Default | What it does |
-|---------|---------|---------|--------------|
-| `git.branching_strategy` | `none`, `phase`, `milestone` | `none` | Branch creation strategy |
-| `git.phase_branch_template` | string | `ez/phase-{phase}-{slug}` | Template for phase branches |
-| `git.milestone_branch_template` | string | `ez/{milestone}-{slug}` | Template for milestone branches |
-
-**Strategies:**
-- **`none`** — Commits to current branch (default EZ Agents behavior)
-- **`phase`** — Creates a branch per phase, merges at phase completion
-- **`milestone`** — Creates one branch for entire milestone, merges at completion
-
-At milestone completion, EZ Agents offers squash merge (recommended) or merge with history.
-
 ---
 
-## Security
-
-### Protecting Sensitive Files
-
-EZ Agents' codebase mapping and analysis commands read files to understand your project. **Protect files containing secrets** by adding them to Claude Code's deny list:
-
-1. Open Claude Code settings (`.claude/settings.json` or global)
-2. Add sensitive file patterns to the deny list:
-
-```json
-{
-  "permissions": {
-    "deny": [
-      "Read(.env)",
-      "Read(.env.*)",
-      "Read(**/secrets/*)",
-      "Read(**/*credential*)",
-      "Read(**/*.pem)",
-      "Read(**/*.key)"
-    ]
-  }
-}
-```
-
-This prevents Claude from reading these files entirely, regardless of what commands you run.
+## Documentation
 
-> [!IMPORTANT]
-> EZ Agents includes built-in protections against committing secrets, but defense-in-depth is best practice. Deny read access to sensitive files as a first line of defense.
+| Doc | What's Inside |
+|-----|---------------|
+| [User Guide](docs/USER-GUIDE.md) | Full command reference, workflows, troubleshooting |
+| [Workflows](docs/WORKFLOWS.md) | Complete workflow diagrams for all use cases |
+| [Provider Behaviors](docs/PROVIDER-BEHAVIORS.md) | Differences between Claude, OpenCode, Gemini, etc. |
+| [Qwen Code Install](docs/QWEN-CODE-INSTALL.md) | Fix for Qwen Code CLI installation issues |
 
 ---
 
-## Troubleshooting
+## Contributing
 
-**Commands not found after install?**
-- Restart your runtime to reload commands/skills
-- Verify files exist in `~/.claude/commands/ez/` (global) or `./.claude/commands/ez/` (local)
-- For Codex, verify skills exist in `~/.codex/skills/ez-*/SKILL.md` (global) or `./.codex/skills/ez-*/SKILL.md` (local)
+Contributions welcome! A few guidelines:
 
-**Commands not working as expected?**
-- Run `/ez:help` to verify installation
-- Re-run `ez-agents` to reinstall
+1. **Test your changes** — Run `npm test` before submitting
+2. **Keep it cross-platform** — No Unix-specific commands (use `fs-utils.cjs`)
+3. **Document behavior** — Update USER-GUIDE.md for new commands
+4. **Respect the workflow** — EZ Agents is about structure; don't break existing patterns
 
-**Updating to the latest version?**
-```bash
-ez-agents-update
-```
+### Development Setup
 
-**Using Docker or containerized environments?**
-
-If file reads fail with tilde paths (`~/.claude/...`), set `CLAUDE_CONFIG_DIR` before installing:
 ```bash
-CLAUDE_CONFIG_DIR=/home/youruser/.claude ez-agents --global
+git clone https://github.com/howlil/ez-agents.git
+cd ez-agents
+npm install
+npm run build:hooks
+npm link
 ```
-This ensures absolute paths are used instead of `~` which may not expand correctly in containers.
-
-### Uninstalling
 
-To remove EZ Agents completely:
+### Running Tests
 
 ```bash
-# Global installs
-ez-agents --claude --global --uninstall
-ez-agents --opencode --global --uninstall
-ez-agents --codex --global --uninstall
-
-# Local installs (current project)
-ez-agents --claude --local --uninstall
-ez-agents --opencode --local --uninstall
-ez-agents --codex --local --uninstall
+npm test              # Run all tests
+npm run test:coverage # With coverage report
 ```
 
-This removes all EZ Agents commands, agents, hooks, and settings while preserving your other configurations.
-
 ---
 
-## Community Ports
-
-OpenCode, Gemini CLI, and Codex are now natively supported via `ez-agents`.
+## Acknowledgments
 
-These community ports pioneered multi-runtime support:
-
-| Project | Platform | Description |
-|---------|----------|-------------|
-| [ez-opencode](https://github.com/rokicool/ez-opencode) | OpenCode | Original OpenCode adaptation |
-| ez-gemini (archived) | Gemini CLI | Original Gemini adaptation by uberfuzzy |
-
----
-
-## Star History
-
-<a href="https://star-history.com/#glittercowboy/ez-agents&Date">
- <picture>
-   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=glittercowboy/ez-agents&type=Date&theme=dark" />
-   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=glittercowboy/ez-agents&type=Date" />
-   <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=glittercowboy/ez-agents&type=Date" />
- </picture>
-</a>
+EZ Agents is a fork of the original project by [TÂCHES](https://github.com/glittercowboy). This fork adds multi-model support (Qwen, Kimi, OpenAI), enterprise-grade security, and cross-platform reliability. Not affiliated with the upstream repository.
 
 ---
 
 ## License
 
-MIT License. See [LICENSE](LICENSE) for details.
+MIT — see [LICENSE](LICENSE)
 
 ---
 
-<div align="center">
-
-**Claude Code is powerful. EZ Agents makes it reliable.**
+## Getting Help
 
-</div>
+- **Issues:** [GitHub Issues](https://github.com/howlil/ez-agents/issues)
+- **Discussions:** [GitHub Discussions](https://github.com/howlil/ez-agents/discussions)
+- **npm:** [@howlil/ez-agents](https://www.npmjs.com/package/@howlil/ez-agents)