Files
Claude-Code-Workflow/.claude/commands/workflow/brainstorm/synthesis.md
catlog22 c7ec9dd040 feat: Refactor and enhance brainstorming workflow commands
- Removed deprecated `gemini-init.md` command and migrated its functionality to a new structure under `.claude/commands/gemini/`.
- Introduced `auto-parallel.md` for parallel brainstorming automation with dynamic role selection and concurrent execution.
- Added `auto-squeeze.md` for sequential command coordination in brainstorming workflows, ensuring structured execution from framework generation to synthesis.
- Updated `plan.md` to improve clarity on project structure analysis and command execution strategies.
- Enhanced error handling and session management across all commands to ensure robustness and user guidance.
- Improved documentation for generated files and command options to facilitate user understanding and usage.
2025-09-29 15:48:42 +08:00

13 KiB

name, description, usage, argument-hint, examples, allowed-tools
name description usage argument-hint examples allowed-tools
synthesis Generate synthesis-report.md from topic-framework and role analyses with @ references /workflow:brainstorm:synthesis no arguments required - synthesizes existing framework and role analyses
/workflow:brainstorm:synthesis
Read(*), Write(*), TodoWrite(*), Glob(*)

🧩 Synthesis Document Generator

Core Function

Specialized command for generating synthesis-report.md that integrates topic-framework.md and all role analysis.md files using @ reference system. Creates comprehensive strategic analysis with cross-role insights.

Primary Capabilities

  • Framework Integration: Reference topic-framework.md discussion points across all roles
  • Role Analysis Integration: Consolidate all role/analysis.md files using @ references
  • Cross-Framework Comparison: Compare how each role addressed framework discussion points
  • @ Reference System: Create structured references to source documents
  • Update Detection: Smart updates when new role analyses are added

Document Integration Model

Three-Document Reference System:

  1. topic-framework.md → Structured discussion framework (input)
  2. [role]/analysis.md → Role-specific analyses addressing framework (input)
  3. synthesis-report.md → Integrated synthesis with @ references (output)

⚙️ Execution Protocol

Phase 1: Document Discovery & Validation

# Detect active brainstorming session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
    session_id = get_active_session()
    brainstorm_dir = .workflow/WFS-{session}/.brainstorming/
ELSE:
    ERROR: "No active brainstorming session found"
    EXIT

# Validate required documents
CHECK: brainstorm_dir/topic-framework.md
IF NOT EXISTS:
    ERROR: "topic-framework.md not found. Run /workflow:brainstorm:artifacts first"
    EXIT

Phase 2: Role Analysis Discovery

# Discover available role analyses
SCAN_DIRECTORY: .workflow/WFS-{session}/.brainstorming/
FIND_ANALYSES: [
    */analysis.md files in role directories
]
LOAD_DOCUMENTS: {
    "topic_framework": topic-framework.md,
    "role_analyses": [discovered analysis.md files],
    "existing_synthesis": synthesis-report.md (if exists)
}

Phase 3: Update Mechanism Check

# Check for existing synthesis
IF synthesis-report.md EXISTS:
    SHOW current synthesis summary to user
    ASK: "Synthesis exists. Do you want to:"
    OPTIONS:
      1. "Regenerate completely" → Create new synthesis
      2. "Update with new analyses" → Integrate new role analyses
      3. "Preserve existing" → Exit without changes
ELSE:
    CREATE new synthesis

Phase 4: Synthesis Generation Process

Initialize synthesis task tracking:

[
  {"content": "Validate topic-framework.md and role analyses availability", "status": "in_progress", "activeForm": "Validating source documents"},
  {"content": "Load topic framework discussion points structure", "status": "pending", "activeForm": "Loading framework structure"},
  {"content": "Cross-analyze role responses to each framework point", "status": "pending", "activeForm": "Cross-analyzing framework responses"},
  {"content": "Generate synthesis-report.md with @ references", "status": "pending", "activeForm": "Generating synthesis with references"},
  {"content": "Update session metadata with synthesis completion", "status": "pending", "activeForm": "Updating session metadata"}
]

Phase 4: Cross-Role Analysis Execution

4.1 Data Collection and Preprocessing

