chati-dev 2.0.5 → 2.0.7

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

@@ -2,7 +2,7 @@
 id: greenfield-wu-report
 agent: greenfield-wu
 trigger: greenfield-wu-tech-stack-assess
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [wu-report.yaml]

package/framework/tasks/greenfield-wu-scaffold-detection.md

@@ -2,7 +2,7 @@
 id: greenfield-wu-scaffold-detection
 agent: greenfield-wu
 trigger: greenfield-wu-analyze-empty
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [scaffold-report.yaml]

package/framework/tasks/greenfield-wu-tech-stack-assess.md

@@ -2,7 +2,7 @@
 id: greenfield-wu-tech-stack-assess
 agent: greenfield-wu
 trigger: greenfield-wu-scaffold-detection
-phase: clarity
+phase: planning
 requires_input: true
 parallelizable: false
 outputs: [tech-stack.yaml]

package/framework/tasks/orchestrator-deviation.md

@@ -54,8 +54,8 @@ Identify which artifacts are impacted:
 ### 4. Assess Impact Scope
 Evaluate the ripple effects:
 - **Localized**: Change affects only current/next agent
-- **Phase-wide**: Change affects current phase (e.g., all of CLARITY)
-- **Mode-wide**: Change affects entire mode (e.g., clarity → build transition)
+- **Phase-wide**: Change affects current phase (e.g., all of PLANNING)
+- **Mode-wide**: Change affects entire mode (e.g., planning → build transition)
 - **Global**: Change affects entire project plan
 
 ### 5. Determine Required Rework
@@ -172,7 +172,7 @@ deviation_plan:
     urgency: "medium"
 
   impact_assessment:
-    scope: "phase-wide"  # Affects multiple CLARITY agents
+    scope: "phase-wide"  # Affects multiple PLANNING agents
     affected_agents:
       - agent: "detail"
         status: "completed"

package/framework/tasks/orchestrator-escalate.md

@@ -190,8 +190,8 @@ escalation_report:
 
     context:
       previous_agent: "detail"
-      session_mode: "clarity"
-      pipeline_position: "CLARITY/architect"
+      session_mode: "planning"
+      pipeline_position: "PLANNING/architect"
 
   root_cause_analysis:
     primary_cause: "dependency-missing"

package/framework/tasks/orchestrator-handoff.md

@@ -77,14 +77,14 @@ Modify `.chati/session.yaml`:
 
 ### 7. Determine Next Agent
 Based on pipeline position and mode:
-- **CLARITY**: Follow sequence (wu → brief → detail → architect → ux → phases → tasks → qa-planning)
+- **PLANNING**: Follow sequence (wu → brief → detail → architect → ux → phases → tasks → qa-planning)
 - **BUILD**: dev → qa-implementation
 - **DEPLOY**: devops
 - Handle special transitions (e.g., qa-planning → dev requires mode switch)
 
 ### 8. Check Quality Gates
 Evaluate if mode transition should occur:
-- **After QA-Planning**: If score >= 95%, eligible for clarity → build
+- **After QA-Planning**: If score >= 95%, eligible for planning → build
 - **After Dev**: If complete, eligible for build → validate
 - **After QA-Implementation**: If approved, eligible for validate → deploy
 
@@ -170,8 +170,8 @@ handoff_document:
     status: "completed"
     quality_score: 8.5
     duration_minutes: 45
-    mode: "clarity"
-    phase: "CLARITY"
+    mode: "planning"
+    phase: "PLANNING"
 
   summary: |
     Completed detailed requirements analysis for HealthCare Portal.
@@ -228,14 +228,14 @@ handoff_document:
 
   session_update:
     agent_status: "completed"
-    pipeline_progress: 37.5  # 3 of 8 CLARITY agents done
+    pipeline_progress: 37.5  # 3 of 8 PLANNING agents done
     mode_transition_check:
       eligible: false
       reason: "QA-Planning not yet complete"
 
   routing_decision:
     next_action: "route-to-architect"
-    mode: "clarity"
+    mode: "planning"
     context_package:
       - ".chati/artifacts/handoffs/2026-02-13-detail.md"
       - ".chati/artifacts/handoffs/2026-02-12-brief.md"

package/framework/tasks/orchestrator-health.md

@@ -282,7 +282,7 @@ health_report:
     status: "healthy"
     articles_present: 11
     article_xi_valid: true
