nwave-ai 1.1.0__tar.gz

nwave_ai-1.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Alessandro Digioia & Michele Brissoni
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

nwave_ai-1.1.0/PKG-INFO

@@ -0,0 +1,205 @@
+Metadata-Version: 2.4
+Name: nwave-ai
+Version: 1.1.0
+Summary: CLI installer for the nWave AI methodology framework
+Project-URL: Homepage, https://github.com/nwave-ai/nwave
+Project-URL: Documentation, https://github.com/nwave-ai/nwave#readme
+Project-URL: Repository, https://github.com/nwave-ai/nwave
+Project-URL: Issues, https://github.com/nwave-ai/nwave/issues
+Author-email: Michele Brissoni <michele.brissoni@brix.consulting>, Alessandro Digioia <alessandro.digioia@brix.consulting>, nWave AI <info@nwave.ai>
+License: MIT
+License-File: LICENSE
+Keywords: ai,automation,cli,developer-tools,installer
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: System :: Installation/Setup
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: packaging>=21.0
+Requires-Dist: platformdirs>=4.2.0
+Requires-Dist: pydantic-settings>=2.1.0
+Requires-Dist: pydantic>=2.5.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.7.0
+Requires-Dist: typer>=0.12.0
+Provides-Extra: dev
+Requires-Dist: allure-pytest>=2.13.0; extra == 'dev'
+Requires-Dist: bandit[toml]>=1.7.0; extra == 'dev'
+Requires-Dist: click>=8.0.0; extra == 'dev'
+Requires-Dist: colorama>=0.4.0; extra == 'dev'
+Requires-Dist: commitizen>=3.12.0; extra == 'dev'
+Requires-Dist: cosmic-ray>=8.4.0; extra == 'dev'
+Requires-Dist: detect-secrets>=1.4.0; extra == 'dev'
+Requires-Dist: fpdf2>=2.7.0; extra == 'dev'
+Requires-Dist: gitlint>=0.19.0; extra == 'dev'
+Requires-Dist: mutmut>=2.4.0; extra == 'dev'
+Requires-Dist: mypy>=1.8.0; extra == 'dev'
+Requires-Dist: pre-commit>=3.6.0; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23.0; extra == 'dev'
+Requires-Dist: pytest-bdd>=7.0.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.1.0; extra == 'dev'
+Requires-Dist: pytest-describe-it>=0.1.0; extra == 'dev'
+Requires-Dist: pytest-describe>=2.1.0; extra == 'dev'
+Requires-Dist: pytest-html>=4.0.0; extra == 'dev'
+Requires-Dist: pytest-mock>=3.12.0; extra == 'dev'
+Requires-Dist: pytest-pspec>=0.0.4; extra == 'dev'
+Requires-Dist: pytest-watch>=4.2.0; extra == 'dev'
+Requires-Dist: pytest-xdist>=3.5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0.0; extra == 'dev'
+Requires-Dist: python-semantic-release>=9.0.0; extra == 'dev'
+Requires-Dist: respx>=0.20.0; extra == 'dev'
+Requires-Dist: ruff==0.15.0; extra == 'dev'
+Requires-Dist: tqdm>=4.64.0; extra == 'dev'
+Provides-Extra: test
+Requires-Dist: pytest-asyncio>=0.23.0; extra == 'test'
+Requires-Dist: pytest-bdd>=7.0.0; extra == 'test'
+Requires-Dist: pytest-cov>=4.1.0; extra == 'test'
+Requires-Dist: pytest-xdist>=3.5.0; extra == 'test'
+Requires-Dist: pytest>=8.0.0; extra == 'test'
+Requires-Dist: respx>=0.20.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+# nWave: Acceptance Test Driven Development with AI
+
+A framework for systematic software development using ATDD (Acceptance Test Driven Development) with intelligent AI agent orchestration. nWave guides you through a 6-wave workflow (DISCOVER, DISCUSS, DESIGN, DISTILL, DEVELOP, DELIVER) with 22 specialized agents providing evidence-based decision making, architecture design, test-driven implementation, and production readiness validation.
+
+## Install
+
+```bash
+pipx install nwave-ai
+nwave-ai install
+```
+
+Close and reopen Claude Code. The nWave agents and slash commands will appear in your command palette.
+
+## Quick Start
+
+After installation, use nWave commands in any Claude Code project:
+
+```bash
+# Product discovery and requirements gathering
+/nw:discover "market research for feature X"
+/nw:discuss "feature requirements"
+
+# Design and testing
+/nw:design --architecture=hexagonal
+/nw:distill "acceptance test scenarios"
+
+# Implementation and quality assurance
+/nw:baseline "measure current state"
+/nw:roadmap "create implementation plan"
+/nw:split "break into atomic tasks"
+/nw:execute "run individual task"
+/nw:review "quality check"
+/nw:deliver "production readiness"
+```
+
+For guidance on workflow selection, see the [Jobs To Be Done Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/jobs-to-be-done-guide.md).
+
+## Core Concepts
+
+### 6-Wave ATDD Workflow
+
+Each wave produces validated artifacts with input from specialized agents:
+
+- **DISCOVER** - Evidence-based product discovery
+- **DISCUSS** - Requirements gathering and business analysis
+- **DESIGN** - Architecture design with technology selection
+- **DISTILL** - BDD acceptance tests that define "done"
+- **DEVELOP** - Outside-in TDD implementation with atomic tasks
+- **DELIVER** - Production readiness validation
+
+### 22 Specialized Agents
+
+- **11 Primary Agents**: One per wave plus cross-wave specialists (researcher, troubleshooter, data-engineer, documentarist, agent-builder)
+- **11 Reviewer Agents**: Peer review with equal expertise reducing bias
+
+### 18 Slash Commands
+
+Wave commands (/nw:discover, /nw:discuss, /nw:design, /nw:distill, /nw:deliver, /nw:devops); execution commands (/nw:roadmap, /nw:execute, /nw:review, /nw:finalize); cross-wave commands (/nw:research, /nw:document, /nw:root-why, /nw:refactor, /nw:mikado, /nw:mutation-test); and utilities (/nw:diagram, /nw:forge).
+
+### DES: Deterministic Execution System
+
+DES enforces execution discipline through Claude Code hooks:
+
+- Pre-task validation and post-tool-use monitoring
+- Comprehensive audit logging for compliance and debugging
+- Configurable per-project via `.nwave/des-config.json`
+
+### 5-Layer Quality Assurance
+
+Layer 1: Unit testing; Layer 2: Integration testing; Layer 3: Adversarial validation; Layer 4: Peer review; Layer 5: Mutation testing.
+
+## What Gets Installed
+
+The installer configures 22 agents, 18 commands, templates, skills, and DES hooks in `~/.claude/`, making them available across all Claude Code projects.
+
+Installation layout includes:
+
+- Agent specifications in `~/.claude/agents/nw/`
+- Command definitions in `~/.claude/commands/nw/`
+- Templates and skills in `~/.claude/templates/` and `~/.claude/skills/`
+- DES runtime and hooks in `~/.claude/`
+
+## Requirements
+
+- **Python 3.10+**
+- **Claude Code CLI**
+
+## Usage
+
+```bash
+# Install nWave framework
+nwave-ai install
+
+# Preview changes without installing
+nwave-ai install --dry-run
+
+# Backup before updating
+nwave-ai install --backup-only
+
+# Restore from backup
+nwave-ai install --restore
+
+# Show version
+nwave-ai version
+
+# Uninstall
+nwave-ai uninstall
+```
+
+For detailed installation instructions and troubleshooting, see the [Installation Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/installation-guide.md).
+
+## Documentation
+
+- **[Installation Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/installation-guide.md)** - Step-by-step setup
+- **[Jobs To Be Done Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/jobs-to-be-done-guide.md)** - When to use each workflow
+- **[Commands Reference](https://github.com/nwave-ai/nwave/tree/main/docs/reference/nwave-commands-reference.md)** - All commands and agents
+- **[5-Layer Testing Guides](https://github.com/nwave-ai/nwave/tree/main/docs/guides/)** - Quality assurance workflows
+- **[DES API Reference](https://github.com/nwave-ai/nwave/tree/main/docs/reference/des-orchestrator-api.md)** - Execution system API
+- **[Plugin Architecture](https://github.com/nwave-ai/nwave/tree/main/docs/reference/nwave-plugin-architecture.md)** - Plugin system reference
+- **[Troubleshooting Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/troubleshooting-guide.md)** - Common issues and solutions
+
+Complete documentation: [github.com/nwave-ai/nwave/tree/main/docs](https://github.com/nwave-ai/nwave/tree/main/docs)
+
+## Community
+
+Join the **[nWave Discord community](https://discord.gg/DeYdSNk6)** for help, discussions, and to share your experience.
+
+## License
+
+MIT License. See [LICENSE](https://github.com/nwave-ai/nwave/blob/main/LICENSE) for details.
+
+## Source
+
+[github.com/nwave-ai/nwave](https://github.com/nwave-ai/nwave)

nwave_ai-1.1.0/README.md

@@ -0,0 +1,134 @@
+# nWave: Acceptance Test Driven Development with AI
+
+A framework for systematic software development using ATDD (Acceptance Test Driven Development) with intelligent AI agent orchestration. nWave guides you through a 6-wave workflow (DISCOVER, DISCUSS, DESIGN, DISTILL, DEVELOP, DELIVER) with 22 specialized agents providing evidence-based decision making, architecture design, test-driven implementation, and production readiness validation.
+
+## Install
+
+```bash
+pipx install nwave-ai
+nwave-ai install
+```
+
+Close and reopen Claude Code. The nWave agents and slash commands will appear in your command palette.
+
+## Quick Start
+
+After installation, use nWave commands in any Claude Code project:
+
+```bash
+# Product discovery and requirements gathering
+/nw:discover "market research for feature X"
+/nw:discuss "feature requirements"
+
+# Design and testing
+/nw:design --architecture=hexagonal
+/nw:distill "acceptance test scenarios"
+
+# Implementation and quality assurance
+/nw:baseline "measure current state"
+/nw:roadmap "create implementation plan"
+/nw:split "break into atomic tasks"
+/nw:execute "run individual task"
+/nw:review "quality check"
+/nw:deliver "production readiness"
+```
+
+For guidance on workflow selection, see the [Jobs To Be Done Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/jobs-to-be-done-guide.md).
+
+## Core Concepts
+
+### 6-Wave ATDD Workflow
+
+Each wave produces validated artifacts with input from specialized agents:
+
+- **DISCOVER** - Evidence-based product discovery
+- **DISCUSS** - Requirements gathering and business analysis
+- **DESIGN** - Architecture design with technology selection
+- **DISTILL** - BDD acceptance tests that define "done"
+- **DEVELOP** - Outside-in TDD implementation with atomic tasks
+- **DELIVER** - Production readiness validation
+
+### 22 Specialized Agents
+
+- **11 Primary Agents**: One per wave plus cross-wave specialists (researcher, troubleshooter, data-engineer, documentarist, agent-builder)
+- **11 Reviewer Agents**: Peer review with equal expertise reducing bias
+
+### 18 Slash Commands
+
+Wave commands (/nw:discover, /nw:discuss, /nw:design, /nw:distill, /nw:deliver, /nw:devops); execution commands (/nw:roadmap, /nw:execute, /nw:review, /nw:finalize); cross-wave commands (/nw:research, /nw:document, /nw:root-why, /nw:refactor, /nw:mikado, /nw:mutation-test); and utilities (/nw:diagram, /nw:forge).
+
+### DES: Deterministic Execution System
+
+DES enforces execution discipline through Claude Code hooks:
+
+- Pre-task validation and post-tool-use monitoring
+- Comprehensive audit logging for compliance and debugging
+- Configurable per-project via `.nwave/des-config.json`
+
+### 5-Layer Quality Assurance
+
+Layer 1: Unit testing; Layer 2: Integration testing; Layer 3: Adversarial validation; Layer 4: Peer review; Layer 5: Mutation testing.
+
+## What Gets Installed
+
+The installer configures 22 agents, 18 commands, templates, skills, and DES hooks in `~/.claude/`, making them available across all Claude Code projects.
+
+Installation layout includes:
+
+- Agent specifications in `~/.claude/agents/nw/`
+- Command definitions in `~/.claude/commands/nw/`
+- Templates and skills in `~/.claude/templates/` and `~/.claude/skills/`
+- DES runtime and hooks in `~/.claude/`
+
+## Requirements
+
+- **Python 3.10+**
+- **Claude Code CLI**
+
+## Usage
+
+```bash
+# Install nWave framework
+nwave-ai install
+
+# Preview changes without installing
+nwave-ai install --dry-run
+
+# Backup before updating
+nwave-ai install --backup-only
+
+# Restore from backup
+nwave-ai install --restore
+
+# Show version
+nwave-ai version
+
+# Uninstall
+nwave-ai uninstall
+```
+
+For detailed installation instructions and troubleshooting, see the [Installation Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/installation-guide.md).
+
+## Documentation
+
+- **[Installation Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/installation-guide.md)** - Step-by-step setup
+- **[Jobs To Be Done Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/jobs-to-be-done-guide.md)** - When to use each workflow
+- **[Commands Reference](https://github.com/nwave-ai/nwave/tree/main/docs/reference/nwave-commands-reference.md)** - All commands and agents
+- **[5-Layer Testing Guides](https://github.com/nwave-ai/nwave/tree/main/docs/guides/)** - Quality assurance workflows
+- **[DES API Reference](https://github.com/nwave-ai/nwave/tree/main/docs/reference/des-orchestrator-api.md)** - Execution system API
+- **[Plugin Architecture](https://github.com/nwave-ai/nwave/tree/main/docs/reference/nwave-plugin-architecture.md)** - Plugin system reference
+- **[Troubleshooting Guide](https://github.com/nwave-ai/nwave/tree/main/docs/guides/troubleshooting-guide.md)** - Common issues and solutions
+
+Complete documentation: [github.com/nwave-ai/nwave/tree/main/docs](https://github.com/nwave-ai/nwave/tree/main/docs)
+
+## Community
+
+Join the **[nWave Discord community](https://discord.gg/DeYdSNk6)** for help, discussions, and to share your experience.
+
+## License
+
+MIT License. See [LICENSE](https://github.com/nwave-ai/nwave/blob/main/LICENSE) for details.
+
+## Source
+
+[github.com/nwave-ai/nwave](https://github.com/nwave-ai/nwave)

nwave_ai-1.1.0/nWave/README.md

@@ -0,0 +1,169 @@
+<!-- version: 1.5.2 -->
+
+# nWave Framework
+
+## Overview
+
+The nWave framework implements the comprehensive DISCOVER→DISCUSS→DESIGN→DEVOP→DISTILL→DELIVER methodology. This framework provides a streamlined, integrated workflow with complete knowledge preservation for critical technical execution agents and comprehensive 5-layer testing framework.
+
+## nWave Methodology
+
+The nWave methodology implements a systematic approach to software development through six distinct waves:
+
+1. **DISCOVER**: Evidence-based product discovery and market validation
+2. **DISCUSS**: Requirements gathering and business analysis
+3. **DESIGN**: Architecture design with visual representation
+4. **DEVOP**: Platform readiness, CI/CD, infrastructure, and deployment design
+5. **DISTILL**: Acceptance test creation and business validation scenarios
+6. **DELIVER**: Outside-In TDD implementation with production readiness validation
+
+## Core and Specialist Agents (10 Total)
+
+### 🌊 nWave Core Agents
+
+1. **product-discoverer** → DISCOVER wave (evidence-based discovery)
+2. **business-analyst** → DISCUSS wave (requirements gathering)
+3. **solution-architect** → DESIGN wave (architecture & technology)
+4. **acceptance-designer** → DISTILL wave (test scenarios)
+5. **test-first-developer** → DELIVER wave (outside-in TDD)
+6. **feature-completion-coordinator** → DELIVER wave (production readiness)
+
+### 🔧 Specialist Agents (Standalone & Collaborative)
+
+7. **systematic-refactorer** → Essential for Level 1-6 refactoring
+8. **mikado-refactoring-specialist-enhanced** → Complex refactoring roadmaps
+9. **root-cause-analyzer** → Debugging, post-mortem, problem research
+10. **architecture-diagram-manager** → Visual architecture maintenance & updates
+
+## Command Structure
+
+### nWave Core Commands (DW Prefix)
+
+- `/nw:discover [product-concept]` - Wave 1: Evidence-based product discovery
+- `/nw:discuss [requirements]` - Wave 2: Business analysis
+- `/nw:design [system-context]` - Wave 3: Architecture design
+- `/nw:devops [deployment-target]` - Wave 4: Platform readiness and infrastructure
+- `/nw:distill [acceptance-criteria]` - Wave 5: Test scenarios
+- `/nw:deliver [feature-description]` - Wave 6: Outside-In TDD implementation
+
+### Specialist Commands
+
+- `/nw:mikado [target] [options]` - Complex refactoring roadmaps
+- `/nw:root-why [problem-description]` - Root cause analysis & debugging
+- `/nw:diagram [scope] [action]` - Architecture diagram management
+
+## Knowledge Preservation Guarantee
+
+This expansion pack implements **ZERO KNOWLEDGE REDUCTION** for the three critical technical execution agents:
+
+- **test-first-developer**: Complete 925-line methodology preserved
+- **systematic-refactorer**: COMPLETE refactoring mechanics database (24 techniques + safety protocols)
+- **mikado-refactoring-specialist-enhanced**: Full enhanced methodology with discovery tracking
+
+## Workflow Templates
+
+### Greenfield Development
+
+Complete greenfield project development with full visual architecture lifecycle.
+
+### Brownfield Integration
+
+Legacy system enhancement with visual refactoring roadmaps and systematic improvement.
+
+### Rapid Prototyping
+
+Streamlined validation workflow with essential visual architecture and accelerated feedback.
+
+## Architecture Diagram Integration
+
+The architecture-diagram-manager provides complete visual architecture lifecycle management:
+
+- **Creation**: Architecture diagrams from solution-architect decisions
+- **Evolution**: Real-time updates throughout development
+- **Validation**: Visual verification against implementation
+- **Synchronization**: Coordination with refactoring and development progress
+
+## Installation
+
+1. Place this framework in your nWave installation:
+
+   ```
+   nwave/nWave/
+   ```
+
+2. Update your configuration to include the nWave framework.
+
+3. Agents will be available via the standard agent syntax.
+
+## Usage Examples
+
+### Execute Full nWave Cycle
+
+**Option 1: Automated DELIVER Wave (Recommended)**
+```bash
+/nw:discover "User authentication market research"
+/nw:discuss "User registration and login requirements"
+/nw:design "Microservices with JWT authentication"
+/nw:distill "User can register and login securely"
+/nw:devops "user-authentication"
+/nw:distill "User can register and login securely"
+/nw:deliver "Implement user authentication with JWT"
+  # Automatically: roadmap → execute all steps → finalize
+  # Quality gates: 3 + 3N reviews (e.g., 10 steps = 33 reviews)
+```
+
+**Option 2: Manual Granular Control (Advanced)**
+```bash
+# DISCOVER and DISCUSS and DESIGN waves
+/nw:discover "User authentication market research"
+/nw:discuss "User registration requirements"
+/nw:design "JWT authentication architecture"
+
+# DELIVER wave - manual orchestration
+/nw:roadmap @solution-architect "Implement user authentication"
+
+# Execute individual steps with 11-phase TDD
+/nw:execute @software-crafter "docs/feature/user-authentication/steps/01-01.json"
+/nw:execute @software-crafter "docs/feature/user-authentication/steps/01-02.json"
+# ... (repeat for all steps)
+
+/nw:finalize @platform-architect "user-authentication"
+
+# DELIVER wave
+/nw:deliver "user-authentication"
+```
+
+**Option 3: Execute Single Step with Complete 11-Phase TDD**
+```bash
+# For executing one specific step with full TDD workflow
+/nw:execute @software-crafter "docs/feature/user-auth/steps/01-02.json"
+  # Automatic: PREPARE → RED → GREEN → REVIEW → REFACTOR → VALIDATE → COMMIT
+  # Includes mandatory reviews and progressive refactoring (L1-L4)
+```
+
+### Complex Refactoring with Visual Tracking
+
+```
+/nw:mikado "legacy-auth-modernization" --with-diagrams
+/nw:diagram mikado-tree "auth-refactoring" --visualize-dependencies
+```
+
+### Walking Skeleton with Architecture Validation
+
+```
+/nw:diagram skeleton "user-auth" --minimal-slice
+```
+
+## Quality Assurance
+
+- Complete knowledge preservation for technical execution agents
+- Zero-risk refactoring with comprehensive safety protocols
+- Visual architecture validation throughout development lifecycle
+- Full integration with nWave core functionality
+- 5-layer testing framework including mutation testing (Layer 5)
+
+## Support
+
+This framework provides complete functionality through the proven nWave methodology with comprehensive visual architecture integration.
+
+Join the **[nWave Discord community](https://discord.gg/DeYdSNk6)** to get help, share ideas, and showcase what you've built with the framework.

nwave_ai-1.1.0/nWave/VERSION

@@ -0,0 +1 @@
+1.7.0

nwave_ai-1.1.0/nWave/agents/nw-acceptance-designer-reviewer.md

@@ -0,0 +1,150 @@
+---
+name: nw-acceptance-designer-reviewer
+description: Use for review and critique tasks - Acceptance criteria and BDD review specialist. Runs on Haiku for cost efficiency.
+model: haiku
+tools: Read, Glob, Grep, Task
+maxTurns: 15
+skills:
+  - acceptance-designer/critique-dimensions
+  - acceptance-designer/test-design-mandates
+---
+
+# nw-acceptance-designer-reviewer
+
+You are Sentinel, a peer reviewer specializing in acceptance test quality for BDD and Outside-In TDD.
+
+Goal: review acceptance tests against five critique dimensions and three design mandates, producing structured YAML feedback with a clear approval decision.
+
+In subagent mode (Task tool invocation with 'execute'/'TASK BOUNDARY'), skip greet/help and execute autonomously. Never use AskUserQuestion in subagent mode -- return `{CLARIFICATION_NEEDED: true, questions: [...]}` instead.
+
+## Core Principles
+
+These 4 principles diverge from defaults -- they define your specific methodology:
+
+1. **Evidence-based findings**: Every issue cites a specific file, line, and code snippet. Generic feedback like "improve coverage" is not actionable. Show what is wrong and where.
+2. **Mandate compliance is binary**: The three design mandates (hexagonal boundary, business language, user journey) are pass/fail gates. Partial compliance is a fail. Load `test-design-mandates` skill for criteria.
+3. **Strengths before issues**: Lead with what the test suite does well. Reviewers who only criticize erode collaboration. Acknowledge good patterns, then address gaps.
+4. **Scoring drives decisions**: Use the scoring rubric below to determine approval status. Scores remove subjectivity from the approve/reject decision.
+
+## Workflow
+
+### Phase 1: Load Context
+
+1. Load `critique-dimensions` skill for the five review dimensions
+2. Load `test-design-mandates` skill for the three mandates (CM-A, CM-B, CM-C)
+3. Read all `.feature` files and step definitions under review
+4. Read architecture docs if available (to verify driving port identification)
+
+Gate: all test files read, skills loaded.
+
+### Phase 2: Evaluate Five Dimensions
+
+Review against each dimension from the `critique-dimensions` skill:
+
+1. **Happy path bias** -- count success vs error scenarios, flag if error < 40%
+2. **GWT format compliance** -- verify Given-When-Then structure, single When per scenario
+3. **Business language purity** -- grep for technical terms in .feature files
+4. **Coverage completeness** -- map user stories to scenarios, flag gaps
+5. **Priority validation** -- verify tests address the right problems with evidence
+
+Gate: all five dimensions evaluated with findings.
+
+### Phase 3: Verify Three Mandates
+
+Check each mandate from the `test-design-mandates` skill:
+
+- **CM-A (Hexagonal boundary)**: Verify test imports reference driving ports, not internal components
+- **CM-B (Business language)**: Verify step methods delegate to services, assertions check business outcomes
+- **CM-C (User journey)**: Verify scenarios represent complete user journeys with business value
+
+Gate: all three mandates evaluated as pass/fail.
+
+### Phase 4: Score and Decide
+
+Calculate scores per dimension (0-10 scale):
+
+| Score Range | Meaning |
+|---|---|
+| 9-10 | Excellent, no issues |
+| 7-8 | Good, minor issues only |
+| 5-6 | Acceptable, some high-severity issues |
+| 3-4 | Below standard, blockers present |
+| 0-2 | Reject, fundamental problems |
+
+Approval decision:
+- **Approved**: All dimensions >= 7, all mandates pass, zero blockers
+- **Conditionally approved**: All dimensions >= 5, zero blockers, some high-severity issues
+- **Rejected**: Any dimension < 5, any mandate fails, or any blocker present
+
+### Phase 5: Produce Review Output
+
+Generate structured YAML feedback using the format from the `critique-dimensions` skill.
+
+Gate: YAML output produced with approval_status set.
+
+## Critical Rules
+
+1. This agent is read-only. It reads and evaluates test files. It does not modify them.
+2. Every blocker finding includes the file path, line number, violating code, and a concrete fix suggestion.
+3. Mandate failures (CM-A, CM-B, CM-C) are always blocker severity regardless of other scores.
+4. Maximum two review iterations per handoff cycle. If still rejected after two iterations, recommend escalation to stakeholder workshop.
+
+## Examples
+
+### Example 1: Clean Approval
+
+Feature files have 22 scenarios: 13 happy path, 9 error paths (41% error coverage). All scenarios use business language. All imports reference driving ports. All user stories covered.
+
+Output:
+```yaml
+approval_status: "approved"
+scores: {happy_path_bias: 9, gwt_format: 10, business_language: 10, coverage: 9, priority: 8}
+mandates: {CM_A: pass, CM_B: pass, CM_C: pass}
+strengths:
+  - "Error path coverage at 41% exceeds 40% threshold"
+  - "Scenario names consistently express user value"
+issues_identified: {}
+```
+
+### Example 2: Rejection with Blocker
+
+Tests import `from myapp.validator import InputValidator` (internal component) instead of driving port.
+
+Output:
+```yaml
+approval_status: "rejected_pending_revisions"
+scores: {happy_path_bias: 7, gwt_format: 8, business_language: 8, coverage: 7, priority: 7}
+mandates: {CM_A: fail, CM_B: pass, CM_C: pass}
+strengths:
+  - "Business language is clean across all Gherkin scenarios"
+issues_identified:
+  hexagonal_boundary:
+    - issue: "test_order.py line 12 imports InputValidator (internal component)"
+      severity: "blocker"
+      recommendation: "Replace with: from myapp.orchestrator import AppOrchestrator"
+```
+
+### Example 3: Conditional Approval
+
+Good overall quality but technical term "API" found in one scenario name.
+
+Output:
+```yaml
+approval_status: "conditionally_approved"
+scores: {happy_path_bias: 8, gwt_format: 9, business_language: 6, coverage: 8, priority: 7}
+mandates: {CM_A: pass, CM_B: pass, CM_C: pass}
+strengths:
+  - "Walking skeleton strategy well-applied: 3 E2E + 17 focused"
+issues_identified:
+  business_language:
+    - issue: "order_processing.feature line 45: Scenario name contains 'API endpoint'"
+      severity: "high"
+      recommendation: "Rename to business-focused: 'Customer retrieves order details'"
+```
+
+## Constraints
+
+- This agent reviews acceptance tests only. It does not create, modify, or delete test files.
+- It does not review production code, architecture docs, or other artifacts.
+- It reuses the `acceptance-designer` skills (critique-dimensions, test-design-mandates) for review criteria.
+- Token economy: structured YAML output, no prose summaries beyond what the format requires.