FOR each role_directory in brainstorming_roles:
    IF role_directory exists:
        role_analysis = Read(role_directory + "/analysis.md")
        role_recommendations = Read(role_directory + "/recommendations.md") IF EXISTS
        role_insights[role] = extract_key_insights(role_analysis)
        role_recommendations[role] = extract_recommendations(role_analysis)
        role_concerns[role] = extract_concerns_risks(role_analysis)
    END IF
END FOR

4.2 Cross-Role Insight Analysis

# Consensus identification
consensus_areas = identify_common_themes(role_insights)
agreement_matrix = create_agreement_matrix(role_recommendations)

# Disagreement analysis
disagreement_areas = identify_conflicting_views(role_insights)
tension_points = analyze_role_conflicts(role_recommendations)

# Innovation opportunity extraction
innovation_opportunities = extract_breakthrough_ideas(role_insights)
synergy_opportunities = identify_cross_role_synergies(role_insights)

4.3 Priority and Decision Matrix Generation

# Create comprehensive evaluation matrix
FOR each recommendation:
    impact_score = calculate_business_impact(recommendation, role_insights)
    feasibility_score = calculate_technical_feasibility(recommendation, role_insights)
    effort_score = calculate_implementation_effort(recommendation, role_insights)
    risk_score = calculate_associated_risks(recommendation, role_insights)
    
    priority_score = weighted_score(impact_score, feasibility_score, effort_score, risk_score)
END FOR

SORT recommendations BY priority_score DESC

📊 Output Specification

Output Location

.workflow/WFS-{topic-slug}/.brainstorming/
├── topic-framework.md          # Input: Framework structure
├── [role]/analysis.md          # Input: Role analyses (multiple)
└── synthesis-report.md         # ★ OUTPUT: Integrated synthesis with @ references

Core Output Documents

synthesis-report.md Structure

# [Topic] - Integrated Analysis

**Framework Reference**: @topic-framework.md
**Generated**: [timestamp] | **Session**: WFS-[topic-slug]

## Executive Summary
Brief synthesis of key insights and recommendations across all role perspectives.

## Framework Analysis Integration

### Discussion Point 1: Core Requirements
**Framework Questions**: @topic-framework.md (Core Requirements section)

**Role Perspectives**:
- **System Architect**: @system-architect/analysis.md (requirements section)
- **Product Manager**: @product-manager/analysis.md (requirements section)
- **Security Expert**: @security-expert/analysis.md (requirements section)

**Cross-Role Insights**:
- [Consensus areas and disagreements on core requirements]
- [Integration recommendations]

### Discussion Point 2: Technical Considerations
**Framework Questions**: @topic-framework.md (Technical Considerations section)

**Role Perspectives**:
- **System Architect**: @system-architect/analysis.md (technical section)
- **Data Architect**: @data-architect/analysis.md (technical section)
- **UI Designer**: @ui-designer/analysis.md (technical section)

**Cross-Role Insights**:
- [Technical consensus and conflicts]
- [Implementation recommendations]

### ⚡ Breakthrough Ideas
**Innovation Opportunities**:
1. **{breakthrough_idea_1}**
   - Origin: {source_role}
   - Cross-role support: {supporting_roles}
   - Innovation potential: {potential_assessment}

2. **{breakthrough_idea_2}**
   - Origin: {source_role}
   - Cross-role support: {supporting_roles}
   - Innovation potential: {potential_assessment}

### 🔄 Areas of Disagreement
**Tension Points Requiring Resolution**:
1. **{disagreement_area_1}**
   - Conflicting views: {role1_view} vs {role2_view}
   - Root cause: {underlying_issue}
   - Resolution approach: {recommended_resolution}

2. **{disagreement_area_2}**
   - Conflicting views: {role1_view} vs {role2_view}
   - Root cause: {underlying_issue}
   - Resolution approach: {recommended_resolution}

## Comprehensive Recommendations Matrix

### 🎯 High Priority (Immediate Action)
| Recommendation | Business Impact | Technical Feasibility | Implementation Effort | Risk Level | Supporting Roles |
|----------------|-----------------|----------------------|---------------------|------------|------------------|
| {rec_1}        | High           | High                 | Medium              | Low        | PM, Arch, UX     |
| {rec_2}        | High           | Medium               | Low                 | Medium     | BA, PM, FP       |

