# Specification: 4-Tier MMA Architecture Formalization

## Overview
This track aims to formalize and automate the 4-Tier Hierarchical Multi-Model Architecture (MMA) within the Conductor framework. It introduces specialized skills for each tier and a new specialized CLI tool (`mma-exec`) to handle role-specific context gathering and "Context Amnesia" protocols.

## Goals
- Isolate cognitive load for sub-agents by providing only domain-specific context.
- Minimize token burn through "Context Amnesia" and AST-based skeleton views.
- Formalize the Orchestrator (Tier 1), Tech Lead (Tier 2), Worker (Tier 3), and QA (Tier 4) roles.

## Functional Requirements

### 1. Specialized Tier Skills
Create four new Gemini CLI skills located in `.gemini/skills/`:
- **mma-tier1-orchestrator:** Focused on product alignment, high-level planning, and track management.
- **mma-tier2-tech-lead:** Focused on architectural design, tech stack alignment, and code review.
- **mma-tier3-worker:** Focused on TDD implementation, surgical code changes, and following specific specs.
- **mma-tier4-qa:** Focused on test analysis, error summarization, and bug reproduction.

### 2. Specialized CLI: `mma-exec`
A new Python-based CLI tool to replace/extend `run_subagent.ps1`:
- **Role Scoping:** Automatically determines which project documents (Product, Tech Stack, etc.) to include based on the active role.
- **AST Skeleton Views:** Integrates with `tree-sitter` to generate and provide only the interface/signature skeletons of dependency files to Tier 3 Workers.
- **Context Amnesia Protocol:** Ensures each role execution starts with a fresh, scoped context to prevent history-induced hallucinations.
- **Conductor Integration:** Designed to be called by the Conductor agent or manually by the developer.

### 3. Workflow Integration
- Update `conductor/workflow.md` to formalize the use of `mma-exec` and the tiered skills.
- Add specific commands/aliases within the Conductor context to trigger role hand-offs.

## Non-Functional Requirements
- **Performance:** Context gathering (including AST parsing) must be fast enough for interactive use.
- **Transparency:** All hand-offs and context inclusions must be logged for developer auditing.

## Acceptance Criteria
- [ ] Four new skills are registered and accessible.
- [ ] `mma-exec` tool can successfully spawn a worker with only AST skeleton views of requested dependencies.
- [ ] A test task can be implemented using the tiered delegation flow without manual context curation.
- [ ] `workflow.md` documentation is fully updated.

## Out of Scope
- Migrating existing tracks to the new architecture (only new tasks/tracks are required to use it).
- Automating the *decision* of when to hand off (remains semi-automated/manual per user preference).
