remove mma_utilization_refinement_20260226 from tracks
This commit is contained in:
@@ -1,5 +0,0 @@
|
|||||||
# Track mma_utilization_refinement_20260226 Context
|
|
||||||
|
|
||||||
- [Specification](./spec.md)
|
|
||||||
- [Implementation Plan](./plan.md)
|
|
||||||
- [Metadata](./metadata.json)
|
|
||||||
@@ -1,8 +0,0 @@
|
|||||||
{
|
|
||||||
"track_id": "mma_utilization_refinement_20260226",
|
|
||||||
"type": "feature",
|
|
||||||
"status": "new",
|
|
||||||
"created_at": "2026-02-26T08:23:00Z",
|
|
||||||
"updated_at": "2026-02-26T08:23:00Z",
|
|
||||||
"description": "Refine MMA utilization by segregating tiers, enhancing sub-agent tooling with AST skeletons, and improving observability via dedicated logging."
|
|
||||||
}
|
|
||||||
@@ -1,26 +0,0 @@
|
|||||||
# Implementation Plan: MMA Utilization Refinement
|
|
||||||
|
|
||||||
## Phase 1: Skill Segregation and Tier Re-Alignment
|
|
||||||
- [x] Task: Refine `mma-tier1-orchestrator` skill to focus exclusively on project/track initialization. e950601
|
|
||||||
- [x] Task: Refine `mma-tier2-tech-lead` skill for track execution, ensuring persistent memory across tasks (Disable Context Amnesia). e950601
|
|
||||||
- [x] Task: Refine `mma-tier3-worker` and `mma-tier4-qa` skills to be stateless but equipped with full file read/write tools and should be provided only the context the need of the project beyond that with ast skeleton extraction or what tier 2 provies them. e950601
|
|
||||||
- [ ] Task: Conductor - User Manual Verification 'Phase 1' (Protocol in workflow.md)
|
|
||||||
|
|
||||||
## Phase 2: AST Skeleton Extraction (Skeleton Views)
|
|
||||||
- [x] Task: Enhance `mcp_client.py` with `get_python_skeleton` functionality using `tree-sitter` to extract signatures and docstrings. e950601
|
|
||||||
- [x] Task: Update `mma_exec.py` to utilize these skeletons for non-target dependencies when preparing context for Tier 3. e950601
|
|
||||||
- [x] Task: Integrate "Interface-level" scrubbed versions into the sub-agent injection logic. e950601
|
|
||||||
- [ ] Task: Conductor - User Manual Verification 'Phase 2' (Protocol in workflow.md)
|
|
||||||
|
|
||||||
## Phase 3: Sub-Agent Observability
|
|
||||||
- [x] Task: Implement a dedicated logging mechanism for sub-agents (e.g., `logs/agents/mma_tier<#>_task_<timestamp>.log`) that captures reasoning and tool output. e950601
|
|
||||||
- [x] Task: Ensure sub-agent executions do not pollute the primary Gemini CLI history while remaining visible to the user via the log. e950601
|
|
||||||
- [ ] Task: Conductor - User Manual Verification 'Phase 3' (Protocol in workflow.md)
|
|
||||||
|
|
||||||
## Phase 4: Workflow Optimization and Validation
|
|
||||||
- [x] Task: Update `conductor/workflow.md` to formally document the refined tier roles and tool permissions. e950601
|
|
||||||
- [x] Task: Conduct a full end-to-end "Dry Run" (Create a dummy track and implement a small feature) to verify the new architecture. e950601
|
|
||||||
- [ ] Task: Conductor - User Manual Verification 'Phase 4' (Protocol in workflow.md)
|
|
||||||
|
|
||||||
## Phase: Review Fixes
|
|
||||||
- [x] Task: Apply review suggestions d343066
|
|
||||||
@@ -1,34 +0,0 @@
|
|||||||
# Specification: MMA Utilization Refinement
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
Refine the Multi-Model Architecture (MMA) implementation within the Conductor framework to ensure clear role segregation, proper tool permissions, and improved observability for sub-agents.
|
|
||||||
|
|
||||||
## Goals
|
|
||||||
- Enforce Tier 1 as the track creator and Tier 2 as the track executor.
|
|
||||||
- Restore and fix segregated skills (`mma-tier1` through `mma-tier4`).
|
|
||||||
- Provide Tier 3 & 4 with direct file I/O tools to reduce Tier 2 context bloat.
|
|
||||||
- Implement AST-based "Skeleton Views" for Tier 3 context injection.
|
|
||||||
- Create a non-polluting verbose log/feed for sub-agent operations.
|
|
||||||
- Remove "Context Amnesia" from Tier 2 while maintaining it for Tiers 3 & 4.
|
|
||||||
|
|
||||||
## Functional Requirements
|
|
||||||
1. **Skill Refinement:**
|
|
||||||
- Update `mma-tier1-orchestrator` to focus on `/conductor:setup` and `/conductor:newTrack`.
|
|
||||||
- Update `mma-tier2-tech-lead` to manage `/conductor:implement`. It must maintain persistent context for the duration of a track session (no amnesia).
|
|
||||||
- Update `mma-tier3-worker` and `mma-tier4-qa` to be stateless (Context Amnesia) but equipped with `read_file`, `write_file`, and codebase exploration tools.
|
|
||||||
2. **AST Extraction (Skeleton Views):**
|
|
||||||
- Enhance `mcp_client.py` (or a dedicated utility) to generate Python skeletons (signatures and docstrings) using `tree-sitter`.
|
|
||||||
- Update `mma_exec.py` to utilize these skeletons for modules NOT being actively worked on by Tier 3.
|
|
||||||
3. **Observability:**
|
|
||||||
- Ensure sub-agent reasoning and tool calls are logged to a dedicated log file (e.g., `logs/mma_subagents.log`) or separate shell to avoid polluting the main session history.
|
|
||||||
4. **Workflow Update:**
|
|
||||||
- Update `conductor/workflow.md` to reflect the new tier responsibilities and tool access rules.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
- [ ] Tier 1 can successfully initialize a track.
|
|
||||||
- [ ] Tier 2 can delegate a coding task to Tier 3.
|
|
||||||
- [ ] Tier 3 receives a "Skeleton View" of relevant dependencies instead of full files.
|
|
||||||
- [ ] Tier 3 can write files back to the project.
|
|
||||||
- [ ] Tier 4 can analyze logs and provide summaries.
|
|
||||||
- [ ] Sub-agent verbose output is captured in a dedicated log.
|
|
||||||
- [ ] Tier 2 context remains focused on the high-level plan, not implementation details.
|
|
||||||
Reference in New Issue
Block a user