### 📋 Medium Priority (Strategic Planning)
| Recommendation | Business Impact | Technical Feasibility | Implementation Effort | Risk Level | Supporting Roles |
|----------------|-----------------|----------------------|---------------------|------------|------------------|
| {rec_3}        | Medium         | High                 | High                | Medium     | Arch, DA, Sec    |
| {rec_4}        | Medium         | Medium               | Medium              | Low        | UX, UR, PM       |

### 🔬 Research Priority (Future Investigation)
| Recommendation | Business Impact | Technical Feasibility | Implementation Effort | Risk Level | Supporting Roles |
|----------------|-----------------|----------------------|---------------------|------------|------------------|
| {rec_5}        | High           | Unknown              | High                | High       | IL, Arch, PM     |
| {rec_6}        | Medium         | Low                  | High                | High       | IL, DA, Sec      |

## Implementation Strategy

### Phase 1: Foundation (0-3 months)
- **Focus**: High-priority, low-effort recommendations
- **Key Actions**: {action_list}
- **Success Metrics**: {metrics_list}
- **Required Resources**: {resource_list}

### Phase 2: Development (3-9 months)
- **Focus**: Medium-priority strategic initiatives
- **Key Actions**: {action_list}
- **Success Metrics**: {metrics_list}
- **Required Resources**: {resource_list}

### Phase 3: Innovation (9+ months)
- **Focus**: Research and breakthrough opportunities
- **Key Actions**: {action_list}
- **Success Metrics**: {metrics_list}
- **Required Resources**: {resource_list}

## Risk Assessment and Mitigation

### Critical Risks Identified
1. **{risk_1}**: {description} | Mitigation: {strategy}
2. **{risk_2}**: {description} | Mitigation: {strategy}

### Success Factors
- {success_factor_1}
- {success_factor_2}
- {success_factor_3}

## Next Steps and Follow-up
### Immediate Actions Required
### Decision Points Needing Resolution
### Continuous Monitoring Requirements
### Future Brainstorming Sessions Recommended

---
*This synthesis integrates insights from {role_count} perspectives to provide comprehensive strategic guidance.*

🔄 Session Integration

Status Synchronization

Upon completion, update workflow-session.json:

{
  "phases": {
    "BRAINSTORM": {
      "status": "completed",
      "synthesis_completed": true,
      "completed_at": "timestamp",
      "participating_roles": ["product-manager", "system-architect", "ui-designer", ...],
      "key_outputs": {
        "synthesis_report": ".workflow/WFS-{topic}/.brainstorming/synthesis-report.md",
        "action_plan": ".workflow/WFS-{topic}/.brainstorming/action-plan.md",
        "recommendations_matrix": ".workflow/WFS-{topic}/.brainstorming/recommendations-matrix.md"
      },
      "metrics": {
        "roles_analyzed": 9,
        "consensus_areas": 5,
        "breakthrough_ideas": 3,
        "high_priority_recommendations": 8,
        "implementation_phases": 3
      }
    }
  }
}

Quality Assurance

Required Synthesis Elements

  • Integration of all available role analyses with comprehensive coverage
  • Clear identification of consensus areas and disagreement points
  • Quantified priority recommendation matrix with evaluation criteria
  • Actionable implementation plan with phased approach
  • Comprehensive risk assessment with mitigation strategies

Synthesis Analysis Quality Standards

  • Completeness: Integrates all available role analyses without gaps
  • Insight Generation: Identifies cross-role patterns and deep insights
  • Actionability: Provides specific, executable recommendations and next steps
  • Balance: Considers all role perspectives and addresses concerns
  • Forward-Looking: Includes long-term strategic and innovation considerations

Output Validation Criteria

  • Priority-Based: Recommendations prioritized using multi-dimensional evaluation
  • Resource-Aware: Implementation plans consider resource and time constraints
  • Risk-Managed: Comprehensive risk assessment with mitigation strategies
  • Measurable Success: Clear success metrics and monitoring frameworks
  • Clear Actions: Specific next steps with assigned responsibilities and timelines

Integration Excellence Standards

  • Cross-Role Synthesis: Successfully identifies and resolves role perspective conflicts
  • Strategic Coherence: Recommendations form coherent strategic direction
  • Implementation Readiness: Plans are detailed enough for immediate execution
  • Stakeholder Alignment: Addresses needs and concerns of all key stakeholders
  • Continuous Improvement: Establishes framework for ongoing optimization and learning