chati-dev 2.0.4 → 2.0.6

package/framework/i18n/es.yaml

@@ -10,15 +10,13 @@ installer:
   brownfield: "Brownfield (integracion con proyecto existente)"
   detected_brownfield: "Detectado package.json y src/ en el directorio actual"
   suggestion_brownfield: "Sugerencia: Brownfield"
-  select_ides: "Seleccione IDE(s) para configuracion de Chati.dev:"
-  select_mcps: "Seleccione MCPs para instalar (nivel de proyecto):"
   confirmation_title: "Resumen de Instalacion"
   project_label: "Proyecto"
   language_label: "Idioma"
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Se instalara:"
-  agents_count: "13 definiciones de agentes (fases CLARITY, BUILD, DEPLOY)"
+  agents_count: "13 definiciones de agentes (fases PLANNING, BUILD, DEPLOY)"
   workflows_count: "5 blueprints de workflow"
   templates_count: "5 templates (PRD, PRD Brownfield, Arquitectura, Task, QA Gate)"
   constitution: "Constitucion (17 Articulos + Preambulo)"

package/framework/i18n/fr.yaml

@@ -10,15 +10,13 @@ installer:
   brownfield: "Brownfield (integration avec un projet existant)"
   detected_brownfield: "Detecte package.json et src/ dans le repertoire actuel"
   suggestion_brownfield: "Suggestion: Brownfield"
-  select_ides: "Selectionnez IDE(s) pour la configuration de Chati.dev:"
-  select_mcps: "Selectionnez les MCPs a installer (niveau projet):"
   confirmation_title: "Resume de l'Installation"
   project_label: "Projet"
   language_label: "Langue"
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Sera installe:"
-  agents_count: "13 definitions d'agents (phases CLARITY, BUILD, DEPLOY)"
+  agents_count: "13 definitions d'agents (phases PLANNING, BUILD, DEPLOY)"
   workflows_count: "5 blueprints de workflow"
   templates_count: "5 templates (PRD, PRD Brownfield, Architecture, Task, QA Gate)"
   constitution: "Constitution (17 Articles + Preambule)"

package/framework/i18n/pt.yaml

@@ -10,15 +10,13 @@ installer:
   brownfield: "Brownfield (integracao com projeto existente)"
   detected_brownfield: "Detectado package.json e src/ no diretorio atual"
   suggestion_brownfield: "Sugestao: Brownfield"
-  select_ides: "Selecione IDE(s) para configuracao do Chati.dev:"
-  select_mcps: "Selecione MCPs para instalar (nivel de projeto):"
   confirmation_title: "Resumo da Instalacao"
   project_label: "Projeto"
   language_label: "Idioma"
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Sera instalado:"
-  agents_count: "13 definicoes de agentes (fases CLARITY, BUILD, DEPLOY)"
+  agents_count: "13 definicoes de agentes (fases PLANNING, BUILD, DEPLOY)"
   workflows_count: "5 blueprints de workflow"
   templates_count: "5 templates (PRD, PRD Brownfield, Arquitetura, Task, QA Gate)"
   constitution: "Constituicao (17 Artigos + Preambulo)"

package/framework/intelligence/context-engine.md

@@ -26,7 +26,7 @@ The orchestrator injects context through 5 hierarchical layers:
 | Layer | Name | Source | When Active |
 |-------|------|--------|-------------|
 | **L0** | Constitution | `chati.dev/constitution.md` (Articles I-XVI) | ALWAYS (non-negotiable) |
-| **L1** | Mode + Global | `config.yaml` + mode governance (clarity/build/deploy) | ALWAYS |
+| **L1** | Mode + Global | `config.yaml` + mode governance (planning/build/deploy) | ALWAYS |
 | **L2** | Agent Scope | `chati.dev/agents/{agent}/` — mission, inputs, outputs, criteria | When agent is active |
 | **L3** | Pipeline State | `.chati/session.yaml` — pipeline position, scores, backlog | When session is active |
 | **L4** | Task Context | Active artifact + previous agent's handoff | When task is active |
@@ -53,11 +53,11 @@ The orchestrator produces a structured XML block injected into agent prompts:
     Key: Self-validation required. Loop until quality threshold.
     Guided options (1,2,3). Persistent session state.
     Two-layer handoff. Language protocol. Deviation protocol.