-    mode_definitions: ["clarity", "build", "deploy"]
+    mode_definitions: ["planning", "build", "deploy"]
     transition_rules_defined: true
     quality_gates_specified: true
 

package/framework/tasks/orchestrator-mode-switch.md

@@ -18,7 +18,7 @@ criteria:
 # Orchestrator Mode Switch Task
 
 ## Purpose
-Execute transitions between modes (clarity, build, deploy) while enforcing Article XI governance rules and validating quality gates.
+Execute transitions between modes (planning, build, deploy) while enforcing Article XI governance rules and validating quality gates.
 
 ## Prerequisites
 - Session state at `.chati/session.yaml`
@@ -33,28 +33,28 @@ Identify the transition request:
 - **Autonomous**: Quality gate met, auto-transition enabled
 - **Suggested**: Conditions met, awaiting user confirmation
 - **Manual**: User explicitly requests mode change
-- **Backward**: QA-Implementation found spec issues, reverting to clarity
+- **Backward**: QA-Implementation found spec issues, reverting to planning
 
 ### 2. Load Current Mode State
 Read session to understand current position:
-- Current mode (clarity/build/deploy)
+- Current mode (planning/build/deploy)
 - Last completed agent in current mode
 - Quality scores
 - Mode transition history
 
 ### 3. Validate Transition Direction
 Check if transition is valid per Article XI:
-- **Forward transitions**: clarity → build, build → validate, validate → deploy
-- **Backward transitions**: build/validate → clarity (on spec issues)
-- **Invalid**: deploy → build, build → clarity (except on QA failure)
+- **Forward transitions**: planning → build, build → validate, validate → deploy
+- **Backward transitions**: build/validate → planning (on spec issues)
+- **Invalid**: deploy → build, build → planning (except on QA failure)
 
 ### 4. Check Transition Preconditions
 Verify mode-specific requirements are met:
 
-**For clarity → build**:
+**For planning → build**:
 - QA-Planning agent completed
 - QA-Planning score >= 95%
-- All CLARITY agents complete or skipped
+- All PLANNING agents complete or skipped
 - No blocking issues
 
 **For build → validate**:
@@ -67,7 +67,7 @@ Verify mode-specific requirements are met:
 - QA-Implementation approved (score >= 8.0)
 - No deployment blockers
 
-**For backward to clarity**:
+**For backward to planning**:
 - QA-Implementation found spec/architecture issues
 - Issues documented in handoff
 - User confirmation obtained (if manual)
@@ -101,7 +101,7 @@ If transition approved:
 
 ### 9. Apply Mode Scope Restrictions
 Enforce Article XI scope rules for new mode:
-- **clarity**: Read all, write only to `chati.dev/` directory
+- **planning**: Read all, write only to `chati.dev/` directory
 - **build**: Full filesystem access
 - **deploy**: Full access + infrastructure operations
 
@@ -109,7 +109,7 @@ Enforce Article XI scope rules for new mode:
 Route to first agent of new mode:
 - **build mode**: Route to `dev` agent
 - **deploy mode**: Route to `devops` agent
-- **clarity mode** (backward): Route to agent that needs rework
+- **planning mode** (backward): Route to agent that needs rework
 
 ## Decision Points
 
@@ -128,14 +128,14 @@ If user wants to force transition despite low confidence:
 
 ### When Backward Transition is Needed
 If QA-Implementation finds fundamental spec problems:
-1. Identify which CLARITY agent needs to re-run
+1. Identify which PLANNING agent needs to re-run
 2. Mark affected agents as `needs_revalidation`
-3. Set mode to `clarity`
+3. Set mode to `planning`
 4. Route to earliest affected agent
 
 ### When Multiple Transitions are Eligible
 If conditions for multiple transitions are met (edge case):
-1. Follow pipeline sequence (clarity → build → deploy)
+1. Follow pipeline sequence (planning → build → deploy)
 2. Execute one transition at a time
 3. Re-evaluate after each transition
 
@@ -180,9 +180,9 @@ mode_transition:
   type: "autonomous"  # or "suggested", "manual", "backward"
 
   from_state:
-    mode: "clarity"
+    mode: "planning"
     current_agent: "qa-planning"
-    pipeline_position: "CLARITY/qa-planning"
+    pipeline_position: "PLANNING/qa-planning"
 
   to_state:
     mode: "build"
@@ -195,7 +195,7 @@ mode_transition:
     autonomous_gate: true
 
   validation:
