Files
Claude-Code-Workflow/.claude/commands/workflow/brainstorm/auto-squeeze.md
catlog22 17e8243d35 refactor: Update brainstorming workflow roles and documentation
Major role restructuring to improve workflow efficiency and clarity:

## New Roles Added (4)
- product-owner: Backlog management and user story definition
- scrum-master: Sprint planning and agile process facilitation
- ux-expert: User experience optimization and usability testing
- subject-matter-expert: Domain expertise and industry standards

## Roles Removed (5)
- business-analyst → functionality split to product-owner and scrum-master
- feature-planner → merged into product-owner responsibilities
- innovation-lead → integrated into subject-matter-expert
- security-expert → integrated into subject-matter-expert
- user-researcher → merged into ux-expert

## Files Updated
### Command Files (.claude/commands/workflow/brainstorm/)
- Created: product-owner.md, scrum-master.md, ux-expert.md, subject-matter-expert.md
- Deleted: business-analyst.md, feature-planner.md, innovation-lead.md, security-expert.md, user-researcher.md
- Updated: artifacts.md, auto-parallel.md, auto-squeeze.md, synthesis.md

### Planning Templates (.claude/workflows/cli-templates/planning-roles/)
- Created: product-owner.md, scrum-master.md, ux-expert.md, subject-matter-expert.md
- Archived: Moved 5 deprecated roles to _deprecated/ with migration guide
- Added: _deprecated/README.md with deprecation details and migration paths

### Agent Configurations
- Updated conceptual-planning-agent.md with new role mappings
- Updated action-planning-agent.md with new role references

### Documentation
- Updated README.md brainstorming role tables and descriptions
- Updated README_CN.md with Chinese translations for new roles
- Updated workflow documentation files with new role references

## Breaking Changes
Commands for removed roles are no longer available. Use replacement roles:
- /workflow:brainstorm:business-analyst → use product-owner or scrum-master
- /workflow:brainstorm:feature-planner → use product-owner
- /workflow:brainstorm:innovation-lead → use subject-matter-expert
- /workflow:brainstorm:security-expert → use subject-matter-expert
- /workflow:brainstorm:user-researcher → use ux-expert

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-01 23:31:10 +08:00

11 KiB

name, description, usage, argument-hint, examples, allowed-tools
name description usage argument-hint examples allowed-tools
auto-squeeze Orchestrate 3-phase brainstorming workflow by executing commands sequentially /workflow:brainstorm:auto-squeeze "<topic>" topic or challenge description for coordinated brainstorming
/workflow:brainstorm:auto-squeeze "Build real-time collaboration feature"
/workflow:brainstorm:auto-squeeze "Optimize database performance for millions of users"
/workflow:brainstorm:auto-squeeze "Implement secure authentication system"
SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Glob(*)

Workflow Brainstorm Auto-Squeeze Command

Coordinator Role

This command is a pure orchestrator: Execute brainstorming commands in sequence (artifacts → roles → synthesis), auto-select relevant roles, and ensure complete brainstorming workflow execution.

Execution Flow:

  1. Initialize TodoWrite → Execute Phase 1 (artifacts) → Validate framework → Update TodoWrite
  2. Select 2-3 relevant roles → Display selection → Execute Phase 2 (role analyses) → Update TodoWrite
  3. Execute Phase 3 (synthesis) → Validate outputs → Return summary

Core Rules

  1. Start Immediately: First action is TodoWrite initialization, second action is Phase 1 command execution
  2. Auto-Select Roles: Analyze topic keywords to select 2-3 most relevant roles (max 3)
  3. Display Selection: Show selected roles to user before execution
  4. Sequential Execution: Execute role commands one by one, not in parallel
  5. Complete All Phases: Do not return to user until synthesis completes
  6. Track Progress: Update TodoWrite after every command completion

3-Phase Execution

Phase 1: Framework Generation

Step 1.1: Role Selection Auto-select 2-3 roles based on topic keywords (see Role Selection Logic below)

Step 1.2: Generate Role-Specific Framework Command: SlashCommand(command="/workflow:brainstorm:artifacts \"[topic]\" --roles \"[role1,role2,role3]\"")