-    Mode governance (clarity/build/deploy).
+    Mode governance (planning/build/deploy).
     Context brackets. Memory governance. Registry governance.
   </constitution>
 
-  <mode>clarity</mode>
+  <mode>planning</mode>
 
   <agent name="brief" mission="Extract user requirements in 5 structured phases">
     <inputs>WU artifact, user access</inputs>

package/framework/orchestrator/chati.md

@@ -96,7 +96,7 @@ If not already set in session.yaml:
 project:
   name: "{detected or asked}"
   type: greenfield | brownfield
-  state: clarity
+  state: planning
 execution_mode: interactive
 current_agent: greenfield-wu | brownfield-wu
 language: "{detected}"
@@ -106,8 +106,8 @@ user_level_confidence: 0.0
 
 #### 3d. Route to First Agent
 ```
-If greenfield -> Read chati.dev/agents/clarity/greenfield-wu.md -> Activate
-If brownfield -> Read chati.dev/agents/clarity/brownfield-wu.md -> Activate
+If greenfield -> Read chati.dev/agents/planning/greenfield-wu.md -> Activate
+If brownfield -> Read chati.dev/agents/planning/brownfield-wu.md -> Activate
 ```
 
 ### Step 5: Session Resume
@@ -144,71 +144,151 @@ brownfield-wu -> Brief -> Architect -> Detail -> UX -> Phases -> Tasks -> QA-Pla
 ### Agent Location Map
 | Agent | File |
 |-------|------|
-| greenfield-wu | chati.dev/agents/clarity/greenfield-wu.md |
-| brownfield-wu | chati.dev/agents/clarity/brownfield-wu.md |
-| brief | chati.dev/agents/clarity/brief.md |
-| detail | chati.dev/agents/clarity/detail.md |
-| architect | chati.dev/agents/clarity/architect.md |
-| ux | chati.dev/agents/clarity/ux.md |
-| phases | chati.dev/agents/clarity/phases.md |
-| tasks | chati.dev/agents/clarity/tasks.md |
+| greenfield-wu | chati.dev/agents/planning/greenfield-wu.md |
+| brownfield-wu | chati.dev/agents/planning/brownfield-wu.md |
+| brief | chati.dev/agents/planning/brief.md |
+| detail | chati.dev/agents/planning/detail.md |
+| architect | chati.dev/agents/planning/architect.md |
+| ux | chati.dev/agents/planning/ux.md |
+| phases | chati.dev/agents/planning/phases.md |
+| tasks | chati.dev/agents/planning/tasks.md |
 | qa-planning | chati.dev/agents/quality/qa-planning.md |
 | dev | chati.dev/agents/build/dev.md |
 | qa-implementation | chati.dev/agents/quality/qa-implementation.md |
 | devops | chati.dev/agents/deploy/devops.md |
 
 ### Transition Logic
+
 ```
 When an agent completes (score >= 95%):
   1. Agent generates handoff at chati.dev/artifacts/handoffs/{agent-name}-handoff.md
   2. Agent updates session.yaml (status: completed, score, completed_at)
   3. Agent updates CLAUDE.md with current state
   4. Orchestrator identifies next agent from pipeline
+  5. Update session.yaml: current_agent = next_agent
+  6. Update project.state if crossing macro-phase boundary:
+     - WU through QA-Planning = planning
+     - Dev + QA-Implementation = build
+     - Final validation = validate
+     - DevOps = deploy
+  7. Activate agent using Hybrid Activation Protocol (see below)
+```
+
+---
+
+## Hybrid Activation Protocol
+
+The orchestrator uses TWO activation modes depending on the agent type:
+
+### Interactive Agents (run IN-CONVERSATION)
+
+These agents require human interaction and run in the same terminal as the orchestrator:
+- **greenfield-wu** — needs user description of the project
+- **brownfield-wu** — needs user guidance on codebase
+- **brief** — needs iterative requirement extraction with user
+
+For interactive agents:
+```
+1. Read the agent's .md file from the Agent Location Map
+2. Display model recommendation (see Model Map below)
+3. Load agent context into the conversation
+4. User interacts with the agent directly
+5. Agent completes, generates handoff, orchestrator continues
+```
+
+### Autonomous Agents (run in SEPARATE TERMINALS)
+
+All other agents run in separate Claude Code processes with the correct model:
+- **detail**, **architect**, **ux**, **phases**, **tasks**
+- **qa-planning**, **dev**, **qa-implementation**, **devops**
+
+For autonomous agents:
+```
+1. Use the Bash tool to spawn the agent in a separate terminal:
+
+   node packages/chati-dev/src/terminal/run-agent.js \
+     --agent {agent_name} \
+     --task-id {primary_task_id} \
+     --project-dir {absolute_project_path} \
+     --previous-agent {previous_agent_name} \
+     --timeout 600000
+
+2. Wait for the JSON output
+
+3. Parse the result:
+   - If "status": "complete" → Save handoff, continue to next agent
+   - If "status": "needs_input" → Read "needs_input_question", ask the user,
+     then re-run with --additional-context "{user_response}"
+   - If "status": "error" → Apply Recovery Protocol (retry up to 2 times)
+   - If retries exhausted → Fall back to in-conversation activation
+
+4. Update session.yaml with completion data
+```
+
+### Parallel Group Execution
 
   ╔══════════════════════════════════════════════════════════════╗
