feat: Add templates for epics, product brief, and requirements documentation

- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
2026-03-10 17:11:04 +08:00 · 2026-03-07 13:32:04 +08:00
parent 7ee9b579fa
commit 29a1fea467
255 changed files with 14407 additions and 21120 deletions
--- a/.claude/skills/team-ultra-analyze/roles/analyst/role.md
+++ b/.claude/skills/team-ultra-analyze/roles/analyst/role.md
@@ -0,0 +1,90 @@
+---
+role: analyst
+prefix: ANALYZE
+inner_loop: false
+additional_prefixes: [ANALYZE-fix]
+message_types:
+  success: analysis_ready
+  error: error
+---
+
+# Deep Analyst
+
+Perform deep multi-perspective analysis on exploration results via CLI tools. Generate structured insights, discussion points, and recommendations with confidence levels.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Exploration results | `<session>/explorations/*.json` | Yes |
+
+1. Extract session path, topic, perspective, dimensions from task description
+2. Detect direction-fix mode: `type:\s*direction-fix` with `adjusted_focus:\s*(.+)`
+3. Load corresponding exploration results:
+
+| Condition | Source |
+|-----------|--------|
+| Direction fix | Read ALL exploration files, merge context |
+| Normal ANALYZE-N | Read exploration matching number N |
+| Fallback | Read first available exploration file |
+
+4. Select CLI tool by perspective:
+
+| Perspective | CLI Tool | Rule Template |
+|-------------|----------|---------------|
+| technical | gemini | analysis-analyze-code-patterns |
+| architectural | claude | analysis-review-architecture |
+| business | codex | analysis-analyze-code-patterns |
+| domain_expert | gemini | analysis-analyze-code-patterns |
+| direction-fix (any) | gemini | analysis-diagnose-bug-root-cause |
+
+## Phase 3: Deep Analysis via CLI
+
+Build analysis prompt with exploration context:
+
+```
+PURPOSE: <Normal: "Deep analysis of '<topic>' from <perspective> perspective">
+         <Fix: "Supplementary analysis with adjusted focus on '<adjusted_focus>'">
+Success: Actionable insights with confidence levels and evidence references
+
+PRIOR EXPLORATION CONTEXT:
+- Key files: <top 5-8 files from exploration>
+- Patterns found: <top 3-5 patterns>
+- Key findings: <top 3-5 findings>
+
+TASK:
+- <perspective-specific analysis tasks>
+- Generate structured findings with confidence levels (high/medium/low)
+- Identify discussion points requiring user input
+- List open questions needing further exploration
+
+MODE: analysis
+CONTEXT: @**/* | Topic: <topic>
+EXPECTED: Structured analysis with: key_insights, key_findings, discussion_points, open_questions, recommendations
+CONSTRAINTS: Focus on <perspective> perspective | <dimensions>
+```
+
+Execute: `ccw cli -p "<prompt>" --tool <cli-tool> --mode analysis --rule <rule>`
+
+## Phase 4: Result Aggregation
+
+Write analysis output to `<session>/analyses/analysis-<num>.json`:
+
+```json
+{
+  "perspective": "<perspective>",
+  "dimensions": ["<dim1>", "<dim2>"],
+  "is_direction_fix": false,
+  "key_insights": [{"insight": "...", "confidence": "high", "evidence": "file:line"}],
+  "key_findings": [{"finding": "...", "file_ref": "...", "impact": "..."}],
+  "discussion_points": ["..."],
+  "open_questions": ["..."],
+  "recommendations": [{"action": "...", "rationale": "...", "priority": "high"}],
+  "_metadata": {"cli_tool": "...", "cli_rule": "...", "perspective": "...", "timestamp": "..."}
+}
+```
+
+Update `<session>/wisdom/.msg/meta.json` under `analyst` namespace:
+- Read existing -> merge `{ "analyst": { perspective, insight_count, finding_count, is_direction_fix } }` -> write back
--- a/.claude/skills/team-ultra-analyze/roles/coordinator/commands/analyze.md
+++ b/.claude/skills/team-ultra-analyze/roles/coordinator/commands/analyze.md
@@ -0,0 +1,73 @@
+# Analyze Task
+
+Parse topic -> detect pipeline mode and perspectives -> output analysis config.
+
+**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
+
+## Signal Detection
+
+### Pipeline Mode Detection
+
+Parse `--mode` from arguments first. If not specified, auto-detect from topic description:
+
+| Condition | Mode | Depth |
+|-----------|------|-------|
+| `--mode=quick` or topic contains "quick/overview/fast" | Quick | 1 |
+| `--mode=deep` or topic contains "deep/thorough/detailed/comprehensive" | Deep | N (from perspectives) |
+| Default (no match) | Standard | N (from perspectives) |
+
+### Dimension Detection
+
+Scan topic keywords to select analysis perspectives:
+
+| Dimension | Keywords |
+|-----------|----------|
+| architecture | architecture, design, structure |
+| implementation | implement, code, source |
+| performance | performance, optimize, speed |
+| security | security, auth, vulnerability |
+| concept | concept, theory, principle |
+| comparison | compare, vs, difference |
+| decision | decision, choice, tradeoff |
+
+**Depth** = number of selected perspectives. Quick mode always uses depth=1.
+
+## Pipeline Mode Rules
+
+| Mode | Task Structure |
+|------|----------------|
+| quick | EXPLORE-001 -> ANALYZE-001 -> SYNTH-001 (serial, depth=1) |
+| standard | EXPLORE-001..N (parallel) -> ANALYZE-001..N (parallel) -> DISCUSS-001 -> SYNTH-001 |
+| deep | Same as standard but SYNTH-001 omitted (created dynamically after discussion loop) |
+
+## Output
+
+Write analysis config to coordinator state (not a file), to be used by dispatch.md:
+
+```json
+{
+  "pipeline_mode": "<quick|standard|deep>",
+  "depth": <number>,
+  "perspectives": ["<perspective1>", "<perspective2>"],
+  "topic": "<original topic>",
+  "dimensions": ["<dim1>", "<dim2>"]
+}
+```
+
+## Complexity Scoring
+
+| Factor | Points |
+|--------|--------|
+| Per perspective | +1 |
+| Deep mode | +2 |
+| Cross-domain (3+ perspectives) | +1 |
+
+Results: 1-3 Quick, 4-6 Standard, 7+ Deep (if not explicitly set)
+
+## Discussion Loop Configuration
+
+| Mode | Max Discussion Rounds |
+|------|----------------------|
+| quick | 0 |
+| standard | 1 |
+| deep | 5 |
--- a/.claude/skills/team-ultra-analyze/roles/coordinator/role.md
+++ b/.claude/skills/team-ultra-analyze/roles/coordinator/role.md
@@ -36,16 +36,6 @@ When coordinator needs to execute a command (dispatch, monitor):
 3. **Commands are inline execution guides** -- NOT separate agents or subprocesses
 4. **Execute synchronously** -- complete the command workflow before proceeding