Input: Selected roles from step 1.1

Parse Output:

  • Verify topic-framework.md created with role-specific sections

Validation:

  • File .workflow/[session]/.brainstorming/topic-framework.md exists
  • Contains sections for each selected role
  • Includes cross-role integration points

TodoWrite: Mark phase 1 completed, mark "Display selected roles" as in_progress


Phase 2: Role Analysis Execution

Step 2.1: Role Selection Use keyword analysis to auto-select 2-3 roles:

Role Selection Logic:

  • Technical/Architecture keywords: architecture|system|performance|database|api|backend|scalability → system-architect, data-architect, subject-matter-expert
  • UI/UX keywords: user|ui|ux|interface|design|frontend|experience → ui-designer, ux-expert
  • Product/Business keywords: product|feature|business|workflow|process|customer → product-manager, product-owner
  • Agile/Delivery keywords: agile|sprint|scrum|team|collaboration|delivery → scrum-master, product-owner
  • Domain Expertise keywords: domain|standard|compliance|expertise|regulation → subject-matter-expert
  • Default: product-manager (if no clear match)

Selection Rules:

  • Maximum 3 roles
  • Select most relevant role first based on strongest keyword match
  • Include complementary perspectives (e.g., if system-architect selected, also consider security-expert)

Step 2.2: Display Selected Roles Show selection to user before execution:

Selected roles for analysis:
- ui-designer (UI/UX perspective)
- system-architect (Technical architecture)
- security-expert (Security considerations)

Step 2.3: Execute Role Commands Sequentially Execute each selected role command one by one:

Commands:

  • SlashCommand(command="/workflow:brainstorm:ui-designer")
  • SlashCommand(command="/workflow:brainstorm:ux-expert")
  • SlashCommand(command="/workflow:brainstorm:system-architect")
  • SlashCommand(command="/workflow:brainstorm:data-architect")
  • SlashCommand(command="/workflow:brainstorm:product-manager")
  • SlashCommand(command="/workflow:brainstorm:product-owner")
  • SlashCommand(command="/workflow:brainstorm:scrum-master")
  • SlashCommand(command="/workflow:brainstorm:subject-matter-expert")
  • SlashCommand(command="/workflow:brainstorm:test-strategist")

Validation (after each role):

  • File .workflow/[session]/.brainstorming/[role]/analysis.md exists
  • Contains role-specific analysis

TodoWrite: Mark each role task completed after execution, start next role as in_progress


Phase 3: Synthesis Generation

Command: SlashCommand(command="/workflow:brainstorm:synthesis")

Validation:

  • File .workflow/[session]/.brainstorming/synthesis-report.md exists
  • Contains cross-references to role analyses using @ notation

TodoWrite: Mark phase 3 completed

Return to User:

Brainstorming complete for topic: [topic]
Framework: .workflow/[session]/.brainstorming/topic-framework.md
Roles analyzed: [role1], [role2], [role3]
Synthesis: .workflow/[session]/.brainstorming/synthesis-report.md

TodoWrite Pattern

// Initialize (before Phase 1)
TodoWrite({todos: [
  {"content": "Generate topic framework", "status": "in_progress", "activeForm": "Generating topic framework"},
  {"content": "Display selected roles", "status": "pending", "activeForm": "Displaying selected roles"},
  {"content": "Execute ui-designer analysis", "status": "pending", "activeForm": "Executing ui-designer analysis"},
  {"content": "Execute system-architect analysis", "status": "pending", "activeForm": "Executing system-architect analysis"},
  {"content": "Execute security-expert analysis", "status": "pending", "activeForm": "Executing security-expert analysis"},
  {"content": "Generate synthesis report", "status": "pending", "activeForm": "Generating synthesis report"}
]})

// After Phase 1
TodoWrite({todos: [
  {"content": "Generate topic framework", "status": "completed", "activeForm": "Generating topic framework"},
  {"content": "Display selected roles", "status": "in_progress", "activeForm": "Displaying selected roles"},
  {"content": "Execute ui-designer analysis", "status": "pending", "activeForm": "Executing ui-designer analysis"},
  {"content": "Execute system-architect analysis", "status": "pending", "activeForm": "Executing system-architect analysis"},
  {"content": "Execute security-expert analysis", "status": "pending", "activeForm": "Executing security-expert analysis"},
  {"content": "Generate synthesis report", "status": "pending", "activeForm": "Generating synthesis report"}
]})