-  ║ 4.5. PARALLELIZATION CHECK (MANDATORY — DO NOT SKIP)       ║
-  ║                                                             ║
-  ║ Before activating next agent, check parallel eligibility:   ║
+  ║ PARALLELIZATION CHECK (MANDATORY — DO NOT SKIP)             ║
   ║                                                             ║
-  ║ GROUP 1 — Clarity Phase (after Brief completes):            ║
+  ║ GROUP 1 — Planning Phase (after Brief completes):           ║
   ║   Agents: [detail, architect, ux]                           ║
-  ║   AUTONOMOUS: Spawn all 3 simultaneously (default)          ║
-  ║   HUMAN-IN-THE-LOOP: Offer parallel option (recommended)    ║
-  ║   Write scopes:                                             ║
-  ║     detail → chati.dev/artifacts/2-PRD/                     ║
-  ║     architect → chati.dev/artifacts/3-Architecture/         ║
-  ║     ux → chati.dev/artifacts/4-UX/                          ║
-  ║   → Merge ALL handoffs before proceeding to Phases          ║
+  ║   ALL run in parallel via separate terminals                ║
   ║                                                             ║
   ║ GROUP 2 — Build Phase (Dev agent tasks):                    ║
-  ║   ALL MODES: Independent tasks ALWAYS run in parallel       ║
-  ║   → Analyze task dependency graph from tasks.md             ║
-  ║   → Tasks with no shared file deps = parallel               ║
-  ║   → Tasks with deps = sequential within their chain         ║
-  ║   → Each terminal gets isolated write scope per task        ║
-  ║   → Merge results after each parallel batch                 ║
-  ║                                                             ║
-  ║ If next agent is NOT in a parallel group:                   ║
-  ║   → Continue with sequential activation (step 5)            ║
+  ║   Independent tasks ALWAYS run in parallel                  ║
+  ║   Tasks with dependencies = sequential within chain         ║
   ╚══════════════════════════════════════════════════════════════╝
 
-  5. Update session.yaml: current_agent = next_agent
-  6. Update project.state if crossing macro-phase boundary:
-     - WU through QA-Planning = clarity
-     - Dev + QA-Implementation = build
-     - Final validation = validate
-     - DevOps = deploy
-  7. Read next agent's command file -> Extract Model field from Identity section
-  8. Evaluate upgrade conditions against session context
-  9. Display model recommendation (see Model Selection Protocol below)
-  10. Activate agent
+When the next agent is part of a parallel group, use:
+
+```
+node packages/chati-dev/src/terminal/run-parallel.js \
+  --agents detail,architect,ux \
+  --task-ids {task_id_detail},{task_id_architect},{task_id_ux} \
+  --project-dir {absolute_project_path} \
+  --previous-agent brief \
+  --timeout 900000
+```
+
+Parse the consolidated JSON output:
+- If all agents completed → merged handoff ready, continue to next sequential agent
+- If partial failure → present failed agents to user with options:
+  1. Retry failed agents only
+  2. Continue with partial results
+  3. Fall back to sequential execution for failed agents
+
+### Sequential Fallback
+
+If terminal spawning fails (claude CLI not found, system error, etc.):
+```
+1. Log the failure
+2. Fall back to in-conversation activation (read agent .md file, become agent)
+3. Record in session.yaml:
+   terminal_fallback:
+     agent: {name}
+     reason: "{error_message}"
+     timestamp: "{now}"
+4. Continue pipeline normally
+```
+
+### Needs-Input Relay Pattern
+
+When a spawned agent needs user input:
+```
+1. Agent returns status: "needs_input" in JSON output
+2. Agent includes question in "needs_input_question" field
+3. Orchestrator reads the question
+4. Orchestrator presents question to user (in their language)
+5. User responds
+6. Orchestrator re-spawns agent with --additional-context "{user_response}"
+7. Repeat until agent completes or max 3 relay cycles
 ```
 
 ---
 
 ## Model Selection Protocol
 