-    transition_direction: "forward"  # clarity → build
+    transition_direction: "forward"  # planning → build
     preconditions_met: true
     quality_gate:
       required_score: 95
@@ -208,7 +208,7 @@ mode_transition:
     score: 95
     level: "high"
     factors:
-      - "All CLARITY agents completed"
+      - "All PLANNING agents completed"
       - "QA-Planning score excellent (97.5%)"
       - "Only 2 minor open questions"
       - "No blockers"
@@ -238,7 +238,7 @@ mode_transition:
     pipeline_position: "BUILD/dev"
     mode_transitions:
       - type: "autonomous-forward"
-        from: "clarity"
+        from: "planning"
         to: "build"
         timestamp: "2026-02-13T15:45:00Z"
         trigger: "qa-planning-score-97.5"
@@ -251,7 +251,7 @@ mode_transition:
     deviation_protocol: false
 
   user_notification: |
-    ✓ Mode Transition: CLARITY → BUILD
+    ✓ Mode Transition: PLANNING → BUILD
 
     QA-Planning completed with score 97.5% (>= 95% required).
     Autonomous transition to BUILD mode approved.

package/framework/tasks/orchestrator-resume.md

@@ -36,7 +36,7 @@ Check for existing session at `.chati/session.yaml`:
 ### 2. Load Session State
 Parse the YAML session file and extract:
 - Project metadata (name, type, language)
-- Current mode (clarity/build/deploy)
+- Current mode (planning/build/deploy)
 - Pipeline position (phase, last agent)
 - Agent statuses and timestamps
 - Decisions log
@@ -50,7 +50,7 @@ Find the most recent agent with `status: completed`:
 
 ### 4. Determine Next Agent
 Based on pipeline position and last completed agent:
-- **CLARITY pipeline**: greenfield-wu → brief → detail → architect → ux → phases → tasks → qa-planning
+- **PLANNING pipeline**: greenfield-wu → brief → detail → architect → ux → phases → tasks → qa-planning
 - **BUILD pipeline**: dev → qa-implementation
 - **DEPLOY pipeline**: devops
 - Handle special cases (skipped, needs_revalidation)
@@ -72,7 +72,7 @@ Rebuild the working context from session + handoff:
 
 ### 7. Check Mode Transition Conditions
 Evaluate if mode transition should occur:
-- **clarity → build**: QA-Planning score >= 95%
+- **planning → build**: QA-Planning score >= 95%
 - **build → validate**: Dev agent completed
 - **validate → deploy**: QA-Implementation approved
 - Check autonomous_gate flag
@@ -161,9 +161,9 @@ session_state:
     name: "HealthCare Portal"
     type: "brownfield"
     language: "Portugues"
-  current_mode: "clarity"
+  current_mode: "planning"
   pipeline_position:
-    phase: "CLARITY"
+    phase: "PLANNING"
     last_completed_agent: "detail"
     next_agent: "architect"
     completion_percentage: 30
@@ -183,7 +183,7 @@ session_state:
   mode_transition_check:
     eligible: false
     reason: "QA-Planning not yet complete"