-Example:
-```
-Phase 3 needs task dispatch
-  -> Read roles/coordinator/commands/dispatch.md
-  -> Execute Phase 2 (Context Loading)
-  -> Execute Phase 3 (Task Chain Creation)
-  -> Execute Phase 4 (Validation)
-  -> Continue to Phase 4
-```
-
 ---

 ## Entry Router
@@ -54,12 +44,12 @@ When coordinator is invoked, detect invocation type:

 | Detection | Condition | Handler |
 |-----------|-----------|---------|
-| Worker callback | Message contains role tag [explorer], [analyst], [discussant], [synthesizer] | -> handleCallback |
-| Status check | Arguments contain "check" or "status" | -> handleCheck |
-| Manual resume | Arguments contain "resume" or "continue" | -> handleResume |
-| Pipeline complete | All tasks have status "completed" | -> handleComplete |
-| Interrupted session | Active/paused session exists | -> Phase 0 (Session Resume Check) |
-| New session | None of above | -> Phase 1 (Topic Understanding) |
+| Worker callback | Message contains role tag [explorer], [analyst], [discussant], [synthesizer] | -> handleCallback (monitor.md) |
+| Status check | Arguments contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Arguments contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Pipeline complete | All tasks have status "completed" | -> handleComplete (monitor.md) |
+| Interrupted session | Active/paused session exists | -> Phase 0 |
+| New session | None of above | -> Phase 1 |

 For callback/check/resume/complete: load `commands/monitor.md` and execute matched handler, then STOP.