-Before activating any agent, the orchestrator reads the agent's `Model` field and recommends the optimal model.
+Model selection is **enforced by construction**: the orchestrator passes `--model` to the spawned terminal. For interactive agents, the model is recommended to the user.
 
 ### Model Map (Quick Reference)
 
@@ -227,30 +307,19 @@ Before activating any agent, the orchestrator reads the agent's `Model` field an
 | qa-implementation | opus | no downgrade |
 | devops | sonnet | opus if multi-environment or IaC |
 
-### Evaluation Logic
-
-```
-1. Read agent's Model field from its .md file
-2. Extract default model and upgrade condition
-3. If upgrade condition exists:
-   a. Check session context (project.type, codebase_size, integrations_count, requirements_count)
-   b. Check previous agent signals (handoff complexity, discovered tech debt)
-   c. If condition matches -> recommend upgraded model
-   d. If condition does not match -> use default model
-4. If "no downgrade" -> always use the specified model
-```
-
-### Recommendation Message (IDE Mode)
-
-When the recommended model differs from the current model, display:
+### Enforcement
 
 ```
-💡 Model recommendation for {agent_name}: {recommended_model}
-   Reason: {justification}
-   Current: {current_model}
+For autonomous agents (spawned terminals):
+  → Model is AUTOMATICALLY selected and passed via --model flag
+  → No user intervention needed
+  → Correct model guaranteed by the prompt builder
 
-   To switch: /model {recommended_model}
-   Or continue with current model.
+For interactive agents (in-conversation):
+  → Display model recommendation to user:
+    💡 Model recommendation for {agent_name}: {recommended_model}
+       To switch: /model {recommended_model}
+  → Model governance hook provides defense-in-depth validation
 ```
 
 ### Session Logging
@@ -258,10 +327,11 @@ When the recommended model differs from the current model, display:
 ```yaml
 # Appended to session.yaml on each agent activation
 model_selections:
-  - agent: brief
-    recommended: sonnet
-    actual: opus          # What the user actually used
-    reason: "default"
+  - agent: detail
+    recommended: opus
+    actual: opus
+    mode: terminal          # terminal | in-conversation
+    reason: "no downgrade"
     timestamp: "2026-..."
 ```
 
@@ -274,7 +344,7 @@ model_selections:
 Before any agent writes a file, the orchestrator validates the operation against the current mode:
 
 ```
-If project.state == "clarity":
+If project.state == "planning":
   ALLOW write to: chati.dev/**, .chati/**
   BLOCK write to: everything else
   ALLOW read: everything (essential for brownfield-wu codebase analysis)
@@ -294,13 +364,13 @@ If project.state == "deploy":
 Mode transitions are AUTOMATIC based on quality gate results. The orchestrator executes the transition when the trigger condition is met.
 
 ```
-clarity -> build:
+planning -> build:
   TRIGGER: qa-planning agent completes with score >= 95%
   ACTION:
     1. Update project.state = "build"
     2. Log transition in session.yaml mode_transitions:
        - timestamp: "{now}"
-         from: clarity
+         from: planning
          to: build
          trigger: "qa-planning completed with score {score}%"
          type: automatic
@@ -333,12 +403,12 @@ deploy -> completed:
 ### Backward Transitions
 
 ```
-build/validate -> clarity:
+build/validate -> planning:
   TRIGGER: qa-implementation classifies issue as:
     - issue_type: "spec" (requirement gap, ambiguity, conflict)
     - issue_type: "architecture" (design flaw, missing component)
   ACTION:
-    1. Update project.state = "clarity"
+    1. Update project.state = "planning"
     2. Log backward transition in mode_transitions:
        - type: backward
          reason: "{QA finding description}"
@@ -362,8 +432,8 @@ When user requests to skip phases (e.g., "I need to code this NOW"):
 ```
 1. Orchestrator detects intent to change mode
 2. Inform user of current state and what will be skipped:
