@su-record/vibe 2.5.9 → 2.5.11

package/commands/vibe.run.md

@@ -1,1031 +1,1051 @@
----
-description: Execute implementation from SPEC
-argument-hint: "feature name" or --phase N
----
-
-# /vibe.run
-
-Execute **Scenario-Driven Implementation** with automatic quality verification.
-
-> **Core Principle**: Scenarios are both the implementation unit and verification criteria. All scenarios passing = Quality guaranteed.
-
-## Usage
-
-```
-/vibe.run "feature-name"              # Full implementation
-/vibe.run "feature-name" --phase 1    # Specific Phase only
-/vibe.run "feature-name" ultrawork    # ULTRAWORK mode (recommended)
-/vibe.run "feature-name" ulw          # Short alias for ultrawork
-```
-
----
-
-## **Scenario-Driven Development (SDD)**
-
-> Automate **Scenario = Implementation = Verification** so even non-developers can trust quality
-
-### Core Flow
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│                    SCENARIO-DRIVEN IMPLEMENTATION                │
-│                                                                  │
-│   Load Feature file                                              │
-│        ↓                                                        │
-│   ┌──────────────────────────────────────────────────────────┐  │
-│   │ Scenario 1: Happy Path                                    │  │
-│   │   Given → When → Then                                     │  │
-│   │        ↓                                                  │  │
-│   │   [Implement] → [Verify immediately] → ✅ Pass            │  │
-│   └──────────────────────────────────────────────────────────┘  │
-│        ↓                                                        │
-│   ┌──────────────────────────────────────────────────────────┐  │
-│   │ Scenario 2: Edge Case                                     │  │
-│   │   Given → When → Then                                     │  │
-│   │        ↓                                                  │  │
-│   │   [Implement] → [Verify] → ❌ Fail → [Fix] → ✅ Pass      │  │
-│   └──────────────────────────────────────────────────────────┘  │
-│        ↓                                                        │
-│   ┌──────────────────────────────────────────────────────────┐  │
-│   │ Scenario N: ...                                           │  │
-│   │   [Implement] → [Verify immediately] → ✅ Pass            │  │
-│   └──────────────────────────────────────────────────────────┘  │
-│        ↓                                                        │
-│   ┌──────────────────────────────────────────────────────────┐  │
-│   │  📊 QUALITY REPORT                                        │  │
-│   │  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   │  │
-│   │  Scenarios: 5/5 passed ✅                                 │  │
-│   │  Quality score: 94/100                                    │  │
-│   │  Build: ✅ | Tests: ✅                                    │  │
-│   └──────────────────────────────────────────────────────────┘  │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Scenario = Implementation Unit
-
-**Traditional approach (Phase-based)**:
-```
-Phase 1 → Phase 2 → Phase 3 → ... → Verify at the end
-                                      ↓
-                              "Where did it go wrong?"
-```
-
-**SDD approach (Scenario-based)**:
-```
-Scenario 1 → Implement → Verify ✅
-Scenario 2 → Implement → Verify ✅
-Scenario 3 → Implement → Verify ❌ → Fix → ✅
-...
-All pass = Quality guaranteed
-```
-
-### Automated Verification
-
-After implementing each scenario, **automatic verification**:
-
-| Verification Item | Auto Check |
-|-------------------|------------|
-| Given (precondition) | State/data preparation confirmed |
-| When (action) | Feature execution possible |
-| Then (result) | Expected result matches |
-| Code quality | Complexity, style, security |
-
-### Auto-Fix on Failure
-
-```
-Scenario verification failed
-      ↓
-[Root cause analysis] - Which Then condition failed?
-      ↓
-[Implement fix] - Fix only that part
-      ↓
-[Re-verify] - Check again
-      ↓
-Repeat until pass (max 3 times)
-```
-
----
-
-## **ULTRAWORK Mode** (ulw)
-
-> Include `ultrawork` or `ulw` in your command to activate **maximum performance mode**.
-
-### What ULTRAWORK Enables
-
-When you include `ultrawork` (or `ulw`), ALL of these activate automatically:
-
-| Feature | Description |
-|---------|-------------|
-| **Parallel Exploration** | 3+ Task(haiku) agents run simultaneously |
-| **Boulder Loop** | Auto-continues until ALL phases complete |
-| **Context Compression** | Aggressive auto-save at 70%+ context |
-| **No Pause** | Doesn't wait for confirmation between phases |
-| **External LLMs** | Auto-consults GPT/Gemini if enabled |
-| **Error Recovery** | Auto-retries on failure (up to 3 times) |
-
-### Boulder Loop (Inspired by Sisyphus)
-
-Like Sisyphus rolling the boulder, ULTRAWORK **keeps going until done**:
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│                    BOULDER LOOP (ultrawork)                      │
-│                                                                  │
-│   ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐  │
-│   │ Phase 1  │───→│ Phase 2  │───→│ Phase 3  │───→│ Phase N  │  │
-│   └──────────┘    └──────────┘    └──────────┘    └──────────┘  │
-│        │               │               │               │         │
-│        ↓               ↓               ↓               ↓         │
-│   [Parallel]      [Parallel]      [Parallel]      [Parallel]    │
-│   [Implement]     [Implement]     [Implement]     [Implement]   │
-│   [Test]          [Test]          [Test]          [Test]        │
-│        │               │               │               │         │
-│        └───────────────┴───────────────┴───────────────┘         │
-│                              │                                   │
-│                              ↓                                   │
-│                     ┌──────────────┐                             │
-│                     │  ALL DONE?   │                             │
-│                     └──────────────┘                             │
-│                       │         │                                │
-│                      NO        YES                               │
-│                       │         │                                │
-│                       ↓         ↓                                │
-│                   [Continue]  [🎉 Complete!]                     │
-│                                                                  │
-│   NO STOPPING until acceptance criteria met or error limit hit   │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### ULTRAWORK Example
-
-```
-User: /vibe.run "brick-game" ultrawork
-
-Claude:
-🚀 ULTRAWORK MODE ACTIVATED
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📄 SPEC: .claude/vibe/specs/brick-game.md
-🎯 4 Phases detected
-⚡ Boulder Loop: ENABLED (will continue until all phases complete)
-🔄 Auto-retry: ON (max 3 per phase)
-💾 Context compression: AGGRESSIVE
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🏔️ BOULDER ROLLING... Phase 1/4
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚡ [PARALLEL] Launching 3 exploration agents...
-✅ Exploration complete (7.2s)
-🔨 Implementing...
-✅ Phase 1 complete
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🏔️ BOULDER ROLLING... Phase 2/4
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚡ [PARALLEL] Launching 3 exploration agents...
-✅ Exploration complete (6.8s)
-🔨 Implementing...
-❌ Test failed: collision detection
-🔄 Auto-retry 1/3...
-🔨 Fixing...
-✅ Phase 2 complete
-
-[...continues automatically...]
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎉 BOULDER REACHED THE TOP!
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-✅ All 4 phases complete
-✅ All acceptance criteria passed
-✅ Build succeeded
-✅ Tests passed
-
-⏱️ Total: 8m 24s
-📊 Retries: 2
-💾 Context saved: 3 checkpoints
-```
-
-### Normal vs ULTRAWORK Comparison
-
-| Aspect | Normal | ULTRAWORK |
-|--------|--------|-----------|
-| Phase transition | May pause | Auto-continues |
-| On error | Reports and stops | Auto-retries (3x) |
-| Context 70%+ | Warning only | Auto-compress + save |
-| Exploration | Sequential possible | FORCED parallel |
-| Completion | Phase-by-phase | Until ALL done |
-
----
-
-## Rules Reference
-
-**Must follow `~/.claude/vibe/rules/` (global):**
-
-- `core/development-philosophy.md` - Surgical precision, modify only requested scope
-- `core/quick-start.md` - Korean, DRY, SRP, YAGNI
-- `standards/complexity-metrics.md` - Functions ≤20 lines, nesting ≤3 levels
-- `quality/checklist.md` - Code quality checklist
-
-**Language guide:** `~/.claude/vibe/languages/{stack}.md` (global reference)
-
-## Description
-
-Read PTCF structured SPEC document and execute implementation immediately.
-
-> **PLAN, TASKS documents unnecessary** - SPEC is the executable prompt
-
-## Model Orchestration
-
-Automatically select optimal model based on task type:
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│               Opus 4.5 (Orchestrator)                       │
-│               - Coordinate overall flow                     │
-│               - Final decisions/review                      │
-└─────────────────────────┬───────────────────────────────────┘
-                          │
-    ┌─────────────────────┼─────────────────────┐
-    ↓                     ↓                     ↓
-┌─────────┐         ┌─────────┐         ┌─────────┐
-│ Haiku   │         │ Sonnet  │         │ Haiku   │
-│(Explore)│         │ (Impl)  │         │ (Test)  │
-└─────────┘         └─────────┘         └─────────┘
-```
-
-### Task Calls by Role
-
-| Task Type | Model | Task Parameter |
-|-----------|-------|----------------|
-| Codebase exploration | Haiku 4.5 | `model: "haiku"` |
-| Core implementation | Sonnet 4 | `model: "sonnet"` |
-| Test writing | Haiku 4.5 | `model: "haiku"` |
-| Architecture decisions | Opus 4.5 | Main session |
-| Final review | Opus 4.5 | Main session |
-
-### External LLM Usage (When Enabled)
-
-When external LLMs are enabled in `.claude/vibe/config.json`:
-
-| Role | Method | Condition |
-|------|--------|-----------|
-| User direct query | `gpt.question`, `gemini.question` | Hook auto-handles |
-| Internal orchestration | Call global script via Bash | Claude calls directly |
-
-**User questions (Hook auto-handles):**
-- `gpt.question` - GPT architecture consultation
-- `gemini.question` - Gemini Q&A/consultation
-
-**Claude internal calls (directly via Bash):**
-```bash
-# Usage: node llm-orchestrate.js <provider> <mode> [systemPrompt] [prompt]
-#   - If systemPrompt omitted, uses default
-#   - If systemPrompt is "-", uses default and treats next argument as prompt
-
-# Cross-platform path (works on Windows/macOS/Linux)
-VIBE_SCRIPTS="$(node -p "process.env.APPDATA || require('os').homedir() + '/.config'")/vibe/hooks/scripts"
-
-# GPT call
-node "$VIBE_SCRIPTS/llm-orchestrate.js" gpt orchestrate-json "[question content]"
-
-# Gemini call
-node "$VIBE_SCRIPTS/llm-orchestrate.js" gemini orchestrate-json "[question content]"
-
-# Custom system prompt usage
-node "$VIBE_SCRIPTS/llm-orchestrate.js" gpt orchestrate-json "You are a code reviewer" "[question content]"
-```
-
-### External LLM Fallback
-
-**IMPORTANT**: When GPT/Gemini hook fails, Claude MUST handle the task directly:
-
-**Fallback behavior**:
-- Do NOT retry the external LLM call
-- Claude handles the task using its own capabilities
-- Continue with the implementation without interruption
-- Log the fallback but don't block progress
-
-## Vibe Tools (Semantic Analysis & Memory)
-
-Use vibe tools for accurate codebase understanding and session continuity.
-
-### Tool Invocation
-
-All tools are called via:
-```bash
-node -e "import('@su-record/vibe/tools').then(t => t.TOOL_NAME({...args}).then(r => console.log(r.content[0].text)))"
-```
-
-### Semantic Analysis Tools
-
-| Tool | Purpose | Usage |
-|------|---------|-------|
-| `findSymbol` | Find symbol definitions | `{symbolName: 'functionName', searchPath: '.'}` |
-| `findReferences` | Find all references | `{symbolName: 'functionName', searchPath: '.'}` |
-| `analyzeComplexity` | Analyze code complexity | `{filePath: 'src/file.ts'}` |
-| `validateCodeQuality` | Validate code quality | `{filePath: 'src/file.ts'}` |
-
-**Example - Find symbol:**
-```bash
-node -e "import('@su-record/vibe/tools').then(t => t.findSymbol({symbolName: 'login', searchPath: '.'}).then(r => console.log(r.content[0].text)))"
-```
-
-### Memory Tools
-
-| Tool | Purpose | Usage |
-|------|---------|-------|
-| `saveMemory` | Save important decisions | `{key: 'decision-name', value: 'content', category: 'project'}` |
-| `recallMemory` | Recall saved memory | `{key: 'decision-name'}` |
-| `listMemories` | List all memories | `{category: 'project'}` |
-
-**Example - Save important decision:**
-```bash
-node -e "import('@su-record/vibe/tools').then(t => t.saveMemory({key: 'auth-pattern', value: 'Using JWT with refresh tokens', category: 'project'}).then(r => console.log(r.content[0].text)))"
-```
-
-### Session Management (Auto via Hooks)
-
-- **Session start**: Hook auto-calls `startSession` to restore previous context
-- **Context 80%+**: Hook auto-calls `autoSaveContext` to preserve state
-
-## Process
-
-### 1. Load SPEC + Feature
-
-```
-📄 .claude/vibe/specs/{feature-name}.md      → SPEC (structure, constraints, context)
-📄 .claude/vibe/features/{feature-name}.feature → Feature (scenario = implementation unit)
-```
-
-**Error if Feature file missing**:
-```
-❌ Feature file not found.
-   Run /vibe.spec "{feature-name}" first.
-```
-
-### 2. Extract Scenario List
-
-Extract all Scenarios from Feature file:
-
-```markdown
-## Scenarios to Implement
-
-| # | Scenario | Status |
-|---|----------|--------|
-| 1 | Valid login success | ⬜ |
-| 2 | Invalid password error | ⬜ |
-| 3 | Email format validation | ⬜ |
-| 4 | Password reset link | ⬜ |
-
-Total: 4 scenarios
-```
-
-### 3. Scenario-by-Scenario Implementation (Core)
-
-**For each scenario**:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Scenario 1/4: Valid login success
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Given: User is registered
-When: Login with valid email and password
-Then: Login success + JWT token returned
-
-[Step 1] Analyzing implementation...
-  - Required files: auth.service.ts, login.controller.ts
-  - Exploring related code...
-
-[Step 2] Implementing...
-  ✅ auth.service.ts - Added login() method
-  ✅ login.controller.ts - POST /login endpoint
-
-[Step 3] Verifying...
-  ✅ Given: Test user creation possible
-  ✅ When: Login API call succeeded
-  ✅ Then: JWT token return confirmed
-
-✅ Scenario 1 passed!
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-**On failure**:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Scenario 2/4: Invalid password error
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-[Step 3] Verifying...
-  ✅ Given: Test user exists
-  ✅ When: Login attempt with wrong password
-  ❌ Then: "Invalid credentials" error message
-     Actual: "Error occurred" returned
-
-[Auto-fix 1/3]
-  Cause: Error message not properly set
-  Fix: auth.service.ts line 42
-
-[Re-verify]
-  ✅ Then: "Invalid credentials" error message
-
-✅ Scenario 2 passed! (1 fix)
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
----
-
-## **CRITICAL: Parallel Sub-Agent Execution**
-
-> **MUST USE PARALLEL TASK CALLS** - This is REQUIRED, not optional.
-> Sequential execution when parallel is possible = VIOLATION of this workflow.
-
-### Mandatory Parallel Exploration (Phase Start)
-
-**BEFORE any implementation, you MUST launch these Task calls IN PARALLEL (single message, multiple tool calls):**
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  STEP 1: PARALLEL EXPLORATION (REQUIRED)                        │
-│                                                                 │
-│  Launch ALL of these in ONE message:                            │
-│                                                                 │
-│  Task(haiku) ─┬─→ "Analyze related files in <context>"          │
-│               │                                                 │
-│  Task(haiku) ─┼─→ "Check dependencies and imports"              │
-│               │                                                 │
-│  Task(haiku) ─┴─→ "Find existing patterns and conventions"      │
-│                                                                 │
-│  [If GPT enabled] Bash: node {{VIBE_PATH}}/hooks/scripts/llm-orchestrate.js gpt orchestrate-json "[question]"
-│  [If Gemini enabled] Bash: node {{VIBE_PATH}}/hooks/scripts/llm-orchestrate.js gemini orchestrate-json "[question]"
-└─────────────────────────────────────────────────────────────────┘
-                              │
-                              ↓ (wait for all to complete)
-┌─────────────────────────────────────────────────────────────────┐
-│  STEP 2: SYNTHESIZE (Opus)                                      │
-│  - Review all exploration results                               │
-│  - Decide implementation approach                               │
-│  - Identify files to modify/create                              │
-└─────────────────────────────────────────────────────────────────┘
-                              │
-                              ↓
-┌─────────────────────────────────────────────────────────────────┐
-│  STEP 3: IMPLEMENT + BACKGROUND AGENTS (PARALLEL)               │
-│                                                                 │
-│  Main Agent (sonnet):                                           │
-│  └─→ Execute current phase implementation                       │
-│                                                                 │
-│  Background Agents (haiku, run_in_background=true):             │
-│  ├─→ Task: "Prepare Phase N+1 - analyze required files"         │
-│  ├─→ Task: "Pre-generate test cases for current implementation" │
-│  └─→ Task: "Search for related types/interfaces needed"         │
-│                                                                 │
-│  [ULTRAWORK] All 4 agents run simultaneously!                   │
-└─────────────────────────────────────────────────────────────────┘
-                              │
-                              ↓ (main completes, check backgrounds)
-┌─────────────────────────────────────────────────────────────────┐
-│  STEP 4: TEST + PHASE PIPELINING                                │
-│                                                                 │
-│  Current Phase:                                                 │
-│  └─→ Task(haiku): Write tests using pre-generated cases         │
-│                                                                 │
-│  Next Phase Prep (from background results):                     │
-│  └─→ Already have file analysis, ready to start immediately     │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Parallel Task Call Pattern (MUST FOLLOW)
-
-**Correct - Single message with multiple parallel Tasks:**
-```
-<message>
-  Task(haiku, "Analyze src/components/ for existing patterns")
-  Task(haiku, "Check package.json dependencies")
-  Task(haiku, "Find usage of similar features in codebase")
-</message>
-→ All 3 run simultaneously, ~3x faster
-```
-
-**WRONG - Sequential calls (DO NOT DO THIS):**
-```
-<message>Task(haiku, "Analyze...")</message>
-<message>Task(haiku, "Check...")</message>
-<message>Task(haiku, "Find...")</message>
-→ 3x slower, wastes time
-```
-
-### Background Agent Pattern (ULTRAWORK) via Orchestrator
-
-**Launch background agents for next phase via Orchestrator:**
-```bash
-# Start background agent (doesn't block)
-node -e "import('@su-record/vibe/orchestrator').then(o => o.runAgent('Phase 2 prep: Analyze auth API endpoints', 'phase2-prep').then(r => console.log(r.content[0].text)))"
-
-# Multiple backgrounds in parallel
-node -e "import('@su-record/vibe/orchestrator').then(async o => {
-  await Promise.all([
-    o.runAgent('Phase 2 prep: Analyze auth API endpoints', 'phase2-prep'),
-    o.runAgent('Pre-generate test cases for login form', 'test-prep'),
-    o.runAgent('Find existing validation patterns', 'pattern-finder')
-  ]);
-  console.log('All background agents started');
-})"
-```
-
-**Check background agent status:**
-```bash
-node -e "import('@su-record/vibe/orchestrator').then(o => console.log(o.status().content[0].text))"
-```
-
-**Get result when ready:**
-```bash
-node -e "import('@su-record/vibe/orchestrator').then(o => o.getResult('SESSION_ID').then(r => console.log(r.content[0].text)))"
-```
-
-**Why Background Agents Matter:**
-
-| Without Background | With Background |
-|--------------------|-----------------|
-| Phase 1: 60s | Phase 1: 60s (+ backgrounds running) |
-| Phase 2 prep: 20s | Phase 2 prep: 0s (already done!) |
-| Phase 2: 60s | Phase 2: 60s |
-| **Total: 140s** | **Total: 120s** |
-
-For 5 phases: 4 × 20s saved = **80s faster**
-
-### Why Parallel Matters
-
-| Approach | Time | Cache Benefit |
-|----------|------|---------------|
-| Sequential (3 Tasks) | ~30s | Cache cold on each |
-| **Parallel (3 Tasks)** | **~10s** | **Cache warmed once, shared** |
-
-vibe ProjectCache (LRU) caches ts-morph parsing results. Parallel calls share the warmed cache.
-
-### Phase Execution Flow (ULTRAWORK Pipeline)
-
-```
-Phase N Start
-    │
-    ├─→ [PARALLEL] Task(haiku) × 3: Exploration
-    │       - Related code analysis
-    │       - Dependency check
-    │       - Pattern discovery
-    │
-    ↓ (all complete)
-    │
-    ├─→ Opus: Synthesize and decide
-    │
-    ├─→ [PARALLEL PIPELINE] ←── KEY SPEED OPTIMIZATION
-    │       │
-    │       ├─→ Main: Task(sonnet) Implementation
-    │       │
-    │       └─→ Background (run_in_background=true):
-    │               ├─→ Task(haiku): Phase N+1 file analysis
-    │               ├─→ Task(haiku): Test case preparation
-    │               └─→ Task(haiku): Type/interface lookup
-    │
-    ↓ (main completes)
-    │
-    ├─→ Task(haiku): Tests (uses pre-generated cases)
-    │
-    ↓
-Phase N Complete
-    │
-    ↓ (Background results ready - NO WAIT for Phase N+1 exploration!)
-    │
-Phase N+1 Start (IMMEDIATE - exploration already done!)
-```
-
-**Speed Comparison:**
-
-| Mode | Phase Time | 5 Phases Total |
-|------|------------|----------------|
-| Sequential | ~2min/phase | ~10min |
-| Parallel Exploration | ~1.5min/phase | ~7.5min |
-| **ULTRAWORK Pipeline** | **~1min/phase** | **~5min** |
-
-**Why Pipeline is Faster:**
-- Background agents prepare next phase WHILE current phase implements
-- No idle time between phases
-- Test cases pre-generated during implementation
-- Cache stays warm across parallel tasks
-
----
-
-1. **Related code analysis**: Task(haiku) explores `<context>` related code
-2. **File creation/modification**: Task(sonnet) implements per `<output_format>`
-3. **Constraint compliance**: Check `<constraints>`
-4. **Run verification**: Execute verification commands
-
-### 4. Gemini Code Review + Auto-Fix (NEW)
-
-After all scenarios are implemented, **Gemini reviews the code and auto-fixes based on feedback**:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🔍 GEMINI CODE REVIEW
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-[Step 1] Sending implementation code to Gemini...
-  - Changed files: auth.service.ts, auth.controller.ts, ...
-
-[Step 2] Gemini review results:
-  ┌─────────────────────────────────────────────────────┐
-  │ 📝 Gemini Feedback                                  │
-  │                                                     │
-  │ 1. [Improvement] auth.service.ts:24                 │
-  │    Need timing attack prevention for password compare│
-  │    → Recommend using crypto.timingSafeEqual()       │
-  │                                                     │
-  │ 2. [Improvement] auth.controller.ts:15              │
-  │    Rate limiting not applied                        │
-  │    → Recommend adding login attempt limit           │
-  │                                                     │
-  │ 3. [Style] auth.service.ts:42                       │
-  │    Magic number usage                               │
-  │    → Recommend extracting to constant               │
-  └─────────────────────────────────────────────────────┘
-
-[Step 3] Auto-fixing based on feedback...
-  ✅ auth.service.ts:24 - Applied timingSafeEqual
-  ✅ auth.controller.ts:15 - Added rate limiter
-  ✅ auth.service.ts:42 - Extracted constant
-
-[Step 4] Re-verifying...
-  ✅ Build succeeded
-  ✅ Tests passed
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-✅ Gemini review complete! 3 improvements applied
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-**MUST: Gemini Code Review (Required)**
-
-When Gemini is enabled, **must** use global hook script for code review:
-
-```bash
-# Cross-platform path (works on Windows/macOS/Linux)
-VIBE_SCRIPTS="$(node -p "process.env.APPDATA || require('os').homedir() + '/.config'")/vibe/hooks/scripts"
-
-node "$VIBE_SCRIPTS/llm-orchestrate.js" gemini orchestrate-json "Review this code for security, performance, best-practices: [code summary]. SPEC: [summary]. Scenarios: [list]"
-```
-
-**Call sequence:**
-1. Summarize key content of changed files
-2. Add SPEC requirements summary
-3. Execute global script call
-4. Fix code for each feedback item in response
-5. Re-run build/tests
-
-**Fallback handling:**
-- On `"status": "fallback"` response → Skip and proceed to next step
-- On network error → Retry once, then skip
-
-**Review application rules:**
-
-| Feedback Type | Action |
-|---------------|--------|
-| Security vulnerability | Auto-fix immediately |
-| Performance improvement | Auto-fix immediately |
-| Best practices | Auto-fix |
-| Style/preference | Apply selectively (project convention takes priority) |
-
-**Conditions:**
-- Only runs when Gemini MCP is enabled (`vibe gemini auth`)
-- Skip and proceed on fallback response
-- Must re-verify build/tests after fixes
-
-### 5. Quality Report (Auto-generated)
-
-After all scenarios complete + Gemini review, **quality report is auto-generated**:
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  📊 QUALITY REPORT: login                                        │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  ✅ Scenarios: 4/4 passed                                       │
-│                                                                 │
-│  ┌───────────────────────────────────────────────────────────┐  │
-│  │ # │ Scenario                  │ Status │ Retries │        │  │
-│  │───│───────────────────────────│────────│─────────│        │  │
-│  │ 1 │ Valid login success       │ ✅     │ 0       │        │  │
-│  │ 2 │ Invalid password error    │ ✅     │ 1       │        │  │
-│  │ 3 │ Email format validation   │ ✅     │ 0       │        │  │
-│  │ 4 │ Password reset link       │ ✅     │ 0       │        │  │
-│  └───────────────────────────────────────────────────────────┘  │
-│                                                                 │
-│  📈 Quality score: 94/100                                       │
-│                                                                 │
-│  ┌─────────────────────────────────────────────────────────┐    │
-│  │ Item              │ Result │ Notes                       │    │
-│  │───────────────────│────────│─────────────────────────────│    │
-│  │ Build             │ ✅     │ npm run build succeeded     │    │
-│  │ Tests             │ ✅     │ 12/12 passed                │    │
-│  │ Type check        │ ✅     │ 0 errors                    │    │
-│  │ Complexity        │ ✅     │ All functions ≤30 lines     │    │
-│  │ Security          │ ✅     │ 0 vulnerabilities           │    │
-│  │ Gemini review     │ ✅     │ 3 improvements applied      │    │
-│  └─────────────────────────────────────────────────────────┘    │
-│                                                                 │
-│  ⏱️ Total time: 3m 42s                                          │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-**What users should check**:
-- Scenario pass rate (4/4 = 100%)
-- Quality score (94/100)
-- Build/test status
-
-**This alone is enough to trust quality.**
-
-### 6. Update Feature File
-
-Auto-update scenario status:
-
-```markdown
-## Coverage
-
-| Scenario | SPEC AC | Status |
-|----------|---------|--------|
-| Valid login success | AC-1 | ✅ |
-| Invalid password error | AC-2 | ✅ |
-| Email format validation | AC-3 | ✅ |
-| Password reset link | AC-4 | ✅ |
-
-**Last verified**: 2024-01-15 14:32
-**Quality score**: 94/100
-```
-
-## TRUST 5 Principles
-
-Follow during implementation:
-
-| Principle | Description |
-|-----------|-------------|
-| **T**est-first | Write tests first |
-| **R**eadable | Clear code |
-| **U**nified | Consistent style |
-| **S**ecured | Consider security |
-| **T**rackable | Logging, monitoring |
-
-## Input
-
-- `.claude/vibe/specs/{feature-name}.md` (PTCF SPEC)
-- `.claude/vibe/features/{feature-name}.feature` (BDD)
-- `CLAUDE.md` (project context)
-
-## Output
-
-- Implemented code files
-- Test files
-- Updated SPEC document (checkmarks)
-
-## Example
-
-```
-User: /vibe.run "login"
-
-Claude:
-📄 Loading SPEC: .claude/vibe/specs/login.md
-📄 Loading Feature: .claude/vibe/features/login.feature
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📋 Scenarios to Implement
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-| # | Scenario | Status |
-|---|----------|--------|
-| 1 | Valid login success | ⬜ |
-| 2 | Invalid password error | ⬜ |
-| 3 | Email format validation | ⬜ |
-| 4 | Password reset link | ⬜ |
-
-Total: 4 scenarios
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Scenario 1/4: Valid login success
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Given: User is registered
-When: Login with valid email and password
-Then: Login success + JWT token returned
-
-⚡ [PARALLEL] Exploring...
-✅ Exploration complete (2.1s)
-
-🔨 Implementing...
-  ✅ auth.service.ts - Added login()
-  ✅ auth.controller.ts - POST /login
-
-🔍 Verifying...
-  ✅ Given: OK
-  ✅ When: OK
-  ✅ Then: OK
-
-✅ Scenario 1 passed!
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Scenario 2/4: Invalid password error
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🔨 Implementing...
-  ✅ auth.service.ts - Password validation logic
-
-🔍 Verifying...
-  ✅ Given: OK
-  ✅ When: OK
-  ❌ Then: "Invalid credentials" error message
-     Actual: "Error" returned
-
-🔄 Auto-fix 1/3...
-  Fix: auth.service.ts line 42
-
-🔍 Re-verifying...
-  ✅ Then: OK
-
-✅ Scenario 2 passed! (1 fix)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Scenario 3/4: Email format validation
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🔨 Implementing...
-🔍 Verifying...
-✅ Scenario 3 passed!
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 Scenario 4/4: Password reset link
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-🔨 Implementing...
-🔍 Verifying...
-✅ Scenario 4 passed!
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🔍 GEMINI CODE REVIEW
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📤 Sending code to Gemini...
-📝 Gemini feedback:
-  1. [Security] Need timing attack prevention → Fixing...
-  2. [Performance] Unnecessary DB call → Fixing...
-
-✅ 2 improvements auto-applied
-🔍 Re-verifying... ✅ Passed
-
-┌─────────────────────────────────────────────────────────────────┐
-│  📊 QUALITY REPORT: login                                        │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  ✅ Scenarios: 4/4 passed                                       │
-│                                                                 │
-│  | # | Scenario              | Status | Retries |               │
-│  |---|───────────────────────|───────|─────────|               │
-│  | 1 | Valid login success   | ✅    | 0       |               │
-│  | 2 | Invalid password error| ✅    | 1       |               │
-│  | 3 | Email format validation| ✅   | 0       |               │
-│  | 4 | Password reset link   | ✅    | 0       |               │
-│                                                                 │
-│  📈 Quality score: 94/100                                       │
-│  Build: ✅ | Tests: ✅ | Types: ✅ | Gemini: ✅ (2 applied)     │
-│                                                                 │
-│  ⏱️ Total time: 3m 42s                                          │
-└─────────────────────────────────────────────────────────────────┘
-
-🎉 Implementation complete! All scenarios passed + Gemini review applied.
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🔍 AUTO REVIEW (13+ Agents)
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-⚡ [PARALLEL] 13 expert agents reviewing...
-  - security-reviewer ✅
-  - performance-reviewer ✅
-  - architecture-reviewer ✅
-  - ...
-
-📋 Review results:
-  - P1 Critical: 0
-  - P2 Important: 2
-  - P3 Nice-to-have: 1
-
-🔧 Auto-fixing P2 issues...
-  1. [PERF] N+1 query → Fixed
-  2. [ARCH] Circular dependency → Fixed
-
-✅ Auto Review complete! 2 issues auto-resolved.
-```
-
-### Phase-specific Execution
-
-```
-User: /vibe.run "brick-game" --phase 2
-
-Claude:
-📄 Reading SPEC: .claude/vibe/specs/brick-game.md
-🎯 Executing Phase 2 only.
-
-Phase 2: Game Logic
-1. [ ] Paddle movement implementation
-2. [ ] Ball physics engine
-3. [ ] Brick collision handling
-4. [ ] Score system
-5. [ ] Game over conditions
-
-⚡ Launching parallel exploration...
-[Task(haiku) × 3 launched in parallel]
-
-🚀 Starting implementation...
-```
-
-## Error Handling
-
-On failure:
-1. Check error message
-2. Review `<constraints>`
-3. Fix code and retry
-4. If continues to fail, report to user
-
----
-
-## Quality Gate (Mandatory)
-
-### Implementation Quality Checklist
-
-Before marking any scenario as complete, ALL items must pass:
-
-| Category | Check Item | Weight |
-|----------|------------|--------|
-| **Functionality** | All Given/When/Then conditions verified | 20% |
-| **Functionality** | Edge cases handled per scenario | 10% |
-| **Code Quality** | No `any` types in TypeScript | 10% |
-| **Code Quality** | Functions ≤30 lines, nesting ≤3 levels | 10% |
-| **Code Quality** | No hardcoded values (use constants) | 5% |
-| **Security** | Input validation implemented | 10% |
-| **Security** | Authentication/authorization checked | 5% |
-| **Error Handling** | Try-catch or error states present | 10% |
-| **Error Handling** | User-friendly error messages | 5% |
-| **Testing** | Unit tests exist for core logic | 10% |
-| **Performance** | No N+1 queries or unnecessary loops | 5% |
-
-### Quality Score Calculation
-
-```
-Score = Σ(checked items × weight) / 100
-
-Grades:
-- 95-100: ✅ EXCELLENT - Ready to merge
-- 85-94:  ✅ GOOD - Minor improvements recommended
-- 70-84:  ⚠️ FAIR - Improvements required before merge
-- 0-69:   ❌ POOR - Major fixes needed
-```
-
-### Quality Gate Thresholds
-
-| Gate | Minimum Score | Condition |
-|------|---------------|-----------|
-| **Scenario Complete** | 85 | Each scenario must score ≥85 |
-| **Phase Complete** | 90 | Average of all scenarios ≥90 |
-| **Feature Complete** | 90 | All phases complete + Gemini review |
-
-### Auto-Fix Triggers
-
-| Issue Type | Auto-Fix Action |
-|------------|-----------------|
-| Missing error handling | Add try-catch wrapper |
-| Hardcoded values | Extract to constants file |
-| Missing input validation | Add validation schema |
-| Function too long | Suggest split points |
-| N+1 query detected | Add eager loading |
-
-### Forbidden Patterns (Block Merge)
-
-| Pattern | Why Forbidden | Detection |
-|---------|---------------|-----------|
-| `console.log` | Debug code in production | Regex scan |
-| `// TODO` without issue | Untracked work | Comment scan |
-| `any` type | Type safety bypass | TypeScript check |
-| `@ts-ignore` | Type error suppression | TypeScript check |
-| Empty catch blocks | Silent error swallowing | AST analysis |
-| Commented-out code | Dead code | Comment scan |
-
----
-
-## Next Step
-
-```
-/vibe.verify "brick-game"
-```
-
----
-
-ARGUMENTS: $ARGUMENTS
+---
+description: Execute implementation from SPEC
+argument-hint: "feature name" or --phase N
+---
+
+# /vibe.run
+
+Execute **Scenario-Driven Implementation** with automatic quality verification.
+
+> **Core Principle**: Scenarios are both the implementation unit and verification criteria. All scenarios passing = Quality guaranteed.
+
+## Usage
+
+```
+/vibe.run "feature-name"              # Full implementation
+/vibe.run "feature-name" --phase 1    # Specific Phase only
+/vibe.run "feature-name" ultrawork    # ULTRAWORK mode (recommended)
+/vibe.run "feature-name" ulw          # Short alias for ultrawork
+```
+
+---
+
+## **Scenario-Driven Development (SDD)**
+
+> Automate **Scenario = Implementation = Verification** so even non-developers can trust quality
+
+### Core Flow
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│                    SCENARIO-DRIVEN IMPLEMENTATION                │
+│                                                                  │
+│   Load Feature file                                              │
+│        ↓                                                        │
+│   ┌──────────────────────────────────────────────────────────┐  │
+│   │ Scenario 1: Happy Path                                    │  │
+│   │   Given → When → Then                                     │  │
+│   │        ↓                                                  │  │
+│   │   [Implement] → [Verify immediately] → ✅ Pass            │  │
+│   └──────────────────────────────────────────────────────────┘  │
+│        ↓                                                        │
+│   ┌──────────────────────────────────────────────────────────┐  │
+│   │ Scenario 2: Edge Case                                     │  │
+│   │   Given → When → Then                                     │  │
+│   │        ↓                                                  │  │
+│   │   [Implement] → [Verify] → ❌ Fail → [Fix] → ✅ Pass      │  │
+│   └──────────────────────────────────────────────────────────┘  │
+│        ↓                                                        │
+│   ┌──────────────────────────────────────────────────────────┐  │
+│   │ Scenario N: ...                                           │  │
+│   │   [Implement] → [Verify immediately] → ✅ Pass            │  │
+│   └──────────────────────────────────────────────────────────┘  │
+│        ↓                                                        │
+│   ┌──────────────────────────────────────────────────────────┐  │
+│   │  📊 QUALITY REPORT                                        │  │
+│   │  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   │  │
+│   │  Scenarios: 5/5 passed ✅                                 │  │
+│   │  Quality score: 94/100                                    │  │
+│   │  Build: ✅ | Tests: ✅                                    │  │
+│   └──────────────────────────────────────────────────────────┘  │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+### Scenario = Implementation Unit
+
+**Traditional approach (Phase-based)**:
+```
+Phase 1 → Phase 2 → Phase 3 → ... → Verify at the end
+                                      ↓
+                              "Where did it go wrong?"
+```
+
+**SDD approach (Scenario-based)**:
+```
+Scenario 1 → Implement → Verify ✅
+Scenario 2 → Implement → Verify ✅
+Scenario 3 → Implement → Verify ❌ → Fix → ✅
+...
+All pass = Quality guaranteed
+```
+
+### Automated Verification
+
+After implementing each scenario, **automatic verification**:
+
+| Verification Item | Auto Check |
+|-------------------|------------|
+| Given (precondition) | State/data preparation confirmed |
+| When (action) | Feature execution possible |
+| Then (result) | Expected result matches |
+| Code quality | Complexity, style, security |
+
+### Auto-Fix on Failure
+
+```
+Scenario verification failed
+      ↓
+[Root cause analysis] - Which Then condition failed?
+      ↓
+[Implement fix] - Fix only that part
+      ↓
+[Re-verify] - Check again
+      ↓
+Repeat until pass (max 3 times)
+```
+
+---
+
+## **ULTRAWORK Mode** (ulw)
+
+> Include `ultrawork` or `ulw` in your command to activate **maximum performance mode**.
+
+### What ULTRAWORK Enables
+
+When you include `ultrawork` (or `ulw`), ALL of these activate automatically:
+
+| Feature | Description |
+|---------|-------------|
+| **Parallel Exploration** | 3+ Task(haiku) agents run simultaneously |
+| **Boulder Loop** | Auto-continues until ALL phases complete |
+| **Context Compression** | Aggressive auto-save at 70%+ context |
+| **No Pause** | Doesn't wait for confirmation between phases |
+| **External LLMs** | Auto-consults GPT/Gemini if enabled |
+| **Error Recovery** | Auto-retries on failure (up to 3 times) |
+
+### Boulder Loop (Inspired by Sisyphus)
+
+Like Sisyphus rolling the boulder, ULTRAWORK **keeps going until done**:
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│                    BOULDER LOOP (ultrawork)                      │
+│                                                                  │
+│   ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐  │
+│   │ Phase 1  │───→│ Phase 2  │───→│ Phase 3  │───→│ Phase N  │  │
+│   └──────────┘    └──────────┘    └──────────┘    └──────────┘  │
+│        │               │               │               │         │
+│        ↓               ↓               ↓               ↓         │
+│   [Parallel]      [Parallel]      [Parallel]      [Parallel]    │
+│   [Implement]     [Implement]     [Implement]     [Implement]   │
+│   [Test]          [Test]          [Test]          [Test]        │
+│        │               │               │               │         │
+│        └───────────────┴───────────────┴───────────────┘         │
+│                              │                                   │
+│                              ↓                                   │
+│                     ┌──────────────┐                             │
+│                     │  ALL DONE?   │                             │
+│                     └──────────────┘                             │
+│                       │         │                                │
+│                      NO        YES                               │
+│                       │         │                                │
+│                       ↓         ↓                                │
+│                   [Continue]  [🎉 Complete!]                     │
+│                                                                  │
+│   NO STOPPING until acceptance criteria met or error limit hit   │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+### ULTRAWORK Example
+
+```
+User: /vibe.run "brick-game" ultrawork
+
+Claude:
+🚀 ULTRAWORK MODE ACTIVATED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+📄 SPEC: .claude/vibe/specs/brick-game.md
+🎯 4 Phases detected
+⚡ Boulder Loop: ENABLED (will continue until all phases complete)
+🔄 Auto-retry: ON (max 3 per phase)
+💾 Context compression: AGGRESSIVE
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🏔️ BOULDER ROLLING... Phase 1/4
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+⚡ [PARALLEL] Launching 3 exploration agents...
+✅ Exploration complete (7.2s)
+🔨 Implementing...
+✅ Phase 1 complete
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🏔️ BOULDER ROLLING... Phase 2/4
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+⚡ [PARALLEL] Launching 3 exploration agents...
+✅ Exploration complete (6.8s)
+🔨 Implementing...
+❌ Test failed: collision detection
+🔄 Auto-retry 1/3...
+🔨 Fixing...
+✅ Phase 2 complete
+
+[...continues automatically...]
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎉 BOULDER REACHED THE TOP!
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+✅ All 4 phases complete
+✅ All acceptance criteria passed
+✅ Build succeeded
+✅ Tests passed
+
+⏱️ Total: 8m 24s
+📊 Retries: 2
+💾 Context saved: 3 checkpoints
+```
+
+### Normal vs ULTRAWORK Comparison
+
+| Aspect | Normal | ULTRAWORK |
+|--------|--------|-----------|
+| Phase transition | May pause | Auto-continues |
+| On error | Reports and stops | Auto-retries (3x) |
+| Context 70%+ | Warning only | Auto-compress + save |
+| Exploration | Sequential possible | FORCED parallel |
+| Completion | Phase-by-phase | Until ALL done |
+
+---
+
+## Rules Reference
+
+**Must follow `~/.claude/vibe/rules/` (global):**
+
+- `core/development-philosophy.md` - Surgical precision, modify only requested scope
+- `core/quick-start.md` - Korean, DRY, SRP, YAGNI
+- `standards/complexity-metrics.md` - Functions ≤20 lines, nesting ≤3 levels
+- `quality/checklist.md` - Code quality checklist
+
+**Language guide:** `~/.claude/vibe/languages/{stack}.md` (global reference)
+
+## Description
+
+Read PTCF structured SPEC document and execute implementation immediately.
+
+> **PLAN, TASKS documents unnecessary** - SPEC is the executable prompt
+
+## Model Orchestration (Intelligent Routing)
+
+Automatically select optimal model based on **task complexity analysis**.
+
+### Complexity-Based Model Selection
+
+| Complexity Score | Model | When to Use |
+|------------------|-------|-------------|
+| 0-7 (Low) | **Haiku** | Simple fixes, searches, single file changes |
+| 8-19 (Medium) | **Sonnet** | Standard features, 3-5 files, integrations |
+| 20+ (High) | **Opus** | Architecture, security, multi-service, 6+ files |
+
+### Complexity Signals
+
+The following signals increase complexity score:
+
+| Signal | Score |
+|--------|-------|
+| Architecture change | +15 |
+| Security implication | +12 |
+| Multi-service | +8 |
+| Refactoring | +12 |
+| 6+ files | +15 |
+| 3-5 files | +8 |
+| New feature | +5 |
+| Bug fix | -3 |
+| Documentation | -5 |
+
+### Agent Tier System
+
+Each agent has tier variants for cost optimization:
+
+| Agent | Low (Haiku) | Medium (Sonnet) | High (Opus) |
+|-------|-------------|-----------------|-------------|
+| explorer | explorer-low | explorer-medium | explorer |
+| implementer | implementer-low | implementer-medium | implementer |
+| architect | architect-low | architect-medium | architect |
+
+### Task Calls by Role
+
+| Task Type | Model | Task Parameter |
+|-----------|-------|----------------|
+| Simple search | Haiku | `model: "haiku"` |
+| Codebase exploration | Haiku/Sonnet | Auto-selected |
+| Core implementation | Sonnet | `model: "sonnet"` |
+| Test writing | Haiku | `model: "haiku"` |
+| Architecture decisions | Opus | Main session |
+| Final review | Opus | Main session |
+
+### External LLM Usage (When Enabled)
+
+When external LLMs are enabled in `.claude/vibe/config.json`:
+
+| Role | Method | Condition |
+|------|--------|-----------|
+| User direct query | `gpt.question`, `gemini.question` | Hook auto-handles |
+| Internal orchestration | Call global script via Bash | Claude calls directly |
+
+**User questions (Hook auto-handles):**
+- `gpt.question` - GPT architecture consultation
+- `gemini.question` - Gemini Q&A/consultation
+
+**Claude internal calls (directly via Bash):**
+```bash
+# Usage: node llm-orchestrate.js <provider> <mode> [systemPrompt] [prompt]
+#   - If systemPrompt omitted, uses default
+#   - If systemPrompt is "-", uses default and treats next argument as prompt
+
+# Cross-platform path (works on Windows/macOS/Linux)
+VIBE_SCRIPTS="$(node -p "process.env.APPDATA || require('os').homedir() + '/.config'")/vibe/hooks/scripts"
+
+# GPT call
+node "$VIBE_SCRIPTS/llm-orchestrate.js" gpt orchestrate-json "[question content]"
+
+# Gemini call
+node "$VIBE_SCRIPTS/llm-orchestrate.js" gemini orchestrate-json "[question content]"
+
+# Custom system prompt usage
+node "$VIBE_SCRIPTS/llm-orchestrate.js" gpt orchestrate-json "You are a code reviewer" "[question content]"
+```
+
+### External LLM Fallback
+
+**IMPORTANT**: When GPT/Gemini hook fails, Claude MUST handle the task directly:
+
+**Fallback behavior**:
+- Do NOT retry the external LLM call
+- Claude handles the task using its own capabilities
+- Continue with the implementation without interruption
+- Log the fallback but don't block progress
+
+## Vibe Tools (Semantic Analysis & Memory)
+
+Use vibe tools for accurate codebase understanding and session continuity.
+
+### Tool Invocation
+
+All tools are called via:
+```bash
+node -e "import('@su-record/vibe/tools').then(t => t.TOOL_NAME({...args}).then(r => console.log(r.content[0].text)))"
+```
+
+### Semantic Analysis Tools
+
+| Tool | Purpose | Usage |
+|------|---------|-------|
+| `findSymbol` | Find symbol definitions | `{symbolName: 'functionName', searchPath: '.'}` |
+| `findReferences` | Find all references | `{symbolName: 'functionName', searchPath: '.'}` |
+| `analyzeComplexity` | Analyze code complexity | `{filePath: 'src/file.ts'}` |
+| `validateCodeQuality` | Validate code quality | `{filePath: 'src/file.ts'}` |
+
+**Example - Find symbol:**
+```bash
+node -e "import('@su-record/vibe/tools').then(t => t.findSymbol({symbolName: 'login', searchPath: '.'}).then(r => console.log(r.content[0].text)))"
+```
+
+### Memory Tools
+
+| Tool | Purpose | Usage |
+|------|---------|-------|
+| `saveMemory` | Save important decisions | `{key: 'decision-name', value: 'content', category: 'project'}` |
+| `recallMemory` | Recall saved memory | `{key: 'decision-name'}` |
+| `listMemories` | List all memories | `{category: 'project'}` |
+
+**Example - Save important decision:**
+```bash
+node -e "import('@su-record/vibe/tools').then(t => t.saveMemory({key: 'auth-pattern', value: 'Using JWT with refresh tokens', category: 'project'}).then(r => console.log(r.content[0].text)))"
+```
+
+### Session Management (Auto via Hooks)
+
+- **Session start**: Hook auto-calls `startSession` to restore previous context
+- **Context 80%+**: Hook auto-calls `autoSaveContext` to preserve state
+
+## Process
+
+### 1. Load SPEC + Feature
+
+```
+📄 .claude/vibe/specs/{feature-name}.md      → SPEC (structure, constraints, context)
+📄 .claude/vibe/features/{feature-name}.feature → Feature (scenario = implementation unit)
+```
+
+**Error if Feature file missing**:
+```
+❌ Feature file not found.
+   Run /vibe.spec "{feature-name}" first.
+```
+
+### 2. Extract Scenario List
+
+Extract all Scenarios from Feature file:
+
+```markdown
+## Scenarios to Implement
+
+| # | Scenario | Status |
+|---|----------|--------|
+| 1 | Valid login success | ⬜ |
+| 2 | Invalid password error | ⬜ |
+| 3 | Email format validation | ⬜ |
+| 4 | Password reset link | ⬜ |
+
+Total: 4 scenarios
+```
+
+### 3. Scenario-by-Scenario Implementation (Core)
+
+**For each scenario**:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 Scenario 1/4: Valid login success
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Given: User is registered
+When: Login with valid email and password
+Then: Login success + JWT token returned
+
+[Step 1] Analyzing implementation...
+  - Required files: auth.service.ts, login.controller.ts
+  - Exploring related code...
+
+[Step 2] Implementing...
+  ✅ auth.service.ts - Added login() method
+  ✅ login.controller.ts - POST /login endpoint
+
+[Step 3] Verifying...
+  ✅ Given: Test user creation possible
+  ✅ When: Login API call succeeded
+  ✅ Then: JWT token return confirmed
+
+✅ Scenario 1 passed!
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+**On failure**:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 Scenario 2/4: Invalid password error
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+[Step 3] Verifying...
+  ✅ Given: Test user exists
+  ✅ When: Login attempt with wrong password
+  ❌ Then: "Invalid credentials" error message
+     Actual: "Error occurred" returned
+
+[Auto-fix 1/3]
+  Cause: Error message not properly set
+  Fix: auth.service.ts line 42
+
+[Re-verify]
+  ✅ Then: "Invalid credentials" error message
+
+✅ Scenario 2 passed! (1 fix)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+---
+
+## **CRITICAL: Parallel Sub-Agent Execution**
+
+> **MUST USE PARALLEL TASK CALLS** - This is REQUIRED, not optional.
+> Sequential execution when parallel is possible = VIOLATION of this workflow.
+
+### Mandatory Parallel Exploration (Phase Start)
+
+**BEFORE any implementation, you MUST launch these Task calls IN PARALLEL (single message, multiple tool calls):**
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  STEP 1: PARALLEL EXPLORATION (REQUIRED)                        │
+│                                                                 │
+│  Launch ALL of these in ONE message:                            │
+│                                                                 │
+│  Task(haiku) ─┬─→ "Analyze related files in <context>"          │
+│               │                                                 │
+│  Task(haiku) ─┼─→ "Check dependencies and imports"              │
+│               │                                                 │
+│  Task(haiku) ─┴─→ "Find existing patterns and conventions"      │
+│                                                                 │
+│  [If GPT enabled] Bash: node {{VIBE_PATH}}/hooks/scripts/llm-orchestrate.js gpt orchestrate-json "[question]"
+│  [If Gemini enabled] Bash: node {{VIBE_PATH}}/hooks/scripts/llm-orchestrate.js gemini orchestrate-json "[question]"
+└─────────────────────────────────────────────────────────────────┘
+                              │
+                              ↓ (wait for all to complete)
+┌─────────────────────────────────────────────────────────────────┐
+│  STEP 2: SYNTHESIZE (Opus)                                      │
+│  - Review all exploration results                               │
+│  - Decide implementation approach                               │
+│  - Identify files to modify/create                              │
+└─────────────────────────────────────────────────────────────────┘
+                              │
+                              ↓
+┌─────────────────────────────────────────────────────────────────┐
+│  STEP 3: IMPLEMENT + BACKGROUND AGENTS (PARALLEL)               │
+│                                                                 │
+│  Main Agent (sonnet):                                           │
+│  └─→ Execute current phase implementation                       │
+│                                                                 │
+│  Background Agents (haiku, run_in_background=true):             │
+│  ├─→ Task: "Prepare Phase N+1 - analyze required files"         │
+│  ├─→ Task: "Pre-generate test cases for current implementation" │
+│  └─→ Task: "Search for related types/interfaces needed"         │
+│                                                                 │
+│  [ULTRAWORK] All 4 agents run simultaneously!                   │
+└─────────────────────────────────────────────────────────────────┘
+                              │
+                              ↓ (main completes, check backgrounds)
+┌─────────────────────────────────────────────────────────────────┐
+│  STEP 4: TEST + PHASE PIPELINING                                │
+│                                                                 │
+│  Current Phase:                                                 │
+│  └─→ Task(haiku): Write tests using pre-generated cases         │
+│                                                                 │
+│  Next Phase Prep (from background results):                     │
+│  └─→ Already have file analysis, ready to start immediately     │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+### Parallel Task Call Pattern (MUST FOLLOW)
+
+**Correct - Single message with multiple parallel Tasks:**
+```
+<message>
+  Task(haiku, "Analyze src/components/ for existing patterns")
+  Task(haiku, "Check package.json dependencies")
+  Task(haiku, "Find usage of similar features in codebase")
+</message>
+→ All 3 run simultaneously, ~3x faster
+```
+
+**WRONG - Sequential calls (DO NOT DO THIS):**
+```
+<message>Task(haiku, "Analyze...")</message>
+<message>Task(haiku, "Check...")</message>
+<message>Task(haiku, "Find...")</message>
+→ 3x slower, wastes time
+```
+
+### Background Agent Pattern (ULTRAWORK) via Orchestrator
+
+**Launch background agents for next phase via Orchestrator:**
+```bash
+# Start background agent (doesn't block)
+node -e "import('@su-record/vibe/orchestrator').then(o => o.runAgent('Phase 2 prep: Analyze auth API endpoints', 'phase2-prep').then(r => console.log(r.content[0].text)))"
+
+# Multiple backgrounds in parallel
+node -e "import('@su-record/vibe/orchestrator').then(async o => {
+  await Promise.all([
+    o.runAgent('Phase 2 prep: Analyze auth API endpoints', 'phase2-prep'),
+    o.runAgent('Pre-generate test cases for login form', 'test-prep'),
+    o.runAgent('Find existing validation patterns', 'pattern-finder')
+  ]);
+  console.log('All background agents started');
+})"
+```
+
+**Check background agent status:**
+```bash
+node -e "import('@su-record/vibe/orchestrator').then(o => console.log(o.status().content[0].text))"
+```
+
+**Get result when ready:**
+```bash
+node -e "import('@su-record/vibe/orchestrator').then(o => o.getResult('SESSION_ID').then(r => console.log(r.content[0].text)))"
+```
+
+**Why Background Agents Matter:**
+
+| Without Background | With Background |
+|--------------------|-----------------|
+| Phase 1: 60s | Phase 1: 60s (+ backgrounds running) |
+| Phase 2 prep: 20s | Phase 2 prep: 0s (already done!) |
+| Phase 2: 60s | Phase 2: 60s |
+| **Total: 140s** | **Total: 120s** |
+
+For 5 phases: 4 × 20s saved = **80s faster**
+
+### Why Parallel Matters
+
+| Approach | Time | Cache Benefit |
+|----------|------|---------------|
+| Sequential (3 Tasks) | ~30s | Cache cold on each |
+| **Parallel (3 Tasks)** | **~10s** | **Cache warmed once, shared** |
+
+vibe ProjectCache (LRU) caches ts-morph parsing results. Parallel calls share the warmed cache.
+
+### Phase Execution Flow (ULTRAWORK Pipeline)
+
+```
+Phase N Start
+    │
+    ├─→ [PARALLEL] Task(haiku) × 3: Exploration
+    │       - Related code analysis
+    │       - Dependency check
+    │       - Pattern discovery
+    │
+    ↓ (all complete)
+    │
+    ├─→ Opus: Synthesize and decide
+    │
+    ├─→ [PARALLEL PIPELINE] ←── KEY SPEED OPTIMIZATION
+    │       │
+    │       ├─→ Main: Task(sonnet) Implementation
+    │       │
+    │       └─→ Background (run_in_background=true):
+    │               ├─→ Task(haiku): Phase N+1 file analysis
+    │               ├─→ Task(haiku): Test case preparation
+    │               └─→ Task(haiku): Type/interface lookup
+    │
+    ↓ (main completes)
+    │
+    ├─→ Task(haiku): Tests (uses pre-generated cases)
+    │
+    ↓
+Phase N Complete
+    │
+    ↓ (Background results ready - NO WAIT for Phase N+1 exploration!)
+    │
+Phase N+1 Start (IMMEDIATE - exploration already done!)
+```
+
+**Speed Comparison:**
+
+| Mode | Phase Time | 5 Phases Total |
+|------|------------|----------------|
+| Sequential | ~2min/phase | ~10min |
+| Parallel Exploration | ~1.5min/phase | ~7.5min |
+| **ULTRAWORK Pipeline** | **~1min/phase** | **~5min** |
+
+**Why Pipeline is Faster:**
+- Background agents prepare next phase WHILE current phase implements
+- No idle time between phases
+- Test cases pre-generated during implementation
+- Cache stays warm across parallel tasks
+
+---
+
+1. **Related code analysis**: Task(haiku) explores `<context>` related code
+2. **File creation/modification**: Task(sonnet) implements per `<output_format>`
+3. **Constraint compliance**: Check `<constraints>`
+4. **Run verification**: Execute verification commands
+
+### 4. Gemini Code Review + Auto-Fix (NEW)
+
+After all scenarios are implemented, **Gemini reviews the code and auto-fixes based on feedback**:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🔍 GEMINI CODE REVIEW
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+[Step 1] Sending implementation code to Gemini...
+  - Changed files: auth.service.ts, auth.controller.ts, ...
+
+[Step 2] Gemini review results:
+  ┌─────────────────────────────────────────────────────┐
+  │ 📝 Gemini Feedback                                  │
+  │                                                     │
+  │ 1. [Improvement] auth.service.ts:24                 │
+  │    Need timing attack prevention for password compare│
+  │    → Recommend using crypto.timingSafeEqual()       │
+  │                                                     │
+  │ 2. [Improvement] auth.controller.ts:15              │
+  │    Rate limiting not applied                        │
+  │    → Recommend adding login attempt limit           │
+  │                                                     │
+  │ 3. [Style] auth.service.ts:42                       │
+  │    Magic number usage                               │
+  │    → Recommend extracting to constant               │
+  └─────────────────────────────────────────────────────┘
+
+[Step 3] Auto-fixing based on feedback...
+  ✅ auth.service.ts:24 - Applied timingSafeEqual
+  ✅ auth.controller.ts:15 - Added rate limiter
+  ✅ auth.service.ts:42 - Extracted constant
+
+[Step 4] Re-verifying...
+  ✅ Build succeeded
+  ✅ Tests passed
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ Gemini review complete! 3 improvements applied
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+**MUST: Gemini Code Review (Required)**
+
+When Gemini is enabled, **must** use global hook script for code review:
+
+```bash
+# Cross-platform path (works on Windows/macOS/Linux)
+VIBE_SCRIPTS="$(node -p "process.env.APPDATA || require('os').homedir() + '/.config'")/vibe/hooks/scripts"
+
+node "$VIBE_SCRIPTS/llm-orchestrate.js" gemini orchestrate-json "Review this code for security, performance, best-practices: [code summary]. SPEC: [summary]. Scenarios: [list]"
+```
+
+**Call sequence:**
+1. Summarize key content of changed files
+2. Add SPEC requirements summary
+3. Execute global script call
+4. Fix code for each feedback item in response
+5. Re-run build/tests
+
+**Fallback handling:**
+- On `"status": "fallback"` response → Skip and proceed to next step
+- On network error → Retry once, then skip
+
+**Review application rules:**
+
+| Feedback Type | Action |
+|---------------|--------|
+| Security vulnerability | Auto-fix immediately |
+| Performance improvement | Auto-fix immediately |
+| Best practices | Auto-fix |
+| Style/preference | Apply selectively (project convention takes priority) |
+
+**Conditions:**
+- Only runs when Gemini MCP is enabled (`vibe gemini auth`)
+- Skip and proceed on fallback response
+- Must re-verify build/tests after fixes
+
+### 5. Quality Report (Auto-generated)
+
+After all scenarios complete + Gemini review, **quality report is auto-generated**:
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  📊 QUALITY REPORT: login                                        │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                 │
+│  ✅ Scenarios: 4/4 passed                                       │
+│                                                                 │
+│  ┌───────────────────────────────────────────────────────────┐  │
+│  │ # │ Scenario                  │ Status │ Retries │        │  │
+│  │───│───────────────────────────│────────│─────────│        │  │
+│  │ 1 │ Valid login success       │ ✅     │ 0       │        │  │
+│  │ 2 │ Invalid password error    │ ✅     │ 1       │        │  │
+│  │ 3 │ Email format validation   │ ✅     │ 0       │        │  │
+│  │ 4 │ Password reset link       │ ✅     │ 0       │        │  │
+│  └───────────────────────────────────────────────────────────┘  │
+│                                                                 │
+│  📈 Quality score: 94/100                                       │
+│                                                                 │
+│  ┌─────────────────────────────────────────────────────────┐    │
+│  │ Item              │ Result │ Notes                       │    │
+│  │───────────────────│────────│─────────────────────────────│    │
+│  │ Build             │ ✅     │ npm run build succeeded     │    │
+│  │ Tests             │ ✅     │ 12/12 passed                │    │
+│  │ Type check        │ ✅     │ 0 errors                    │    │
+│  │ Complexity        │ ✅     │ All functions ≤30 lines     │    │
+│  │ Security          │ ✅     │ 0 vulnerabilities           │    │
+│  │ Gemini review     │ ✅     │ 3 improvements applied      │    │
+│  └─────────────────────────────────────────────────────────┘    │
+│                                                                 │
+│  ⏱️ Total time: 3m 42s                                          │
+│                                                                 │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+**What users should check**:
+- Scenario pass rate (4/4 = 100%)
+- Quality score (94/100)
+- Build/test status
+
+**This alone is enough to trust quality.**
+
+### 6. Update Feature File
+
+Auto-update scenario status:
+
+```markdown
+## Coverage
+
+| Scenario | SPEC AC | Status |
+|----------|---------|--------|
+| Valid login success | AC-1 | ✅ |
+| Invalid password error | AC-2 | ✅ |
+| Email format validation | AC-3 | ✅ |
+| Password reset link | AC-4 | ✅ |
+
+**Last verified**: 2024-01-15 14:32
+**Quality score**: 94/100
+```
+
+## TRUST 5 Principles
+
+Follow during implementation:
+
+| Principle | Description |
+|-----------|-------------|
+| **T**est-first | Write tests first |
+| **R**eadable | Clear code |
+| **U**nified | Consistent style |
+| **S**ecured | Consider security |
+| **T**rackable | Logging, monitoring |
+
+## Input
+
+- `.claude/vibe/specs/{feature-name}.md` (PTCF SPEC)
+- `.claude/vibe/features/{feature-name}.feature` (BDD)
+- `CLAUDE.md` (project context)
+
+## Output
+
+- Implemented code files
+- Test files
+- Updated SPEC document (checkmarks)
+
+## Example
+
+```
+User: /vibe.run "login"
+
+Claude:
+📄 Loading SPEC: .claude/vibe/specs/login.md
+📄 Loading Feature: .claude/vibe/features/login.feature
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+📋 Scenarios to Implement
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| # | Scenario | Status |
+|---|----------|--------|
+| 1 | Valid login success | ⬜ |
+| 2 | Invalid password error | ⬜ |
+| 3 | Email format validation | ⬜ |
+| 4 | Password reset link | ⬜ |
+
+Total: 4 scenarios
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 Scenario 1/4: Valid login success
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Given: User is registered
+When: Login with valid email and password
+Then: Login success + JWT token returned
+
+⚡ [PARALLEL] Exploring...
+✅ Exploration complete (2.1s)
+
+🔨 Implementing...
+  ✅ auth.service.ts - Added login()
+  ✅ auth.controller.ts - POST /login
+
+🔍 Verifying...
+  ✅ Given: OK
+  ✅ When: OK
+  ✅ Then: OK
+
+✅ Scenario 1 passed!
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 Scenario 2/4: Invalid password error
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🔨 Implementing...
+  ✅ auth.service.ts - Password validation logic
+
+🔍 Verifying...
+  ✅ Given: OK
+  ✅ When: OK
+  ❌ Then: "Invalid credentials" error message
+     Actual: "Error" returned
+
+🔄 Auto-fix 1/3...
+  Fix: auth.service.ts line 42
+
+🔍 Re-verifying...
+  ✅ Then: OK
+
+✅ Scenario 2 passed! (1 fix)
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 Scenario 3/4: Email format validation
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🔨 Implementing...
+🔍 Verifying...
+✅ Scenario 3 passed!
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 Scenario 4/4: Password reset link
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🔨 Implementing...
+🔍 Verifying...
+✅ Scenario 4 passed!
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🔍 GEMINI CODE REVIEW
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+📤 Sending code to Gemini...
+📝 Gemini feedback:
+  1. [Security] Need timing attack prevention → Fixing...
+  2. [Performance] Unnecessary DB call → Fixing...
+
+✅ 2 improvements auto-applied
+🔍 Re-verifying... ✅ Passed
+
+┌─────────────────────────────────────────────────────────────────┐
+│  📊 QUALITY REPORT: login                                        │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                 │
+│  ✅ Scenarios: 4/4 passed                                       │
+│                                                                 │
+│  | # | Scenario              | Status | Retries |               │
+│  |---|───────────────────────|───────|─────────|               │
+│  | 1 | Valid login success   | ✅    | 0       |               │
+│  | 2 | Invalid password error| ✅    | 1       |               │
+│  | 3 | Email format validation| ✅   | 0       |               │
+│  | 4 | Password reset link   | ✅    | 0       |               │
+│                                                                 │
+│  📈 Quality score: 94/100                                       │
+│  Build: ✅ | Tests: ✅ | Types: ✅ | Gemini: ✅ (2 applied)     │
+│                                                                 │
+│  ⏱️ Total time: 3m 42s                                          │
+└─────────────────────────────────────────────────────────────────┘
+
+🎉 Implementation complete! All scenarios passed + Gemini review applied.
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🔍 AUTO REVIEW (13+ Agents)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+⚡ [PARALLEL] 13 expert agents reviewing...
+  - security-reviewer ✅
+  - performance-reviewer ✅
+  - architecture-reviewer ✅
+  - ...
+
+📋 Review results:
+  - P1 Critical: 0
+  - P2 Important: 2
+  - P3 Nice-to-have: 1
+
+🔧 Auto-fixing P2 issues...
+  1. [PERF] N+1 query → Fixed
+  2. [ARCH] Circular dependency → Fixed
+
+✅ Auto Review complete! 2 issues auto-resolved.
+```
+
+### Phase-specific Execution
+
+```
+User: /vibe.run "brick-game" --phase 2
+
+Claude:
+📄 Reading SPEC: .claude/vibe/specs/brick-game.md
+🎯 Executing Phase 2 only.
+
+Phase 2: Game Logic
+1. [ ] Paddle movement implementation
+2. [ ] Ball physics engine
+3. [ ] Brick collision handling
+4. [ ] Score system
+5. [ ] Game over conditions
+
+⚡ Launching parallel exploration...
+[Task(haiku) × 3 launched in parallel]
+
+🚀 Starting implementation...
+```
+
+## Error Handling
+
+On failure:
+1. Check error message
+2. Review `<constraints>`
+3. Fix code and retry
+4. If continues to fail, report to user
+
+---
+
+## Quality Gate (Mandatory)
+
+### Implementation Quality Checklist
+
+Before marking any scenario as complete, ALL items must pass:
+
+| Category | Check Item | Weight |
+|----------|------------|--------|
+| **Functionality** | All Given/When/Then conditions verified | 20% |
+| **Functionality** | Edge cases handled per scenario | 10% |
+| **Code Quality** | No `any` types in TypeScript | 10% |
+| **Code Quality** | Functions ≤30 lines, nesting ≤3 levels | 10% |
+| **Code Quality** | No hardcoded values (use constants) | 5% |
+| **Security** | Input validation implemented | 10% |
+| **Security** | Authentication/authorization checked | 5% |
+| **Error Handling** | Try-catch or error states present | 10% |
+| **Error Handling** | User-friendly error messages | 5% |
+| **Testing** | Unit tests exist for core logic | 10% |
+| **Performance** | No N+1 queries or unnecessary loops | 5% |
+
+### Quality Score Calculation
+
+```
+Score = Σ(checked items × weight) / 100
+
+Grades:
+- 95-100: ✅ EXCELLENT - Ready to merge
+- 85-94:  ✅ GOOD - Minor improvements recommended
+- 70-84:  ⚠️ FAIR - Improvements required before merge
+- 0-69:   ❌ POOR - Major fixes needed
+```
+
+### Quality Gate Thresholds
+
+| Gate | Minimum Score | Condition |
+|------|---------------|-----------|
+| **Scenario Complete** | 85 | Each scenario must score ≥85 |
+| **Phase Complete** | 90 | Average of all scenarios ≥90 |
+| **Feature Complete** | 90 | All phases complete + Gemini review |
+
+### Auto-Fix Triggers
+
+| Issue Type | Auto-Fix Action |
+|------------|-----------------|
+| Missing error handling | Add try-catch wrapper |
+| Hardcoded values | Extract to constants file |
+| Missing input validation | Add validation schema |
+| Function too long | Suggest split points |
+| N+1 query detected | Add eager loading |
+
+### Forbidden Patterns (Block Merge)
+
+| Pattern | Why Forbidden | Detection |
+|---------|---------------|-----------|
+| `console.log` | Debug code in production | Regex scan |
+| `// TODO` without issue | Untracked work | Comment scan |
+| `any` type | Type safety bypass | TypeScript check |
+| `@ts-ignore` | Type error suppression | TypeScript check |
+| Empty catch blocks | Silent error swallowing | AST analysis |
+| Commented-out code | Dead code | Comment scan |
+
+---
+
+## Next Step
+
+```
+/vibe.verify "brick-game"
+```
+
+---
+
+ARGUMENTS: $ARGUMENTS