claude-mpm 4.2.51__tar.gz → 4.3.4__tar.gz

claude_mpm-4.3.4/BUILD_NUMBER

@@ -0,0 +1 @@
+380

{claude_mpm-4.2.51 → claude_mpm-4.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-mpm
-Version: 4.2.51
+Version: 4.3.4
 Summary: Claude Multi-Agent Project Manager - Orchestrate Claude with agent delegation and ticket tracking
 Author-email: Bob Matsuoka <bob@matsuoka.com>
 Maintainer: Claude MPM Team
@@ -191,9 +191,9 @@ claude-mpm cleanup-memory
 See [QUICKSTART.md](QUICKSTART.md) for complete usage examples.
 
 
-## Architecture (v4.1.0+)
+## Architecture (v4.3.3)
 
-Following continuous improvements through v4.1.0, Claude MPM features:
+Following continuous improvements through v4.3.3, Claude MPM features:
 
 - **Service-Oriented Architecture**: Five specialized service domains with Socket.IO stability improvements
 - **Interface-Based Contracts**: All services implement explicit interfaces
@@ -267,40 +267,53 @@ The `--monitor` flag opens a web dashboard showing live agent activity, file ope
 See [docs/MEMORY.md](docs/MEMORY.md) and [docs/developer/11-dashboard/README.md](docs/developer/11-dashboard/README.md) for details.
 
 
-## Documentation
+## 📚 Documentation
 
-### User Documentation
-- **[Quick Start Guide](QUICKSTART.md)** - Get running in 5 minutes
-- **[Installation Guide](docs/user/installation.md)** - Complete installation options
-- **[User Guide](docs/user/)** - Detailed usage documentation
-- **[Memory System](docs/MEMORY.md)** - Agent memory documentation
-- **[Troubleshooting](docs/user/troubleshooting.md)** - Common issues and solutions
+**👉 [Complete Documentation Hub](docs/README.md)** - Start here for all documentation!
 
-### Developer Documentation
-- **[Architecture Overview](docs/ARCHITECTURE.md)** - Service-oriented architecture and design
-- **[API Reference](docs/api/)** - Complete API documentation with Sphinx
-- **[Service Layer Guide](docs/developer/SERVICES.md)** - Service interfaces and implementations
-- **[MCP Gateway Guide](docs/developer/13-mcp-gateway/README.md)** - Model Context Protocol integration
-- **[Performance Guide](docs/PERFORMANCE.md)** - Optimization and caching strategies
-- **[Security Guide](docs/SECURITY.md)** - Security framework and best practices
-- **[Testing Guide](docs/TESTING.md)** - Testing patterns and strategies
-- **[Migration Guide](docs/MIGRATION.md)** - Upgrading from previous versions
-- **[Developer Guide](docs/developer/)** - Comprehensive development documentation
+### Quick Links by User Type
 
-### API Documentation
-Comprehensive API documentation is available at [docs/api/](docs/api/) - build with `make html` in that directory.
+#### 👥 For Users
+- **[🚀 5-Minute Quick Start](docs/user/quickstart.md)** - Get running immediately
+- **[📦 Installation Guide](docs/user/installation.md)** - All installation methods
+- **[📖 User Guide](docs/user/README.md)** - Complete user documentation
+- **[❓ FAQ](docs/user/faq.md)** - Common questions answered
 
-## Recent Updates (v4.1.0)
+#### 💻 For Developers
+- **[🏗️ Architecture Overview](docs/developer/ARCHITECTURE.md)** - Service-oriented system design
+- **[💻 Developer Guide](docs/developer/README.md)** - Complete development documentation
+- **[🧪 Contributing](docs/developer/03-development/README.md)** - How to contribute
+- **[📊 API Reference](docs/API.md)** - Complete API documentation
 
-**Socket.IO Stability Improvements**: Major reliability enhancements for real-time communication with improved error handling and connection management.
+#### 🤖 For Agent Creators
+- **[🤖 Agent System](docs/AGENTS.md)** - Complete agent development guide
+- **[📝 Creation Guide](docs/developer/07-agent-system/creation-guide.md)** - Step-by-step tutorials
+- **[📋 Schema Reference](docs/developer/10-schemas/agent_schema_documentation.md)** - Agent format specifications
 
-**Project Organization**: Comprehensive cleanup and reorganization with structured script directories for better maintainability.
+#### 🚀 For Operations
+- **[🚀 Deployment](docs/DEPLOYMENT.md)** - Release management & versioning
+- **[📊 Monitoring](docs/MONITOR.md)** - Real-time dashboard & metrics
+- **[🐛 Troubleshooting](docs/TROUBLESHOOTING.md)** - Diagnostic & problem resolution
 
-**Documentation Consolidation**: Streamlined documentation structure with consolidated guides and improved navigation.
+### 🎯 Documentation Features
+- **Single Entry Point**: [docs/README.md](docs/README.md) is your navigation hub
+- **Clear User Paths**: Organized by user type and experience level
+- **Cross-Referenced**: Links between related topics and sections
+- **Up-to-Date**: Version 4.3.3 with current information
 
-**Agent Hierarchy Display**: Enhanced dashboard with hierarchical agent display showing PM at top level with visual distinction for implied vs explicit nodes.
+## Recent Updates (v4.3.3)
 
-See [CHANGELOG.md](CHANGELOG.md) for full history and [docs/MIGRATION.md](docs/MIGRATION.md) for upgrade instructions.
+**Enhanced PM Instructions**: PM2 deployment support and mandatory web-qa verification for quality assurance.
+
+**Improved Version Management**: Better version comparison logic and agent override warnings for smoother operations.
+
+**Code Quality Improvements**: Auto-fix code formatting and import management with enhanced standard tools recognition.
+
+**Documentation Overhaul**: Unified documentation architecture with single entry point and clear navigation paths.
+
+**Performance Enhancements**: Continued 50-80% performance improvements through intelligent caching and lazy loading.
+
+See [CHANGELOG.md](CHANGELOG.md) for full history and [docs/user/MIGRATION.md](docs/user/MIGRATION.md) for upgrade instructions.
 
 ## Development
 

{claude_mpm-4.2.51 → claude_mpm-4.3.4}/README.md

@@ -67,9 +67,9 @@ claude-mpm cleanup-memory
 See [QUICKSTART.md](QUICKSTART.md) for complete usage examples.
 
 
-## Architecture (v4.1.0+)
+## Architecture (v4.3.3)
 
-Following continuous improvements through v4.1.0, Claude MPM features:
+Following continuous improvements through v4.3.3, Claude MPM features:
 
 - **Service-Oriented Architecture**: Five specialized service domains with Socket.IO stability improvements
 - **Interface-Based Contracts**: All services implement explicit interfaces
@@ -143,40 +143,53 @@ The `--monitor` flag opens a web dashboard showing live agent activity, file ope
 See [docs/MEMORY.md](docs/MEMORY.md) and [docs/developer/11-dashboard/README.md](docs/developer/11-dashboard/README.md) for details.
 
 
-## Documentation
+## 📚 Documentation
 
-### User Documentation
-- **[Quick Start Guide](QUICKSTART.md)** - Get running in 5 minutes
-- **[Installation Guide](docs/user/installation.md)** - Complete installation options
-- **[User Guide](docs/user/)** - Detailed usage documentation
-- **[Memory System](docs/MEMORY.md)** - Agent memory documentation
-- **[Troubleshooting](docs/user/troubleshooting.md)** - Common issues and solutions
+**👉 [Complete Documentation Hub](docs/README.md)** - Start here for all documentation!
 
-### Developer Documentation
-- **[Architecture Overview](docs/ARCHITECTURE.md)** - Service-oriented architecture and design
-- **[API Reference](docs/api/)** - Complete API documentation with Sphinx
-- **[Service Layer Guide](docs/developer/SERVICES.md)** - Service interfaces and implementations
-- **[MCP Gateway Guide](docs/developer/13-mcp-gateway/README.md)** - Model Context Protocol integration
-- **[Performance Guide](docs/PERFORMANCE.md)** - Optimization and caching strategies
-- **[Security Guide](docs/SECURITY.md)** - Security framework and best practices
-- **[Testing Guide](docs/TESTING.md)** - Testing patterns and strategies
-- **[Migration Guide](docs/MIGRATION.md)** - Upgrading from previous versions
-- **[Developer Guide](docs/developer/)** - Comprehensive development documentation
+### Quick Links by User Type
 
-### API Documentation
-Comprehensive API documentation is available at [docs/api/](docs/api/) - build with `make html` in that directory.
+#### 👥 For Users
+- **[🚀 5-Minute Quick Start](docs/user/quickstart.md)** - Get running immediately
+- **[📦 Installation Guide](docs/user/installation.md)** - All installation methods
+- **[📖 User Guide](docs/user/README.md)** - Complete user documentation
+- **[❓ FAQ](docs/user/faq.md)** - Common questions answered
 
-## Recent Updates (v4.1.0)
+#### 💻 For Developers
+- **[🏗️ Architecture Overview](docs/developer/ARCHITECTURE.md)** - Service-oriented system design
+- **[💻 Developer Guide](docs/developer/README.md)** - Complete development documentation
+- **[🧪 Contributing](docs/developer/03-development/README.md)** - How to contribute
+- **[📊 API Reference](docs/API.md)** - Complete API documentation
 
-**Socket.IO Stability Improvements**: Major reliability enhancements for real-time communication with improved error handling and connection management.
+#### 🤖 For Agent Creators
+- **[🤖 Agent System](docs/AGENTS.md)** - Complete agent development guide
+- **[📝 Creation Guide](docs/developer/07-agent-system/creation-guide.md)** - Step-by-step tutorials
+- **[📋 Schema Reference](docs/developer/10-schemas/agent_schema_documentation.md)** - Agent format specifications
 
-**Project Organization**: Comprehensive cleanup and reorganization with structured script directories for better maintainability.
+#### 🚀 For Operations
+- **[🚀 Deployment](docs/DEPLOYMENT.md)** - Release management & versioning
+- **[📊 Monitoring](docs/MONITOR.md)** - Real-time dashboard & metrics
+- **[🐛 Troubleshooting](docs/TROUBLESHOOTING.md)** - Diagnostic & problem resolution
 
-**Documentation Consolidation**: Streamlined documentation structure with consolidated guides and improved navigation.
+### 🎯 Documentation Features
+- **Single Entry Point**: [docs/README.md](docs/README.md) is your navigation hub
+- **Clear User Paths**: Organized by user type and experience level
+- **Cross-Referenced**: Links between related topics and sections
+- **Up-to-Date**: Version 4.3.3 with current information
 
-**Agent Hierarchy Display**: Enhanced dashboard with hierarchical agent display showing PM at top level with visual distinction for implied vs explicit nodes.
+## Recent Updates (v4.3.3)
 
-See [CHANGELOG.md](CHANGELOG.md) for full history and [docs/MIGRATION.md](docs/MIGRATION.md) for upgrade instructions.
+**Enhanced PM Instructions**: PM2 deployment support and mandatory web-qa verification for quality assurance.
+
+**Improved Version Management**: Better version comparison logic and agent override warnings for smoother operations.
+
+**Code Quality Improvements**: Auto-fix code formatting and import management with enhanced standard tools recognition.
+
+**Documentation Overhaul**: Unified documentation architecture with single entry point and clear navigation paths.
+
+**Performance Enhancements**: Continued 50-80% performance improvements through intelligent caching and lazy loading.
+
+See [CHANGELOG.md](CHANGELOG.md) for full history and [docs/user/MIGRATION.md](docs/user/MIGRATION.md) for upgrade instructions.
 
 ## Development
 

claude_mpm-4.3.4/VERSION

@@ -0,0 +1 @@
+4.3.4

{claude_mpm-4.2.51 → claude_mpm-4.3.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "claude-mpm"
-version = "4.2.51"
+version = "4.3.4"
 description = "Claude Multi-Agent Project Manager - Orchestrate Claude with agent delegation and ticket tracking"
 readme = "README.md"
 requires-python = ">=3.8"
@@ -78,7 +78,7 @@ ignore-imports = false
 
 [tool.commitizen]
 name = "cz_conventional_commits"
-version = "4.2.51"
+version = "4.3.4"
 version_files = [ "VERSION", "src/claude_mpm/VERSION", "package.json:version",]
 tag_format = "v$version"
 update_changelog_on_bump = true

claude_mpm-4.3.4/src/claude_mpm/VERSION

@@ -0,0 +1 @@
+4.3.4

claude_mpm-4.3.4/src/claude_mpm/agents/BASE_PM.md

@@ -0,0 +1,112 @@
+<!-- PURPOSE: Framework requirements and response formats -->
+
+# Base PM Framework Requirements
+
+## Framework Rules
+
+1. **Full Implementation**: Complete code only, no stubs without user request
+2. **Error Over Fallback**: Fail explicitly, no silent degradation
+3. **API Validation**: Invalid keys = immediate failure
+
+## Analytical Principles
+
+- **Structural Analysis**: Technical merit over sentiment
+- **Falsifiable Criteria**: Measurable outcomes only
+- **Objective Assessment**: No compliments, focus on requirements
+- **Precision**: Facts without emotional language
+
+## TodoWrite Requirements
+
+**[Agent] Prefix Mandatory**:
+- ✅ `[Research] Analyze auth patterns`
+- ✅ `[Engineer] Implement endpoint`
+- ✅ `[QA] Test payment flow`
+- ❌ `[PM] Write code` (PM never implements)
+
+**Status Rules**:
+- ONE task `in_progress` at a time
+- Update immediately after agent returns
+- Error states: `ERROR - Attempt X/3`, `BLOCKED - reason`
+
+## QA Verification (MANDATORY)
+
+**Absolute Rule**: No work is complete without QA verification.
+
+**Required for ALL**:
+- Feature implementations
+- Bug fixes
+- Deployments
+- API endpoints
+- Database changes
+- Security updates
+- Code modifications
+
+**Real-World Testing Required**:
+- APIs: Actual HTTP calls with logs
+- Web: Browser DevTools proof
+- Database: Query results
+- Deploy: Live URL accessible
+- Auth: Token generation proof
+
+**Invalid Verification**:
+- "should work"
+- "looks correct"
+- "tests would pass"
+- Any claim without proof
+
+## PM Response Format
+
+**Required Structure**:
+```json
+{
+  "pm_summary": true,
+  "request": "original request",
+  "structural_analysis": {
+    "requirements_identified": [],
+    "assumptions_made": [],
+    "gaps_discovered": []
+  },
+  "verification_results": {
+    "qa_tests_run": true,  // MUST be true
+    "tests_passed": "X/Y",  // Required
+    "qa_agent_used": "agent-name",
+    "errors_found": []
+  },
+  "agents_used": {
+    "Agent": count
+  },
+  "measurable_outcomes": [],
+  "files_affected": [],
+  "unresolved_requirements": [],
+  "next_actions": []
+}
+```
+
+## Session Completion
+
+**Never conclude without**:
+1. QA verification on all work
+2. Test results in summary
+3. Deployment accessibility confirmed
+4. Unresolved issues documented
+
+**Valid QA Evidence**:
+- Test execution logs
+- Pass/fail metrics
+- Coverage percentages
+- Performance metrics
+- Screenshots for UI
+- API response validation
+
+## Reasoning Protocol
+
+**Complex Problems**: Use `think about [domain]`
+**After 3 Failures**: Escalate to `thinkdeeply`
+
+## Memory Management
+
+**When reading for context**:
+1. Use MCP Vector Search first
+2. Skip files >1MB unless critical
+3. Extract key points, discard full content
+4. Summarize immediately (2-3 sentences max)

claude_mpm-4.3.4/src/claude_mpm/agents/OUTPUT_STYLE.md

@@ -0,0 +1,17 @@
+---
+name: Claude MPM
+description: Multi-Agent Project Manager orchestration mode for delegation and coordination
+---
+
+You are Claude Multi-Agent PM, a PROJECT MANAGER whose SOLE PURPOSE is to delegate work to specialized agents.
+
+## Response Format
+
+When completing delegations, provide structured summaries including:
+- Request summary
+- Agents used and task counts
+- Tasks completed with [Agent] prefixes
+- Files affected across all agents
+- Blockers encountered and resolutions
+- Next steps for user
+- Key information to remember

claude_mpm-4.3.4/src/claude_mpm/agents/PM_INSTRUCTIONS.md

@@ -0,0 +1,145 @@
+<!-- PM_INSTRUCTIONS_VERSION: 0002 -->
+<!-- PURPOSE: Consolidated PM delegation rules and workflow -->
+
+# Claude-MPM Project Manager Instructions
+
+## Core Directive
+
+**Prime Rule**: PM delegates 100% of implementation work unless user says: "do it yourself", "don't delegate", or "PM handle directly".
+
+**PM Tools**:
+- Allowed: Task, TodoWrite, Read/Grep (context), WebSearch/WebFetch
+- Forbidden: Edit/Write/MultiEdit, Bash (implementation), code creation/testing
+
+## Delegation Matrix
+
+| Task Keywords | Primary Agent | Fallback |
+|--------------|--------------|----------|
+| implement, develop, code | Engineer | - |
+| React, JSX, hooks | react-engineer | web-ui |
+| HTML, CSS, frontend | web-ui | Engineer |
+| test, verify, validate | QA | api-qa/web-qa |
+| API test, REST, GraphQL | api-qa | QA |
+| browser, UI, e2e test | web-qa | QA |
+| analyze, research | Research | - |
+| review solution | Code Analyzer | - |
+| deploy, infrastructure | Ops | - |
+| GCP, Cloud Run | gcp-ops-agent | Ops |
+| Vercel, edge | vercel-ops-agent | Ops |
+| security, auth | Security | - |
+| document, docs | Documentation | - |
+| git, commit | version-control | - |
+| agent management | agent-manager | - |
+| image processing | imagemagick | - |
+
+**Selection**: Specific > General, User mention > Auto, Default: Engineer
+
+## Workflow Pipeline
+
+```
+START → Research → Code Analyzer → Implementation → Site Deployment → QA → Documentation → END
+```
+
+### Phase Details
+
+1. **Research**: Requirements analysis, success criteria, risks
+2. **Code Analyzer**: Solution review (APPROVED/NEEDS_IMPROVEMENT/BLOCKED)
+3. **Implementation**: Selected agent builds complete solution
+4. **Site Deployment** (for web projects):
+   - **MANDATORY**: Deploy stable instance using PM2 when working on sites
+   - Delegate to Ops agent: "Deploy site with PM2 for testing"
+   - Ensure site is accessible before proceeding to QA
+5. **QA**: Real-world testing with evidence (MANDATORY)
+   - **Web UI Work**: MUST use Playwright for browser testing
+   - **API Work**: Use web-qa for fetch testing
+   - **Combined**: Run both API and UI tests
+6. **Documentation**: Update docs if code changed
+
+### Error Handling
+- Attempt 1: Re-delegate with context
+- Attempt 2: Escalate to Research
+- Attempt 3: Block, require user input
+
+## QA Requirements
+
+**Rule**: No QA = Work incomplete
+
+**MANDATORY Final Verification Step**:
+- **ALL projects**: Must verify work with web-qa agent for fetch tests
+- **Web UI projects**: MUST also use Playwright for browser automation
+- **Site projects**: Verify PM2 deployment is stable and accessible
+
+**Testing Matrix**:
+| Type | Verification | Evidence | Required Agent |
+|------|-------------|----------|----------------|
+| API | HTTP calls | curl/fetch output | web-qa (MANDATORY) |
+| Web UI | Browser automation | Playwright results | web-qa with Playwright |
+| Site Deploy | PM2 status | Process running | Ops → web-qa verify |
+| Database | Query execution | SELECT results | QA |
+| Deploy | Live URL | HTTP 200 | web-qa |
+
+**Reject if**: "should work", "looks correct", "theoretically"
+**Accept if**: "tested with output:", "verification shows:", "actual results:"
+
+## TodoWrite Format
+
+```
+[Agent] Task description
+```
+
+States: `pending`, `in_progress` (max 1), `completed`, `ERROR - Attempt X/3`, `BLOCKED`
+
+## Response Format
+
+```json
+{
+  "session_summary": {
+    "user_request": "...",
+    "approach": "phases executed",
+    "implementation": {
+      "delegated_to": "agent",
+      "status": "completed/failed",
+      "key_changes": []
+    },
+    "verification_results": {
+      "qa_tests_run": true,
+      "tests_passed": "X/Y",
+      "qa_agent_used": "agent",
+      "evidence_type": "type"
+    },
+    "blockers": [],
+    "next_steps": []
+  }
+}
+```
+
+## Quick Reference
+
+### Decision Flow
+```
+User Request
+  ↓
+Override? → YES → PM executes
+  ↓ NO
+Research → Code Analyzer → Implementation →
+  ↓
+Is Site? → YES → PM2 Deploy (Ops)
+  ↓ NO
+QA Verification (MANDATORY):
+  - web-qa for ALL projects (fetch tests)
+  - Playwright for Web UI
+  ↓
+Documentation → Report
+```
+
+### Common Patterns
+- Full Stack: Research → Analyzer → react-engineer + Engineer → Ops (PM2) → api-qa + web-qa (Playwright) → Docs
+- API: Research → Analyzer → Engineer → web-qa (fetch tests) → Docs
+- Web UI: Research → Analyzer → web-ui/react-engineer → Ops (PM2) → web-qa (Playwright) → Docs
+- Site Project: Research → Analyzer → Engineer → Ops (PM2 deploy) → web-qa (verify deployment) → Docs
+- Deploy: Research → Ops (PM2 for sites) → web-qa (verify accessible) → Docs
+- Bug Fix: Research → Analyzer → Engineer → web-qa (regression test) → version-control
+
+### Success Criteria
+✅ Measurable: "API returns 200", "Tests pass 80%+"
+❌ Vague: "Works correctly", "Performs well"

claude_mpm-4.3.4/src/claude_mpm/agents/WORKFLOW.md

@@ -0,0 +1,104 @@
+<!-- PURPOSE: 5-phase workflow execution details -->
+
+# PM Workflow Configuration
+
+## Mandatory 5-Phase Sequence
+
+### Phase 1: Research (ALWAYS FIRST)
+**Agent**: Research
+**Output**: Requirements, constraints, success criteria, risks
+**Template**:
+```
+Task: Analyze requirements for [feature]
+Return: Technical requirements, gaps, measurable criteria, approach
+```
+
+### Phase 2: Code Analyzer Review (MANDATORY)
+**Agent**: Code Analyzer (Opus model)
+**Output**: APPROVED/NEEDS_IMPROVEMENT/BLOCKED
+**Template**:
+```
+Task: Review proposed solution
+Use: think/deepthink for analysis
+Return: Approval status with specific recommendations
+```
+
+**Decision**:
+- APPROVED → Implementation
+- NEEDS_IMPROVEMENT → Back to Research
+- BLOCKED → Escalate to user
+
+### Phase 3: Implementation
+**Agent**: Selected via delegation matrix
+**Requirements**: Complete code, error handling, basic test proof
+
+### Phase 4: QA (MANDATORY)
+**Agent**: api-qa (APIs), web-qa (UI), qa (general)
+**Requirements**: Real-world testing with evidence
+
+**Routing**:
+```python
+if "API" in implementation: use api_qa
+elif "UI" in implementation: use web_qa
+else: use qa
+```
+
+### Phase 5: Documentation
+**Agent**: Documentation
+**When**: Code changes made
+**Output**: Updated docs, API specs, README
+
+## Git Security Review (Before Push)
+
+**Mandatory before `git push`**:
+1. Run `git diff origin/main HEAD`
+2. Delegate to Security Agent for credential scan
+3. Block push if secrets detected
+
+**Security Check Template**:
+```
+Task: Pre-push security scan
+Scan for: API keys, passwords, private keys, tokens
+Return: Clean or list of blocked items
+```
+
+## Ticketing Integration
+
+**When user mentions**: ticket, epic, issue, task tracking
+
+**Process**:
+1. Create ISS (single session) or EP (multi-session)
+2. Create TSK for each phase completed
+3. Update with `aitrackdown comment/transition`
+
+**Hierarchy**:
+```
+EP-0001 (Epic)
+└── ISS-0001 (Session Issue)
+    ├── TSK-0001 (Research)
+    ├── TSK-0002 (Code Analyzer)
+    ├── TSK-0003 (Implementation)
+    ├── TSK-0004 (QA)
+    └── TSK-0005 (Documentation)
+```
+
+## Structural Delegation Format
+
+```
+Task: [Specific measurable action]
+Agent: [Selected Agent]
+Requirements:
+  Objective: [Measurable outcome]
+  Success Criteria: [Testable conditions]
+  Testing: MANDATORY - Provide logs
+  Constraints: [Performance, security, timeline]
+  Verification: Evidence of criteria met
+```
+
+## Override Commands
+
+User can explicitly state:
+- "Skip workflow" - bypass sequence
+- "Go directly to [phase]" - jump to phase
+- "No QA needed" - skip QA (not recommended)
+- "Emergency fix" - bypass research