@@ -85,12 +75,7 @@ For callback/check/resume/complete: load `commands/monitor.md` and execute match
 Triggered when an active/paused session is detected on coordinator entry.

 1. Load session.json from detected session folder
-2. Audit task list:
-
-```
-TaskList()
-```
-
+2. Audit task list: `TaskList()`
 3. Reconcile session state vs task status:

 | Task Status | Session Expects | Action |
@@ -99,42 +84,19 @@ TaskList()
 | completed | Already tracked | Skip |
 | pending + unblocked | Ready to run | Include in spawn list |

-4. Rebuild team if not active:
-
-```
-TeamCreate({ team_name: "ultra-analyze" })
-```
-
+4. Rebuild team if not active: `TeamCreate({ team_name: "ultra-analyze" })`
 5. Spawn workers for ready tasks -> Phase 4 coordination loop

 ---

 ## Phase 1: Topic Understanding & Requirement Clarification

+TEXT-LEVEL ONLY. No source code reading.
+
 1. Parse user task description from $ARGUMENTS
 2. Extract explicit settings: `--mode`, scope, focus areas
-
-3. **Pipeline mode selection**:
-
-| Condition | Mode | Depth |
-|-----------|------|-------|
-| `--mode=quick` or topic contains "quick/overview/fast" | Quick | 1 |
-| `--mode=deep` or topic contains "deep/thorough/detailed/comprehensive" | Deep | N (from perspectives) |
-| Default | Standard | N (from perspectives) |
-
-4. **Dimension detection** (from topic keywords):
-
-| Dimension | Keywords |
-|-----------|----------|
-| architecture | architecture, design, structure |
-| implementation | implement, code |
-| performance | performance, optimize |
-| security | security, auth |
-| concept | concept, theory |
-| comparison | compare, vs |
-| decision | decision, choice |
-
-5. **Interactive clarification** (non-auto mode): AskUserQuestion for focus, perspectives, depth.
+3. Delegate to `commands/analyze.md` for signal detection and pipeline mode selection
+4. **Interactive clarification** (non-auto mode): AskUserQuestion for focus, perspectives, depth.

 ---

@@ -156,9 +118,8 @@ TeamCreate({ team_name: "ultra-analyze" })
 ```

 3. Write session.json with mode, requirement, timestamp
-4. Initialize .msg/meta.json with pipeline metadata:
+4. Initialize .msg/meta.json with pipeline metadata via team_msg:
 ```typescript