-    next_gate: "clarity → build at QA-Planning >= 95%"
+    next_gate: "planning → build at QA-Planning >= 95%"
   resumption_action: "route-to-architect"
   user_message: "Welcome back! You completed Detail agent. Next: Architect will design the system architecture."
 ```

package/framework/tasks/orchestrator-route.md

@@ -35,7 +35,7 @@ Extract the core intent from user message. Identify:
 
 ### 2. Load Session Context
 Read `.chati/session.yaml` to understand:
-- Current mode (clarity/build/deploy)
+- Current mode (planning/build/deploy)
 - Last completed agent
 - Pipeline position
 - Active phase
@@ -58,7 +58,7 @@ Check if the requested action is valid for current position:
 
 ### 5. Select Target Agent
 Based on intent and position, identify the appropriate agent:
-- **CLARITY agents**: greenfield-wu, brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning
+- **PLANNING agents**: greenfield-wu, brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning
 - **BUILD agents**: dev, qa-implementation
 - **DEPLOY agents**: devops
 - **Orchestrator actions**: status, health, deviation
@@ -151,16 +151,16 @@ routing_decision:
   intent_classification: "pipeline-next"
   target_type: "agent"  # or "orchestrator-action"
   target: "detail"
-  reason: "User completed brief, detail is next in CLARITY pipeline"
-  mode: "clarity"
-  pipeline_position: "CLARITY/detail"
+  reason: "User completed brief, detail is next in PLANNING pipeline"
+  mode: "planning"
+  pipeline_position: "PLANNING/detail"
   context_package:
     previous_agent: "brief"
     handoff_file: ".chati/artifacts/handoffs/2026-02-13-brief.md"
     session_excerpt:
-      mode: "clarity"
+      mode: "planning"
       project_type: "greenfield"
-      current_phase: "CLARITY"
+      current_phase: "PLANNING"
   validation:
     mode_check: "passed"
     prerequisites_check: "passed"

package/framework/tasks/orchestrator-status.md

@@ -46,7 +46,7 @@ For each agent in the pipeline, gather:
 
 ### 3. Calculate Pipeline Progress
 Determine overall completion for each mode:
-- **CLARITY**: 9 agents (greenfield-wu OR brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning)
+- **PLANNING**: 9 agents (greenfield-wu OR brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning)
 - **BUILD**: 2 agents (dev, qa-implementation)
 - **DEPLOY**: 1 agent (devops)
 - Calculate percentage: completed / total
@@ -60,7 +60,7 @@ Determine where the user is in the pipeline:
 
 ### 5. Check Mode Transition Eligibility
 Evaluate if mode transition conditions are met:
-- **clarity → build**: QA-Planning score >= 95%
+- **planning → build**: QA-Planning score >= 95%
 - **build → validate**: Dev completed
 - **validate → deploy**: QA-Implementation approved
 - Report eligibility status
@@ -159,13 +159,13 @@ status_report:
     initialized: "2026-02-10T14:00:00Z"
 
   current_state:
-    mode: "clarity"
-    phase: "CLARITY"
+    mode: "planning"
+    phase: "PLANNING"
     last_activity: "2026-02-13T02:15:00Z"
     hours_since_activity: 8.25
 
   pipeline_progress:
-    clarity:
+    planning:
       total_agents: 8  # brownfield-wu counted, greenfield-wu skipped
       completed: 3
       percentage: 37.5
@@ -204,7 +204,7 @@ status_report:
 
   mode_transitions:
     eligible_for_next: false
-    next_transition: "clarity → build"
+    next_transition: "planning → build"
     condition: "QA-Planning score >= 95%"
     current_score: null
 
@@ -240,10 +240,10 @@ status_report:
   visual_report: |
     ╔════════════════════════════════════════════════════════════╗
     ║  chati.dev Status - HealthCare Portal                      ║
-    ║  Mode: CLARITY  |  Progress: 25% (3/12 agents)             ║
+    ║  Mode: PLANNING  |  Progress: 25% (3/12 agents)             ║
     ╚════════════════════════════════════════════════════════════╝
 
-    CLARITY Pipeline (37.5%)
+    PLANNING Pipeline (37.5%)
     ✓ brownfield-wu  ✓ brief  ✓ detail  ◐ architect  ○ ux  ○ phases  ○ tasks  ○ qa-planning
 
     BUILD Pipeline (0%)

package/framework/tasks/orchestrator-suggest-mode.md

@@ -30,7 +30,7 @@ Analyze session state to determine if mode transition conditions are met, calcul
 
 ### 1. Load Current Session State
 Read session to understand current position:
-- Current mode (clarity/build/deploy)
+- Current mode (planning/build/deploy)
 - Last completed agent
 - Agent statuses and timestamps
 - Quality scores
@@ -38,17 +38,17 @@ Read session to understand current position:
 
 ### 2. Identify Potential Transitions
 Based on current mode, check eligibility for:
-- **clarity → build**: Triggered after QA-Planning completes
+- **planning → build**: Triggered after QA-Planning completes
 - **build → validate**: Triggered after Dev completes
 - **validate → deploy**: Triggered after QA-Implementation approves
 
 ### 3. Evaluate Transition Conditions
 For each potential transition, check requirements:
 
-**For clarity → build**:
+**For planning → build**:
 - QA-Planning agent status = `completed`
 - QA-Planning score >= 95%
-- All CLARITY agents completed or skipped
+- All PLANNING agents completed or skipped
 - No blocking issues in planning phase
 
 **For build → validate**:
@@ -207,13 +207,13 @@ mode_suggestion:
   session_id: "sess-20260210-140000"
 
   current_state:
-    mode: "clarity"
-    phase: "CLARITY"
+    mode: "planning"
+    phase: "PLANNING"
     last_completed_agent: "qa-planning"
     last_activity: "2026-02-13T15:30:00Z"
 
   potential_transition:
-    from_mode: "clarity"
+    from_mode: "planning"
     to_mode: "build"
     trigger_agent: "qa-planning"
 
@@ -222,7 +222,7 @@ mode_suggestion:
     qa_planning_score: 97.5
     qa_planning_threshold: 95
     score_meets_threshold: true
-    all_clarity_agents_done: true
+    all_planning_agents_done: true
     no_blockers: true
     conditions_met: true
 
@@ -271,7 +271,7 @@ mode_suggestion:
     approved_by: "autonomous"
     rationale: |
       QA-Planning completed with excellent score (97.5% vs 95% required).
-      All CLARITY agents complete. No blockers. High confidence (95%).
+      All PLANNING agents complete. No blockers. High confidence (95%).
       Article XI allows autonomous transition. Auto-executing.
 
   execution:
@@ -282,7 +282,7 @@ mode_suggestion:
   user_notification: |
     ✓ Autonomous Mode Transition
 
-    CLARITY → BUILD
+    PLANNING → BUILD
 
     QA-Planning completed with score 97.5% (>= 95% required).
     Confidence: 95% (high)
@@ -321,14 +321,14 @@ mode_suggestion:
       3 open questions reduce confidence. Suggesting to user.
 
   user_prompt: |
-    Mode Transition Available: CLARITY → BUILD
+    Mode Transition Available: PLANNING → BUILD
 
     QA-Planning completed with score 96.5% (>= 95% required).
     Confidence: 87% (strong suggestion)
 
     Considerations:
     ✓ Quality score exceeds threshold
-    ✓ All CLARITY agents complete
+    ✓ All PLANNING agents complete
     ⚠ 3 open questions remain (non-blocking)
 
     Proceed with transition to BUILD mode? (yes/no)
@@ -358,7 +358,7 @@ mode_suggestion:
   user_notification: |
     Mode Transition: Not Ready
 
-    QA-Planning score: 92% (95% required for CLARITY → BUILD)
+    QA-Planning score: 92% (95% required for PLANNING → BUILD)
 
     To proceed:
     1. Address planning issues identified by QA-Planning

package/framework/tasks/phases-breakdown.md

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

package/framework/tasks/phases-dependency-mapping.md

@@ -2,7 +2,7 @@
 id: phases-dependency-mapping
 agent: phases
 trigger: phases-breakdown
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [dependency-map.yaml]

package/framework/tasks/phases-mvp-scoping.md

@@ -2,7 +2,7 @@
 id: phases-mvp-scoping
 agent: phases
 trigger: phases-dependency-mapping
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [mvp-scope.yaml]

package/framework/tasks/qa-impl-regression-check.md

@@ -192,7 +192,7 @@ regressions:
       severity: CRITICAL
       type: functional
       feature: Mode transition validation
-      description: "Autonomous transition from clarity to build no longer checks 95% threshold"
+      description: "Autonomous transition from planning to build no longer checks 95% threshold"
       baseline_behavior: "Transition blocked when qa-planning score < 95%"
       current_behavior: "Transition proceeds regardless of score"
       root_cause: "Removed threshold check in mode-governance.js line 87 during refactor"
@@ -348,7 +348,7 @@ smoke_tests:
   mode_transitions:
     autonomous_transition:
       status: FAIL
-      issue: "Autonomous transition from clarity to build bypassed 95% check"
+      issue: "Autonomous transition from planning to build bypassed 95% check"
       regression_id: REG-001
 
     manual_transition:

package/framework/tasks/qa-planning-consolidate.md

@@ -2,7 +2,7 @@
 id: qa-planning-consolidate
 agent: qa-planning
 trigger: qa-planning-risk-matrix
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [qa-plan.yaml]
@@ -43,7 +43,7 @@ Compile all QA planning outputs into a final qa-plan.yaml document, calculate an
    - **Execution order established** (5 points): Pre-commit, pre-push, CI, release order set
 
 3. **Calculate Quality Gates Score (25 points)**
-   - **Gates for all stages** (7 points): Pre-commit, clarity, build, validate, deploy gates defined
+   - **Gates for all stages** (7 points): Pre-commit, planning, build, validate, deploy gates defined
    - **Thresholds with pass/fail** (6 points): Clear numeric or boolean thresholds for each gate
    - **Enforcement mechanisms** (6 points): Automated, agent-enforced, manual processes specified
    - **Bypass procedures** (3 points): Deviation protocol, manual approval, exceptions documented
@@ -84,7 +84,7 @@ Compile all QA planning outputs into a final qa-plan.yaml document, calculate an
 
 9. **Cross-Validate with Constitution**
    - Verify mode governance rules are respected (autonomous transition at 95%)
-   - Ensure quality gates align with mode constraints (clarity = read all, write chati.dev/ only)
+   - Ensure quality gates align with mode constraints (planning = read all, write chati.dev/ only)
    - Check that agent handoff logic is valid (qa-planning → dev)
    - Validate autonomous_gate: true is correctly set
 

package/framework/tasks/qa-planning-coverage-plan.md

@@ -2,7 +2,7 @@
 id: qa-planning-coverage-plan
 agent: qa-planning
 trigger: qa-planning-gate-define
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [coverage-plan.yaml]

package/framework/tasks/qa-planning-gate-define.md

@@ -2,7 +2,7 @@
 id: qa-planning-gate-define
 agent: qa-planning
 trigger: qa-planning-test-strategy
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [quality-gates.yaml]
@@ -21,17 +21,17 @@ Define quality gates and enforcement thresholds for each stage of the chati.dev
 
 ## Prerequisites
 - test-strategy.yaml completed with testing approach
-- Phase plan showing pipeline stages (clarity → build → validate → deploy)
+- Phase plan showing pipeline stages (planning → build → validate → deploy)
 - Understanding of mode governance rules from constitution
 - Risk matrix inputs (will be formalized in later task)
 
 ## Steps
 
 1. **Review Pipeline Architecture**
-   - Identify all pipeline stages: clarity (8 agents), build (dev + qa-impl), validate (qa-impl verdict), deploy (devops)
+   - Identify all pipeline stages: planning (8 agents), build (dev + qa-impl), validate (qa-impl verdict), deploy (devops)
    - Map agent handoff points where quality checks occur
    - Note autonomous transition triggers (qa-planning → dev at 95%, qa-impl verdict → devops on PASS)
-   - Identify backward transition scenarios (build → clarity when spec issues found)
+   - Identify backward transition scenarios (build → planning when spec issues found)
 
 2. **Define Pre-Commit Gates**
    - **Unit Test Pass Rate**: 100% (all unit tests must pass)
@@ -41,8 +41,8 @@ Define quality gates and enforcement thresholds for each stage of the chati.dev
    - **Enforcement**: Git pre-commit hooks
    - **Bypass**: Not allowed (ensures baseline quality)
 
-3. **Define Clarity Phase Gates**
-   - **Agent Completion**: All 8 clarity agents must complete (greenfield-wu/brownfield-wu → brief → detail → architect → ux → phases → tasks → qa-planning)
+3. **Define Planning Phase Gates**
+   - **Agent Completion**: All 8 planning agents must complete (greenfield-wu/brownfield-wu → brief → detail → architect → ux → phases → tasks → qa-planning)
    - **Specification Completeness**: 100% of required sections filled
    - **QA Planning Score**: >= 95% for autonomous transition to build phase
    - **Manual Override**: Available if score 90-94% with justification
@@ -161,7 +161,7 @@ pipeline_stages:
         enforcement: tsc --noEmit
         bypass: not_allowed
 
-  clarity:
+  planning:
     gates:
       - name: Agent Completion
         threshold: 8/8 agents complete

package/framework/tasks/qa-planning-risk-matrix.md

@@ -2,7 +2,7 @@
 id: qa-planning-risk-matrix
 agent: qa-planning
 trigger: qa-planning-coverage-plan
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [risk-matrix.yaml]

package/framework/tasks/qa-planning-test-strategy.md

@@ -2,7 +2,7 @@
 id: qa-planning-test-strategy
 agent: qa-planning
 trigger: orchestrator
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [test-strategy.yaml]

package/framework/tasks/tasks-acceptance-write.md

@@ -2,7 +2,7 @@
 id: tasks-acceptance-write
 agent: tasks
 trigger: tasks-estimate
-phase: clarity
+phase: planning
 requires_input: false
 parallelizable: false
 outputs: [task-criteria.yaml]