// After displaying roles
TodoWrite({todos: [
  {"content": "Generate topic framework", "status": "completed", "activeForm": "Generating topic framework"},
  {"content": "Display selected roles", "status": "completed", "activeForm": "Displaying selected roles"},
  {"content": "Execute ui-designer analysis", "status": "in_progress", "activeForm": "Executing ui-designer analysis"},
  {"content": "Execute system-architect analysis", "status": "pending", "activeForm": "Executing system-architect analysis"},
  {"content": "Execute security-expert analysis", "status": "pending", "activeForm": "Executing security-expert analysis"},
  {"content": "Generate synthesis report", "status": "pending", "activeForm": "Generating synthesis report"}
]})

// Continue pattern for each role and synthesis...

Data Flow

User Input (topic)
    ↓
Role Selection (analyze topic keywords)
    ↓ Output: 2-3 selected roles (e.g., ui-designer, system-architect, security-expert)
    ↓
Phase 1: artifacts "topic" --roles "role1,role2,role3"
    ↓ Input: topic + selected roles
    ↓ Output: role-specific topic-framework.md
    ↓
Display: Show selected roles to user
    ↓
Phase 2: Execute each role command sequentially
    ↓ Role 1 → reads role-specific section → analysis.md
    ↓ Role 2 → reads role-specific section → analysis.md
    ↓ Role 3 → reads role-specific section → analysis.md
    ↓
Phase 3: synthesis
    ↓ Input: role-specific framework + all role analyses
    ↓ Output: synthesis-report.md with role-targeted insights
    ↓
Return summary to user

Session Context: All commands use active brainstorming session, sharing:

  • Role-specific topic framework
  • Role-targeted analyses
  • Cross-role integration points
  • Synthesis with role-specific insights

Key Improvement: Framework is generated with roles parameter, ensuring all discussion points are relevant to selected roles

Role Selection Examples

Example 1: UI-Focused Topic

Topic: "Redesign user authentication interface" Keywords detected: user, interface, design Selected roles:

  • ui-designer (primary: UI/UX match)
  • ux-expert (secondary: user experience)
  • subject-matter-expert (complementary: auth standards)

Example 2: Architecture Topic

Topic: "Design scalable microservices architecture" Keywords detected: architecture, scalable, system Selected roles:

  • system-architect (primary: architecture match)
  • data-architect (secondary: scalability/data)
  • subject-matter-expert (complementary: domain expertise)

Example 3: Agile Delivery Topic

Topic: "Optimize team sprint planning and delivery process" Keywords detected: sprint, team, delivery, process Selected roles:

  • scrum-master (primary: agile process match)
  • product-owner (secondary: backlog/delivery focus)
  • product-manager (complementary: product strategy)

Error Handling

  • Framework Generation Failure: Stop workflow, report error, do not proceed to role selection
  • Role Analysis Failure: Log failure, continue with remaining roles, note in final summary
  • Synthesis Failure: Retry once, if still fails report partial completion with available analyses
  • Session Error: Report session issue, prompt user to check session status

Output Structure

.workflow/[session]/.brainstorming/
├── topic-framework.md          # Phase 1 output
├── [role1]/
│   └── analysis.md            # Phase 2 output (role 1)
├── [role2]/
│   └── analysis.md            # Phase 2 output (role 2)
├── [role3]/
│   └── analysis.md            # Phase 2 output (role 3)
└── synthesis-report.md        # Phase 3 output

Coordinator Checklist

Initialize TodoWrite with framework + display + N roles + synthesis tasks Execute Phase 1 (artifacts) immediately Validate topic-framework.md exists Analyze topic keywords for role selection Auto-select 2-3 most relevant roles (max 3) Display selected roles to user with rationale Execute each role command sequentially Validate each role's analysis.md after execution Update TodoWrite after each role completion Execute Phase 3 (synthesis) after all roles complete Validate synthesis-report.md exists Return summary with all generated files