-// Use team_msg to write pipeline metadata to .msg/meta.json
 mcp__ccw-tools__team_msg({
  operation: "log",
  session_id: "<session-id>",
@@ -173,7 +134,6 @@ mcp__ccw-tools__team_msg({
  }
 })
 ```
-
 5. Call `TeamCreate({ team_name: "ultra-analyze" })`

 ---
@@ -181,7 +141,6 @@ mcp__ccw-tools__team_msg({
 ## Phase 3: Create Task Chain

 Execute `commands/dispatch.md` inline (Command Execution Protocol):
-
 1. Read `roles/coordinator/commands/dispatch.md`
 2. Follow dispatch Phase 2 -> Phase 3 -> Phase 4
 3. Result: all pipeline tasks created with correct blockedBy dependencies
@@ -192,38 +151,16 @@ Execute `commands/dispatch.md` inline (Command Execution Protocol):

 ### Initial Spawn

-Find first unblocked tasks and spawn their workers:
-
-```
-Agent({
-  subagent_type: "team-worker",
-  description: "Spawn explorer worker",
-  team_name: "ultra-analyze",
-  name: "explorer",
-  run_in_background: true,
-  prompt: `## Role Assignment
-role: explorer
-role_spec: .claude/skills/team-ultra-analyze/role-specs/explorer.md
-session: <session-folder>
-session_id: <session-id>
-team_name: ultra-analyze
-requirement: <topic-description>
-inner_loop: false
-
-Read role_spec file to load Phase 2-4 domain instructions.
-Execute built-in Phase 1 -> role-spec Phase 2-4 -> built-in Phase 5.`
-})
-```
+Find first unblocked tasks and spawn their workers. Use SKILL.md Worker Spawn Template with:
+- `role_spec: .claude/skills/team-ultra-analyze/roles/<role>/role.md`
+- `team_name: ultra-analyze`
+- `inner_loop: false`

 **STOP** after spawning. Wait for worker callback.

 ### Coordination (via monitor.md handlers)

-All subsequent coordination is handled by `commands/monitor.md` handlers triggered by worker callbacks:
-
- handleCallback -> mark task done -> check pipeline -> handleSpawnNext
- handleSpawnNext -> find ready tasks -> spawn team-worker agents -> STOP
- handleComplete -> all done -> Phase 5
+All subsequent coordination is handled by `commands/monitor.md` handlers triggered by worker callbacks.

 ---

@@ -247,7 +184,7 @@ All subsequent coordination is handled by `commands/monitor.md` handlers trigger
 ```
 AskUserQuestion({
  questions: [{
-    question: "Team pipeline complete. What would you like to do?",
+    question: "Ultra-Analyze pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
@@ -259,13 +196,7 @@ AskUserQuestion({
 })
 ```

-6. Handle user choice:
-
-| Choice | Steps |
-|--------|-------|
-| Archive & Clean | TaskList -> verify all completed -> update session status="completed" -> TeamDelete() -> output final summary |
-| Keep Active | Update session status="paused" -> output resume instructions |
-| Export Results | AskUserQuestion for target directory -> copy artifacts -> Archive & Clean |
+6. Handle user choice per SKILL.md Completion Action section.

 ---

--- a/.claude/skills/team-ultra-analyze/roles/discussant/role.md
+++ b/.claude/skills/team-ultra-analyze/roles/discussant/role.md
@@ -0,0 +1,107 @@
+---
+role: discussant
+prefix: DISCUSS
+inner_loop: false
+message_types:
+  success: discussion_processed
+  error: error
+---
+
+# Discussant
+
+Process analysis results and user feedback. Execute direction adjustments, deep-dive explorations, or targeted Q&A based on discussion type. Update discussion timeline.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Analysis results | `<session>/analyses/*.json` | Yes |
+| Exploration results | `<session>/explorations/*.json` | No |
+
+1. Extract session path, topic, round, discussion type, user feedback:
+
+| Field | Pattern | Default |
+|-------|---------|---------|
+| sessionFolder | `session:\s*(.+)` | required |
+| topic | `topic:\s*(.+)` | required |
+| round | `round:\s*(\d+)` | 1 |
+| discussType | `type:\s*(.+)` | "initial" |
+| userFeedback | `user_feedback:\s*(.+)` | empty |
+
+2. Read all analysis and exploration results
+3. Aggregate current findings, insights, open questions
+
+## Phase 3: Discussion Processing
+
+Select strategy by discussion type:
+
+| Type | Mode | Description |
+|------|------|-------------|
+| initial | inline | Aggregate all analyses: convergent themes, conflicts, top discussion points |
+| deepen | cli | Use CLI tool to investigate open questions deeper |
+| direction-adjusted | cli | Re-analyze via `ccw cli` from adjusted perspective |
+| specific-questions | cli | Targeted exploration answering user questions |
+
+**initial**: Cross-perspective summary -- identify convergent themes, conflicting views, top 5 discussion points and open questions from all analyses.
+
+**deepen**: Use CLI tool for deep investigation:
+```javascript
+Bash({
+  command: `ccw cli -p "PURPOSE: Investigate open questions and uncertain insights; success = evidence-based findings
+TASK: • Focus on open questions: <questions> • Find supporting evidence • Validate uncertain insights • Document findings
+MODE: analysis
+CONTEXT: @**/* | Memory: Session <session-folder>, previous analyses
+EXPECTED: JSON output with investigation results | Write to <session>/discussions/deepen-<num>.json
+CONSTRAINTS: Evidence-based analysis only
+" --tool gemini --mode analysis --rule analysis-trace-code-execution`,
+  run_in_background: false
+})
+```
+
+**direction-adjusted**: CLI re-analysis from adjusted focus:
+```javascript
+Bash({
+  command: `ccw cli -p "Re-analyze '<topic>' with adjusted focus on '<userFeedback>'" --tool gemini --mode analysis`,
+  run_in_background: false
+})
+```
+
+**specific-questions**: Use CLI tool for targeted Q&A:
+```javascript
+Bash({
+  command: `ccw cli -p "PURPOSE: Answer specific user questions about <topic>; success = clear, evidence-based answers
+TASK: • Answer: <userFeedback> • Provide code references • Explain context
+MODE: analysis
+CONTEXT: @**/* | Memory: Session <session-folder>
+EXPECTED: JSON output with answers and evidence | Write to <session>/discussions/questions-<num>.json
+CONSTRAINTS: Direct answers with code references
+" --tool gemini --mode analysis`,
+  run_in_background: false
+})
+```
+
+## Phase 4: Update Discussion Timeline
+
+1. Write round content to `<session>/discussions/discussion-round-<num>.json`:
+```json
+{
+  "round": 1, "type": "initial", "user_feedback": "...",
+  "updated_understanding": { "confirmed": [], "corrected": [], "new_insights": [] },
+  "new_findings": [], "new_questions": [], "timestamp": "..."
+}
+```
+
+2. Append round section to `<session>/discussion.md`:
+```markdown
+### Round <N> - Discussion (<timestamp>)
+#### Type: <discussType>
+#### User Input: <userFeedback or "(Initial discussion round)">
+#### Updated Understanding
+**Confirmed**: <list> | **Corrected**: <list> | **New Insights**: <list>
+#### New Findings / Open Questions
+```
+
+Update `<session>/wisdom/.msg/meta.json` under `discussant` namespace:
+- Read existing -> merge `{ "discussant": { round, type, new_insight_count, corrected_count } }` -> write back
--- a/.claude/skills/team-ultra-analyze/roles/explorer/role.md
+++ b/.claude/skills/team-ultra-analyze/roles/explorer/role.md
@@ -0,0 +1,74 @@
+---
+role: explorer
+prefix: EXPLORE
+inner_loop: false
+message_types:
+  success: exploration_ready
+  error: error
+---
+
+# Codebase Explorer
+
+Explore codebase structure through cli-explore-agent, collecting structured context (files, patterns, findings) for downstream analysis. One explorer per analysis perspective.
+
+## Phase 2: Context & Scope Assessment
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+
+1. Extract session path, topic, perspective, dimensions from task description:
+
+| Field | Pattern | Default |
+|-------|---------|---------|
+| sessionFolder | `session:\s*(.+)` | required |
+| topic | `topic:\s*(.+)` | required |
+| perspective | `perspective:\s*(.+)` | "general" |
+| dimensions | `dimensions:\s*(.+)` | "general" |
+
+2. Determine exploration number from task subject (EXPLORE-N)
+3. Build exploration strategy by perspective:
+
+| Perspective | Focus | Search Depth |
+|-------------|-------|-------------|
+| general | Overall codebase structure and patterns | broad |
+| technical | Implementation details, code patterns, feasibility | medium |
+| architectural | System design, module boundaries, interactions | broad |
+| business | Business logic, domain models, value flows | medium |
+| domain_expert | Domain patterns, standards, best practices | deep |
+
+## Phase 3: Codebase Exploration
+
+Use CLI tool for codebase exploration:
+
+```javascript
+Bash({
+  command: `ccw cli -p "PURPOSE: Explore codebase for <topic> from <perspective> perspective; success = structured findings with relevant files and patterns
+TASK: • Run module depth analysis • Search for topic-related patterns • Identify key files and their relationships • Extract architectural insights
+MODE: analysis
+CONTEXT: @**/* | Memory: Session <session-folder>, perspective <perspective>
+EXPECTED: JSON output with: relevant_files (path, relevance, summary), patterns, key_findings, module_map, questions_for_analysis, _metadata (perspective, search_queries, timestamp)
+CONSTRAINTS: Focus on <perspective> angle - <strategy.focus> | Write to <session>/explorations/exploration-<num>.json
+" --tool gemini --mode analysis --rule analysis-analyze-code-patterns`,
+  run_in_background: false
+})
+```
+
+**ACE fallback** (when CLI produces no output):
+```javascript
+mcp__ace-tool__search_context({ project_root_path: ".", query: "<topic> <perspective>" })
+```
+
+## Phase 4: Result Validation
+
+| Check | Method | Action on Failure |
+|-------|--------|-------------------|
+| Output file exists | Read output path | Create empty result, run ACE fallback |
+| Has relevant_files | Array length > 0 | Trigger ACE supplementary search |
+| Has key_findings | Array length > 0 | Note partial results, proceed |
+
+Write validated exploration to `<session>/explorations/exploration-<num>.json`.
+
+Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
+- Read existing -> merge `{ "explorer": { perspective, file_count, finding_count } }` -> write back
--- a/.claude/skills/team-ultra-analyze/roles/synthesizer/role.md
+++ b/.claude/skills/team-ultra-analyze/roles/synthesizer/role.md
@@ -0,0 +1,78 @@
+---
+role: synthesizer
+prefix: SYNTH
+inner_loop: false
+message_types:
+  success: synthesis_ready
+  error: error
+---
+
+# Synthesizer
+
+Integrate all explorations, analyses, and discussions into final conclusions. Cross-perspective theme extraction, conflict resolution, evidence consolidation, and recommendation prioritization. Pure integration role -- no external tools or CLI calls.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| All artifacts | `<session>/explorations/*.json`, `analyses/*.json`, `discussions/*.json` | Yes |
+| Decision trail | From wisdom/.msg/meta.json | No |
+
+1. Extract session path and topic from task description
+2. Read all exploration, analysis, and discussion round files
+3. Load decision trail and current understanding from meta.json
+4. Select synthesis strategy:
+
+| Condition | Strategy |
+|-----------|----------|
+| Single analysis, no discussions | simple (Quick mode summary) |
+| Multiple analyses, >2 discussion rounds | deep (track evolution) |
+| Default | standard (cross-perspective integration) |
+
+## Phase 3: Cross-Perspective Synthesis
+
+Execute synthesis across four dimensions:
+
+**1. Theme Extraction**: Identify convergent themes across all analysis perspectives. Cluster insights by similarity, rank by cross-perspective confirmation count.
+
+**2. Conflict Resolution**: Identify contradictions between perspectives. Present both sides with trade-off analysis when irreconcilable.
+
+**3. Evidence Consolidation**: Deduplicate findings, aggregate by file reference. Map evidence to conclusions with confidence levels:
+
+| Level | Criteria |
+|-------|----------|
+| High | Multiple sources confirm, strong evidence |
+| Medium | Single source or partial evidence |
+| Low | Speculative, needs verification |
+
+**4. Recommendation Prioritization**: Sort all recommendations by priority (high > medium > low), deduplicate, cap at 10.
+
+Integrate decision trail from discussion rounds into final narrative.
+
+## Phase 4: Write Conclusions
+
+1. Write `<session>/conclusions.json`:
+```json
+{
+  "session_id": "...", "topic": "...", "completed": "ISO-8601",
+  "summary": "Executive summary...",
+  "key_conclusions": [{"point": "...", "evidence": "...", "confidence": "high"}],
+  "recommendations": [{"action": "...", "rationale": "...", "priority": "high"}],
+  "open_questions": ["..."],
+  "decision_trail": [{"round": 1, "decision": "...", "context": "..."}],
+  "cross_perspective_synthesis": { "convergent_themes": [], "conflicts_resolved": [], "unique_contributions": [] },
+  "_metadata": { "explorations": 3, "analyses": 3, "discussions": 2, "strategy": "standard" }
+}
+```
+
+2. Append conclusions section to `<session>/discussion.md`:
+```markdown
+## Conclusions
+### Summary / Key Conclusions / Recommendations / Remaining Questions
+## Decision Trail / Current Understanding (Final) / Session Statistics
+```
+
+Update `<session>/wisdom/.msg/meta.json` under `synthesizer` namespace:
+- Read existing -> merge `{ "synthesizer": { conclusion_count, recommendation_count, open_question_count } }` -> write back