-   "You're in CLARITY mode. Skipping to BUILD will bypass:
-    - {list of pending CLARITY agents}
+   "You're in PLANNING mode. Skipping to BUILD will bypass:
+    - {list of pending PLANNING agents}
     Artifacts from these agents will not be generated."
 3. Request explicit confirmation
 4. If confirmed:
@@ -375,7 +445,7 @@ When user requests to skip phases (e.g., "I need to code this NOW"):
    - Mark skipped agents as "skipped" in session.yaml (not "completed")
    - Continue with target agent
 5. After override session completes, suggest:
-   "You skipped CLARITY phases. Want to go back and complete planning?"
+   "You skipped PLANNING phases. Want to go back and complete planning?"
 ```
 
 ---
@@ -480,7 +550,7 @@ Display project status dashboard:
   Phase: {state}           Mode: {execution_mode}
   Language: {language}     IDE: {ides}
 
-  CLARITY:
+  PLANNING:
     WU: {score}  Brief: {score}  Detail: {score}  Arch: {score}
     UX: {score}  Phases: {score}  Tasks: {score}  QA-P: {score}
 
@@ -686,7 +756,7 @@ If agent fails repeatedly:
 ### Exclusive (only the orchestrator can do this)
 - Route user messages to agents
 - Activate/deactivate agents
-- Execute mode transitions (clarity -> build -> validate -> deploy)
+- Execute mode transitions (planning -> build -> validate -> deploy)
 - Manage session lock (activate/deactivate)
 - Handle deviations and re-routing
 - Manage backlog items
@@ -868,7 +938,7 @@ Level 4 - Graceful Degradation:
 1. **Single Entry Point**: The orchestrator is the ONLY way users interact with Chati.dev. No agent is directly accessible.
 2. **Transparent Routing**: Users should understand which agent is active and why, but never need to manage agents directly.
 3. **State Preservation**: Every state change is logged in session.yaml. No action is lossy.
-4. **Fail-Safe Defaults**: When uncertain, default to the most restrictive mode (clarity) and the safest agent.
+4. **Fail-Safe Defaults**: When uncertain, default to the most restrictive mode (planning) and the safest agent.
 5. **Progressive Disclosure**: Show complexity only when the user needs it. Start simple, reveal depth on demand.
 6. **Pipeline Respect**: Never skip pipeline steps without explicit user consent and documented risk.
 7. **Language Fidelity**: Interaction always in user's language. Artifacts always in English. No exceptions.

package/framework/quality-gates/planning-gate.md

@@ -1,7 +1,7 @@
 # Planning Quality Gate
 
 ## Purpose
-Validates traceability and consistency across all CLARITY artifacts before allowing transition to BUILD phase.
+Validates traceability and consistency across all PLANNING artifacts before allowing transition to BUILD phase.
 
 ## When
 After Tasks agent completes, before Dev agent starts.

package/framework/schemas/context.schema.json

@@ -14,7 +14,7 @@
       "description": "Summarized constitution content (always injected, L0 layer)"
     },
     "mode": {
-      "enum": ["clarity", "build", "deploy"],
+      "enum": ["planning", "build", "deploy"],
       "description": "Current execution mode from session state (L1 layer)"
     },
     "agent": {

package/framework/schemas/session.schema.json

@@ -11,7 +11,7 @@
       "properties": {
         "name": { "type": "string", "description": "Project name" },
         "type": { "enum": ["greenfield", "brownfield"], "description": "Project type" },
-        "state": { "enum": ["clarity", "build", "validate", "deploy", "completed"], "description": "Current pipeline macro-phase" }
+        "state": { "enum": ["planning", "build", "validate", "deploy", "completed"], "description": "Current pipeline macro-phase" }
       }
     },
     "execution_mode": {
@@ -122,8 +122,8 @@
         "required": ["timestamp", "from", "to", "trigger"],
         "properties": {
           "timestamp": { "type": "string", "format": "date-time" },
-          "from": { "enum": ["clarity", "build", "validate", "deploy", "completed"] },
-          "to": { "enum": ["clarity", "build", "validate", "deploy", "completed"] },
+          "from": { "enum": ["planning", "build", "validate", "deploy", "completed"] },
+          "to": { "enum": ["planning", "build", "validate", "deploy", "completed"] },
           "trigger": { "type": "string", "description": "What caused the transition (agent completion, override, backward)" },
           "type": { "enum": ["automatic", "backward", "override"], "description": "Transition classification" },
           "skipped_agents": {

package/framework/tasks/architect-api-design.md

@@ -2,7 +2,7 @@
 id: architect-api-design
 agent: architect
 trigger: architect-stack-selection
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [api-design.yaml]

package/framework/tasks/architect-consolidate.md

@@ -2,7 +2,7 @@
 id: architect-consolidate
 agent: architect
 trigger: architect-security-review
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [architecture-final.yaml]

package/framework/tasks/architect-db-design.md

@@ -2,7 +2,7 @@
 id: architect-db-design
 agent: architect
 trigger: architect-api-design
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [db-design.yaml]

package/framework/tasks/architect-design.md

@@ -2,7 +2,7 @@
 id: architect-design
 agent: architect
 trigger: detail
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: true
 outputs: [architecture.yaml]

package/framework/tasks/architect-security-review.md

@@ -2,7 +2,7 @@
 id: architect-security-review
 agent: architect
 trigger: architect-db-design
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [security-review.yaml]

package/framework/tasks/architect-stack-selection.md

@@ -2,7 +2,7 @@
 id: architect-stack-selection
 agent: architect
 trigger: architect-design
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [stack-selection.yaml]

package/framework/tasks/brief-consolidate.md

@@ -2,7 +2,7 @@
 id: brief-consolidate
 agent: brief
 trigger: brief-constraint-identify
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [brief.yaml]

package/framework/tasks/brief-constraint-identify.md

@@ -2,7 +2,7 @@
 id: brief-constraint-identify
 agent: brief
 trigger: brief-stakeholder-map
-phase: clarity
+phase: planning
 requires_input: true
 parallelizable: false
 outputs: [constraints.yaml]

package/framework/tasks/brief-extract-requirements.md

@@ -2,7 +2,7 @@
 id: brief-extract-requirements
 agent: brief
 trigger: orchestrator
-phase: clarity
+phase: planning
 requires_input: true
 parallelizable: false
 outputs: [requirements-raw.yaml]

package/framework/tasks/brief-stakeholder-map.md

@@ -2,7 +2,7 @@
 id: brief-stakeholder-map
 agent: brief
 trigger: brief-validate-completeness
-phase: clarity
+phase: planning
 requires_input: true
 parallelizable: false
 outputs: [stakeholder-map.yaml]

package/framework/tasks/brief-validate-completeness.md

@@ -2,7 +2,7 @@
 id: brief-validate-completeness
 agent: brief
 trigger: brief-extract-requirements
-phase: clarity
+phase: planning
 requires_input: true
 parallelizable: false
 outputs: [validation-report.yaml]

package/framework/tasks/brownfield-wu-architecture-map.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-architecture-map
 agent: brownfield-wu
 trigger: brownfield-wu-dependency-scan
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: true
 outputs: [architecture-map.yaml]

package/framework/tasks/brownfield-wu-deep-discovery.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-deep-discovery
 agent: brownfield-wu
 trigger: orchestrator
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [discovery.yaml]

package/framework/tasks/brownfield-wu-dependency-scan.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-dependency-scan
 agent: brownfield-wu
 trigger: brownfield-wu-deep-discovery
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: true
 outputs: [dependencies.yaml]

package/framework/tasks/brownfield-wu-migration-plan.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-migration-plan
 agent: brownfield-wu
 trigger: brownfield-wu-risk-assess
-phase: clarity
+phase: planning
 requires_input: true
 parallelizable: false
 outputs: [migration-plan.yaml]

package/framework/tasks/brownfield-wu-report.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-report
 agent: brownfield-wu
 trigger: brownfield-wu-migration-plan
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [wu-report.yaml]

package/framework/tasks/brownfield-wu-risk-assess.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-risk-assess
 agent: brownfield-wu
 trigger: brownfield-wu-architecture-map
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [risk-assessment.yaml]

package/framework/tasks/detail-acceptance-criteria.md

@@ -2,7 +2,7 @@
 id: detail-acceptance-criteria
 agent: detail
 trigger: detail-edge-case-analysis
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [acceptance-criteria.yaml]