chore: Release version v3.0.1

### Command Updates
- Remove test-strategist and user-researcher brainstorming roles
- Update to 8 core brainstorming roles for focused efficiency

### Documentation
- Update version badges to v3.0.1
- Add release notes to CHANGELOG.md
- Update version references in README files

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

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/agents/action-planning-agent.md

@@ -82,7 +82,7 @@ Phase 2: Document Generation (Autonomous Output)
     "topic_framework": ".workflow/WFS-auth/.brainstorming/topic-framework.md",
     "role_analyses": [
       ".workflow/WFS-auth/.brainstorming/system-architect/analysis.md",
-      ".workflow/WFS-auth/.brainstorming/security-expert/analysis.md"
+      ".workflow/WFS-auth/.brainstorming/subject-matter-expert/analysis.md"
     ]
   },
   "context_package": {

.claude/agents/conceptual-planning-agent.md

@@ -90,13 +90,12 @@ def handle_brainstorm_assignment(prompt):
 |------|-------------------|--------------|-----------|
 | system-architect | architecture_patterns, scalability_analysis, integration_points | Technical design and system structure | `mcp__exa__get_code_context_exa("microservices patterns")` |
 | ui-designer | user_flow_patterns, component_reuse, design_system_compliance | UI/UX patterns and consistency | `mcp__exa__get_code_context_exa("React design system patterns")` |
-| business-analyst | process_optimization, cost_analysis, efficiency_metrics, workflow_patterns | Business process and ROI | `mcp__exa__get_code_context_exa("business workflow automation")` |
 | data-architect | data_models, flow_patterns, storage_optimization | Data structure and flow | `mcp__exa__get_code_context_exa("database schema patterns")` |
-| security-expert | vulnerability_assessment, threat_modeling, compliance_check | Security risks and compliance | `mcp__exa__get_code_context_exa("security authentication patterns")` |
-| user-researcher | usage_patterns, pain_points, behavior_analysis | User behavior and needs | `mcp__exa__get_code_context_exa("user research methodologies")` |
 | product-manager | feature_alignment, market_fit, competitive_analysis | Product strategy and positioning | `mcp__exa__get_code_context_exa("product management frameworks")` |
-| innovation-lead | emerging_patterns, technology_trends, disruption_potential | Innovation opportunities | `mcp__exa__get_code_context_exa("emerging technology trends")` |
-| feature-planner | implementation_complexity, dependency_mapping, risk_assessment | Development planning | `mcp__exa__get_code_context_exa("agile development patterns")` |
+| product-owner | backlog_management, user_stories, acceptance_criteria | Product backlog and prioritization | `mcp__exa__get_code_context_exa("product backlog management patterns")` |
+| scrum-master | sprint_planning, team_dynamics, process_optimization | Agile process and collaboration | `mcp__exa__get_code_context_exa("scrum agile methodologies")` |
+| ux-expert | usability_optimization, interaction_design, design_systems | User experience and interface | `mcp__exa__get_code_context_exa("UX design patterns")` |
+| subject-matter-expert | domain_standards, compliance, best_practices | Domain expertise and standards | `mcp__exa__get_code_context_exa("industry best practices standards")` |
 
 ### Output Integration
 
@@ -134,12 +133,12 @@ When called, you receive:
 ### Role Options Include:
 - `system-architect` - Technical architecture, scalability, integration
 - `ui-designer` - User experience, interface design, usability
+- `ux-expert` - User experience optimization, interaction design, design systems
 - `product-manager` - Business value, user needs, market positioning
+- `product-owner` - Backlog management, user stories, acceptance criteria
+- `scrum-master` - Sprint planning, team dynamics, agile process
 - `data-architect` - Data flow, storage, analytics
-- `security-expert` - Security implications, threat modeling, compliance
-- `user-researcher` - User behavior, pain points, research insights
-- `business-analyst` - Process optimization, efficiency, ROI
-- `innovation-lead` - Emerging trends, disruptive technologies
+- `subject-matter-expert` - Domain expertise, industry standards, compliance
 - `test-strategist` - Testing strategy and quality assurance
 
 ### Single Role Execution

.claude/commands/cli/execute.md

@@ -167,7 +167,7 @@ RULES: $(cat [task_template]) | Task type: [task_type], Scope: [task_scope]
 cd .workflow/WFS-123 && ~/.claude/scripts/gemini-wrapper --approval-mode yolo -p "
 PURPOSE: Implement user profile editing
 TASK: Execute IMPL-001 implementation
-CONTEXT: @{src/user/**/*} @{.brainstorming/feature-planner/analysis.md} @{CLAUDE.md}
+CONTEXT: @{src/user/**/*} @{.brainstorming/product-owner/analysis.md} @{CLAUDE.md}
 EXPECTED: Profile edit API, UI components, validation, tests
 RULES: $(cat ~/.claude/workflows/cli-templates/prompts/development/feature.txt) | Type: feature, Scope: user module
 "

.claude/commands/workflow/brainstorm/artifacts.md

@@ -5,8 +5,8 @@ usage: /workflow:brainstorm:artifacts "<topic>" [--roles "role1,role2,role3"]
 argument-hint: "topic or challenge description for framework generation"
 examples:
   - /workflow:brainstorm:artifacts "Build real-time collaboration feature"
-  - /workflow:brainstorm:artifacts "Optimize database performance" --roles "system-architect,data-architect,security-expert"
-  - /workflow:brainstorm:artifacts "Implement secure authentication system" --roles "ui-designer,security-expert,user-researcher"
+  - /workflow:brainstorm:artifacts "Optimize database performance" --roles "system-architect,data-architect,subject-matter-expert"
+  - /workflow:brainstorm:artifacts "Implement secure authentication system" --roles "ui-designer,ux-expert,subject-matter-expert"
 allowed-tools: TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*)
 ---
 
@@ -109,7 +109,7 @@ Framework content adapts based on `--roles` parameter:
 - **Scope**: [Topic boundaries relevant to selected roles]
 - **Objectives**: [Goals from perspective of selected roles]
 - **Context**: [Background focusing on role-specific concerns]
-- **Target Roles**: ui-designer, system-architect, security-expert
+- **Target Roles**: ui-designer, system-architect, subject-matter-expert
 
 ## Role-Specific Discussion Points
 
@@ -135,21 +135,21 @@ Framework content adapts based on `--roles` parameter:
    - What are the performance requirements?
    - What dependencies must be managed?
 
-### For Security Expert
-1. **Security Requirements**
-   - What are the key security concerns?
-   - What threat vectors must be addressed?
-   - What compliance requirements apply?
+### For Subject Matter Expert
+1. **Domain Expertise & Standards**
+   - What industry standards and best practices apply?
+   - What regulatory compliance requirements exist?
+   - What domain-specific patterns should be followed?
 
-2. **Security Implementation**
-   - What authentication/authorization is needed?
-   - What data protection mechanisms are required?
-   - How to handle security incidents?
+2. **Technical Quality & Risk**
+   - What technical debt considerations exist?
+   - What scalability and maintenance implications apply?
+   - What knowledge transfer and documentation is needed?
 
 ## Cross-Role Integration Points
 - How do UI decisions impact architecture?
 - How does architecture constrain UI possibilities?
-- What security requirements affect both UI and architecture?
+- What domain standards affect both UI and architecture?
 
 ## Framework Usage
 **For Role Agents**: Address your specific section + integration points
@@ -157,7 +157,7 @@ Framework content adapts based on `--roles` parameter:
 **Update Process**: Use /workflow:brainstorm:artifacts to update
 
 ---
-*Generated for roles: ui-designer, system-architect, security-expert*
+*Generated for roles: ui-designer, system-architect, subject-matter-expert*
 *Last updated: [timestamp]*
 ```
 
@@ -200,9 +200,9 @@ Framework content adapts based on `--roles` parameter:
 
 ## Available Role Perspectives
 Framework supports analysis from any of these roles:
-- system-architect, ui-designer, security-expert
-- user-researcher, product-manager, business-analyst
-- data-architect, innovation-lead, feature-planner
+- **Technical**: system-architect, data-architect, subject-matter-expert
+- **Product & Design**: ui-designer, ux-expert, product-manager, product-owner
+- **Agile & Quality**: scrum-master, test-strategist
 
 ---
 *Comprehensive framework - adaptable to any role*
@@ -216,17 +216,17 @@ Framework supports analysis from any of these roles:
 **Technical Roles**:
 - `system-architect`: Architecture patterns, scalability, technology stack, integration
 - `data-architect`: Data modeling, processing workflows, analytics, storage
-- `security-expert`: Security requirements, threat modeling, compliance, protection
+- `subject-matter-expert`: Domain expertise, industry standards, compliance, best practices
 
 **Product & Design Roles**:
 - `ui-designer`: User interface, visual design, interaction patterns, accessibility
-- `user-researcher`: User needs, behavior analysis, usability testing, personas
+- `ux-expert`: User experience optimization, usability testing, interaction design, design systems
 - `product-manager`: Business value, feature prioritization, market positioning, roadmap
+- `product-owner`: Backlog management, user stories, acceptance criteria, stakeholder alignment
 
-**Business Roles**:
-- `business-analyst`: Process optimization, requirements analysis, cost-benefit, ROI
-- `innovation-lead`: Emerging technologies, competitive advantage, transformation, trends
-- `feature-planner`: Feature specification, user stories, acceptance criteria, dependencies
+**Agile & Quality Roles**:
+- `scrum-master`: Sprint planning, team dynamics, process optimization, delivery management
+- `test-strategist`: Testing strategies, quality assurance, test automation, validation approaches
 
 ### Dynamic Discussion Point Generation
 
@@ -248,23 +248,32 @@ Generate:
 
 #### Example 1: Architecture-Heavy Topic
 ```bash
-/workflow:brainstorm:artifacts "Design scalable microservices platform" --roles "system-architect,data-architect,security-expert"
+/workflow:brainstorm:artifacts "Design scalable microservices platform" --roles "system-architect,data-architect,subject-matter-expert"
 ```
 **Generated framework focuses on**:
 - Service architecture and communication patterns
 - Data flow and storage strategies
-- Security boundaries and authentication
+- Domain standards and best practices
 
 #### Example 2: User-Focused Topic
 ```bash
-/workflow:brainstorm:artifacts "Improve user onboarding experience" --roles "ui-designer,user-researcher,product-manager"
+/workflow:brainstorm:artifacts "Improve user onboarding experience" --roles "ui-designer,ux-expert,product-manager"
 ```
 **Generated framework focuses on**:
 - Onboarding flow and UI components
-- User behavior and pain points
+- User experience optimization and usability
 - Business value and success metrics
 
-#### Example 3: Comprehensive Analysis
+#### Example 3: Agile Delivery Topic
+```bash
+/workflow:brainstorm:artifacts "Optimize sprint delivery process" --roles "scrum-master,product-owner,test-strategist"
+```
+**Generated framework focuses on**:
+- Sprint planning and team collaboration
+- Backlog management and prioritization
+- Quality assurance and testing strategies
+
+#### Example 4: Comprehensive Analysis
 ```bash
 /workflow:brainstorm:artifacts "Build real-time collaboration feature"
 ```

.claude/commands/workflow/brainstorm/auto-parallel.md

@@ -18,15 +18,17 @@ allowed-tools: SlashCommand(*), Task(*), TodoWrite(*), Read(*), Write(*), Bash(*
 ```
 
 ## Role Selection Logic
-- **Technical & Architecture**: `architecture|system|performance|database|security` → system-architect, data-architect, security-expert
-- **Product & UX**: `user|ui|ux|interface|design|product|feature` → ui-designer, user-researcher, product-manager
+- **Technical & Architecture**: `architecture|system|performance|database|security` → system-architect, data-architect, security-expert, subject-matter-expert
+- **Product & UX**: `user|ui|ux|interface|design|product|feature|experience` → ui-designer, user-researcher, product-manager, ux-expert, product-owner
 - **Business & Process**: `business|process|workflow|cost|innovation|testing` → business-analyst, innovation-lead, test-strategist
+- **Agile & Delivery**: `agile|sprint|scrum|team|collaboration|delivery` → scrum-master, product-owner
+- **Domain Expertise**: `domain|standard|compliance|expertise|regulation` → subject-matter-expert
 - **Multi-role**: Complex topics automatically select 2-3 complementary roles
 - **Default**: `product-manager` if no clear match
 
 **Template Loading**: `bash($(cat "~/.claude/workflows/cli-templates/planning-roles/<role-name>.md"))`
 **Template Source**: `.claude/workflows/cli-templates/planning-roles/`
-**Available Roles**: business-analyst, data-architect, feature-planner, innovation-lead, product-manager, security-expert, system-architect, test-strategist, ui-designer, user-researcher
+**Available Roles**: data-architect, product-manager, product-owner, scrum-master, subject-matter-expert, system-architect, test-strategist, ui-designer, ux-expert
 
 **Example**:
 ```bash
@@ -72,9 +74,10 @@ Auto command coordinates independent specialized commands:
 4. **Command coordination**: SlashCommand handles execution and validation
 
 **Role Selection Logic**:
-- **Technical**: `architecture|system|performance|database|security` → system-architect, data-architect, security-expert
-- **Product & UX**: `user|ui|ux|interface|design|product|feature` → ui-designer, user-researcher, product-manager
-- **Business**: `business|process|workflow|cost|innovation` → business-analyst, innovation-lead
+- **Technical**: `architecture|system|performance|database` → system-architect, data-architect, subject-matter-expert
+- **Product & UX**: `user|ui|ux|interface|design|product|feature|experience` → ui-designer, ux-expert, product-manager, product-owner
+- **Agile & Delivery**: `agile|sprint|scrum|team|collaboration|delivery` → scrum-master, product-owner
+- **Domain Expertise**: `domain|standard|compliance|expertise|regulation` → subject-matter-expert
 - **Auto-select**: 2-3 most relevant roles based on topic analysis
 
 ### Simplified Processing Standards

.claude/commands/workflow/brainstorm/auto-squeeze.md

@@ -61,16 +61,16 @@ 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, security-expert
+  → system-architect, data-architect, subject-matter-expert
 - **UI/UX keywords**: `user|ui|ux|interface|design|frontend|experience`
-  → ui-designer, user-researcher
+  → ui-designer, ux-expert
 - **Product/Business keywords**: `product|feature|business|workflow|process|customer`
-  → product-manager, business-analyst
-- **Security keywords**: `security|auth|permission|encryption|compliance`
-  → security-expert
-- **Innovation keywords**: `innovation|new|disrupt|transform|emerging`
-  → innovation-lead
-- **Default**: ui-designer (if no clear match)
+  → 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
@@ -91,14 +91,14 @@ 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:security-expert")`
-- `SlashCommand(command="/workflow:brainstorm:user-researcher")`
-- `SlashCommand(command="/workflow:brainstorm:product-manager")`
-- `SlashCommand(command="/workflow:brainstorm:business-analyst")`
 - `SlashCommand(command="/workflow:brainstorm:data-architect")`
-- `SlashCommand(command="/workflow:brainstorm:innovation-lead")`
-- `SlashCommand(command="/workflow:brainstorm:feature-planner")`
+- `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
@@ -202,8 +202,8 @@ Return summary to user
 **Keywords detected**: user, interface, design
 **Selected roles**:
 - ui-designer (primary: UI/UX match)
-- user-researcher (secondary: user experience)
-- security-expert (complementary: auth security)
+- ux-expert (secondary: user experience)
+- subject-matter-expert (complementary: auth standards)
 
 ### Example 2: Architecture Topic
 **Topic**: "Design scalable microservices architecture"
@@ -211,15 +211,15 @@ Return summary to user
 **Selected roles**:
 - system-architect (primary: architecture match)
 - data-architect (secondary: scalability/data)
-- security-expert (complementary: system security)
+- subject-matter-expert (complementary: domain expertise)
 
-### Example 3: Business Process Topic
-**Topic**: "Optimize customer onboarding workflow"
-**Keywords detected**: workflow, process, customer
+### Example 3: Agile Delivery Topic
+**Topic**: "Optimize team sprint planning and delivery process"
+**Keywords detected**: sprint, team, delivery, process
 **Selected roles**:
-- business-analyst (primary: process match)
-- product-manager (secondary: customer focus)
-- ui-designer (complementary: user experience)
+- scrum-master (primary: agile process match)
+- product-owner (secondary: backlog/delivery focus)
+- product-manager (complementary: product strategy)
 
 ## Error Handling
 

.claude/commands/workflow/brainstorm/innovation-lead.md

@@ -1,254 +0,0 @@
----
-name: innovation-lead
-description: Generate or update innovation-lead/analysis.md addressing topic-framework discussion points
-usage: /workflow:brainstorm:innovation-lead [topic]
-argument-hint: "optional topic - uses existing framework if available"
-examples:
-  - /workflow:brainstorm:innovation-lead
-  - /workflow:brainstorm:innovation-lead "AI integration opportunities"
-  - /workflow:brainstorm:innovation-lead "future technology trends"
-allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
----
-
-## 🚀 **Role Overview: Innovation Lead**
-
-### Role Definition
-Visionary technology strategist responsible for identifying emerging technology trends, evaluating disruptive innovation opportunities, and designing future-ready solutions that create competitive advantage and drive market transformation.
-
-### Core Responsibilities
-- **Trend Identification**: Identify and analyze emerging technology trends and market opportunities
-- **Innovation Strategy**: Develop innovation roadmaps and technology development strategies
-- **Technology Assessment**: Evaluate new technology application potential and feasibility
-- **Future Planning**: Design forward-looking product and service concepts
-
-### Focus Areas
-- **Emerging Technologies**: AI, blockchain, IoT, AR/VR, quantum computing, and other frontier technologies
-- **Market Trends**: Industry transformation, user behavior evolution, business model innovation
-- **Innovation Opportunities**: Disruptive innovation, blue ocean markets, technology convergence opportunities
-- **Future Vision**: Long-term technology roadmaps, proof of concepts, prototype development
-
-### Success Metrics
-- Innovation impact and market differentiation
-- Technology adoption rates and competitive advantage
-- Future readiness and strategic positioning
-- Breakthrough opportunity identification and validation
-
-## 🧠 **Analysis Framework**
-
-@~/.claude/workflows/brainstorming-principles.md
-
-### Key Analysis Questions
-
-**1. Emerging Trends and Technology Opportunities**
-- Which emerging technologies will have the greatest impact on our industry?
-- What is the technology maturity level and adoption timeline?
-- What new opportunities does technology convergence create?
-
-**2. Disruption Potential and Innovation Assessment**
-- What is the potential for disruptive innovation and its impact?
-- What innovation opportunities exist within current solutions?
-- What unmet market needs and demands exist?
-
-**3. Competitive Advantage and Market Analysis**
-- What are competitors' innovation strategies and directions?
-- What market gaps and blue ocean opportunities exist?
-- What technological barriers and first-mover advantages are available?
-
-**4. Implementation and Risk Assessment**
-- What is the feasibility and risk of technology implementation?
-- What are the investment requirements and expected returns?
-- What organizational innovation capabilities and adaptability are needed?
-
-## ⚡ **Two-Step Execution Flow**
-
-### ⚠️ Session Management - FIRST STEP
-Session detection and selection:
-```bash
-# Check for active sessions
-active_sessions=$(find .workflow -name ".active-*" 2>/dev/null)
-if [ multiple_sessions ]; then
-  prompt_user_to_select_session()
-else
-  use_existing_or_create_new()
-fi
-```
-
-### Step 1: Context Gathering Phase
-**Innovation Lead Perspective Questioning**
-
-Before agent assignment, gather comprehensive innovation lead context:
-
-#### 📋 Role-Specific Questions
-
-**1. Emerging Trends and Future Technologies**
-- What emerging technologies or trends do you think will be most relevant to this topic?
-- Are there any specific industries or markets you want to explore for innovation opportunities?
-- What time horizon are you considering (near-term, medium-term, long-term disruption)?
-- Are there any particular technology domains you want to focus on (AI, IoT, blockchain, etc.)?
-
-**2. Innovation Opportunities and Market Potential**
-- What current limitations or pain points could be addressed through innovation?
-- Are there any unmet market needs or underserved segments you're aware of?
-- What would disruptive success look like in this context?
-- Are there cross-industry innovations that could be applied to this domain?
-
-**3. Disruption Potential and Competitive Landscape**
-- Who are the current market leaders and what are their innovation strategies?
-- What startup activity or venture capital investment trends are you seeing?
-- Are there any potential platform shifts or ecosystem changes on the horizon?
-- What would make a solution truly differentiated in the marketplace?
-
-**4. Implementation and Strategic Considerations**
-- What organizational capabilities or partnerships would be needed for innovation?
-- Are there regulatory, technical, or market barriers to consider?
-- What level of risk tolerance exists for breakthrough vs. incremental innovation?
-- How important is first-mover advantage versus fast-follower strategies?
-
-#### Context Validation
-- **Minimum Response**: Each answer must be ≥50 characters
-- **Re-prompting**: Insufficient detail triggers follow-up questions
-- **Context Storage**: Save responses to `.brainstorming/innovation-lead-context.md`
-
-### Step 2: Agent Assignment with Flow Control
-**Dedicated Agent Execution**
-
-```bash
-Task(conceptual-planning-agent): "
-[FLOW_CONTROL]
-
-Execute dedicated innovation lead conceptual analysis for: {topic}
-
-ASSIGNED_ROLE: innovation-lead
-OUTPUT_LOCATION: .brainstorming/innovation-lead/
-USER_CONTEXT: {validated_responses_from_context_gathering}
-
-Flow Control Steps:
-[
-  {
-    \"step\": \"load_role_template\",
-    \"action\": \"Load innovation-lead planning template\",
-    \"command\": \"bash($(cat ~/.claude/workflows/cli-templates/planning-roles/innovation-lead.md))\",
-    \"output_to\": \"role_template\"
-  }
-]
-
-Conceptual Analysis Requirements:
-- Apply innovation lead perspective to topic analysis
-- Focus on emerging trends, disruption potential, competitive advantage, and future opportunities
-- Use loaded role template framework for analysis structure
-- Generate role-specific deliverables in designated output location
-- Address all user context from questioning phase
-
-Deliverables:
-- analysis.md: Main innovation lead analysis
-- recommendations.md: Innovation lead recommendations
-- deliverables/: Innovation lead-specific outputs as defined in role template
-
-Embody innovation lead role expertise for comprehensive conceptual planning."
-```
-
-### Progress Tracking
-TodoWrite tracking for two-step process:
-```json
-[
-  {"content": "Gather innovation lead context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
-  {"content": "Validate context responses and save to innovation-lead-context.md", "status": "pending", "activeForm": "Validating context"},
-  {"content": "Load innovation-lead planning template via flow control", "status": "pending", "activeForm": "Loading template"},
-  {"content": "Execute dedicated conceptual-planning-agent for innovation-lead role", "status": "pending", "activeForm": "Executing agent"}
-]
-```
-
-## 📋 **TodoWrite Integration**
-
-### Workflow Progress Tracking
-```javascript
-TodoWrite({
-  todos: [
-    {
-      content: "Detect active session and locate topic framework",
-      status: "in_progress",
-      activeForm: "Detecting session and framework"
-    },
-    {
-      content: "Load topic-framework.md and session metadata for context",
-      status: "pending",
-      activeForm: "Loading framework and session context"
-    },
-    {
-      content: "Execute innovation-lead analysis using conceptual-planning-agent with FLOW_CONTROL",
-      status: "pending",
-      activeForm: "Executing innovation-lead framework analysis"
-    },
-    {
-      content: "Generate analysis.md addressing all framework discussion points",
-      status: "pending",
-      activeForm: "Generating structured innovation-lead analysis"
-    },
-    {
-      content: "Update session.json with innovation-lead completion status",
-      status: "pending",
-      activeForm: "Updating session metadata"
-    }
-  ]
-});
-```
-
-## 📊 **Output Structure**
-
-### Framework-Based Analysis
-```
-.workflow/WFS-{session}/.brainstorming/innovation-lead/
-└── analysis.md    # Structured analysis addressing topic-framework.md discussion points
-```
-
-### Analysis Document Structure
-```markdown
-# Innovation Lead Analysis: [Topic from Framework]
-
-## Framework Reference
-**Topic Framework**: @../topic-framework.md
-**Role Focus**: Innovation and Emerging Technology perspective
-
-## Discussion Points Analysis
-[Address each point from topic-framework.md with innovation expertise]
-
-### Core Requirements (from framework)
-[Innovation perspective on emerging technology requirements]
-
-### Technical Considerations (from framework)
-[Future technology and breakthrough considerations]
-
-### User Experience Factors (from framework)
-[Future user behavior and interaction trends]
-
-### Implementation Challenges (from framework)
-[Innovation implementation and market adoption considerations]
-
-### Success Metrics (from framework)
-[Innovation success metrics and breakthrough criteria]
-
-## Innovation Specific Recommendations
-[Role-specific innovation opportunities and breakthrough concepts]
-
----
-*Generated by innovation-lead analysis addressing structured framework*
-```
-
-## 🔄 **Session Integration**
-
-### Completion Status Update
-```json
-{
-  "innovation_lead": {
-    "status": "completed",
-    "framework_addressed": true,
-    "output_location": ".workflow/WFS-{session}/.brainstorming/innovation-lead/analysis.md",
-    "framework_reference": "@../topic-framework.md"
-  }
-}
-```
-
-### Integration Points
-- **Framework Reference**: @../topic-framework.md for structured discussion points
-- **Cross-Role Synthesis**: Innovation insights available for synthesis-report.md integration
-- **Agent Autonomy**: Independent execution with framework guidance

.claude/commands/workflow/brainstorm/product-owner.md

@@ -1,31 +1,31 @@
 ---
-name: business-analyst
-description: Generate or update business-analyst/analysis.md addressing topic-framework discussion points
-usage: /workflow:brainstorm:business-analyst [topic]
+name: product-owner
+description: Generate or update product-owner/analysis.md addressing topic-framework discussion points
+usage: /workflow:brainstorm:product-owner [topic]
 argument-hint: "optional topic - uses existing framework if available"
 examples:
-  - /workflow:brainstorm:business-analyst
-  - /workflow:brainstorm:business-analyst "workflow automation opportunities"
-  - /workflow:brainstorm:business-analyst "business process optimization"
+  - /workflow:brainstorm:product-owner
+  - /workflow:brainstorm:product-owner "user authentication redesign"
+  - /workflow:brainstorm:product-owner "mobile app performance optimization"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---
 
-## 📊 **Business Analyst Analysis Generator**
+## 🎯 **Product Owner Analysis Generator**
 
 ### Purpose
-**Specialized command for generating business-analyst/analysis.md** that addresses topic-framework.md discussion points from business analysis perspective. Creates or updates role-specific analysis with framework references.
+**Specialized command for generating product-owner/analysis.md** that addresses topic-framework.md discussion points from product backlog and feature prioritization perspective. Creates or updates role-specific analysis with framework references.
 
 ### Core Function
 - **Framework-based Analysis**: Address each discussion point in topic-framework.md
-- **Business Analysis Focus**: Process optimization, requirements analysis, and business efficiency perspective
+- **Product Backlog Focus**: Feature prioritization, user stories, and acceptance criteria
 - **Update Mechanism**: Create new or update existing analysis.md
 - **Agent Delegation**: Use conceptual-planning-agent for analysis generation
 
 ### Analysis Scope
-- **Process Analysis**: Analyze existing business processes for efficiency and improvement opportunities
-- **Requirements Analysis**: Identify and define business requirements and functional specifications
-- **Value Analysis**: Assess cost-benefit and ROI of business initiatives
-- **Change Management**: Plan organizational change and process transformation
+- **Backlog Management**: User story creation, refinement, and prioritization
+- **Stakeholder Alignment**: Requirements gathering, value definition, and expectation management
+- **Feature Prioritization**: ROI analysis, MoSCoW method, and value-driven delivery
+- **Acceptance Criteria**: Definition of Done, acceptance testing, and quality standards
 
 ## ⚙️ **Execution Protocol**
 
@@ -68,11 +68,11 @@ ELSE:
 Task(conceptual-planning-agent): "
 [FLOW_CONTROL]
 
-Execute business-analyst analysis for existing topic framework
+Execute product-owner analysis for existing topic framework
 
 ## Context Loading
-ASSIGNED_ROLE: business-analyst
-OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/business-analyst/
+ASSIGNED_ROLE: product-owner
+OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/product-owner/
 ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
 
 ## Flow Control Steps
@@ -82,8 +82,8 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
    - Output: topic_framework_content
 
 2. **load_role_template**
-   - Action: Load business-analyst planning template
-   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/business-analyst.md))
+   - Action: Load product-owner planning template
+   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/product-owner.md))
    - Output: role_template_guidelines
 
 3. **load_session_metadata**
@@ -92,19 +92,19 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
    - Output: session_context
 
 ## Analysis Requirements
-**Framework Reference**: Address all discussion points in topic-framework.md from business analysis perspective
-**Role Focus**: Process optimization, requirements analysis, business efficiency
+**Framework Reference**: Address all discussion points in topic-framework.md from product backlog and feature prioritization perspective
+**Role Focus**: Backlog management, stakeholder alignment, feature prioritization, acceptance criteria
 **Structured Approach**: Create analysis.md addressing framework discussion points
 **Template Integration**: Apply role template guidelines within framework structure
 
 ## Expected Deliverables
-1. **analysis.md**: Comprehensive business analysis addressing all framework discussion points
+1. **analysis.md**: Comprehensive product ownership analysis addressing all framework discussion points
 2. **Framework Reference**: Include @../topic-framework.md reference in analysis
 
 ## Completion Criteria
-- Address each discussion point from topic-framework.md with business analysis expertise
-- Provide process optimization recommendations and requirements specifications
-- Include cost-benefit analysis and change management considerations
+- Address each discussion point from topic-framework.md with product ownership expertise
+- Provide actionable user stories and acceptance criteria definitions
+- Include feature prioritization and stakeholder alignment strategies
 - Reference framework document using @ notation for integration
 "
 ```
@@ -126,17 +126,17 @@ TodoWrite({
       activeForm: "Loading framework and session context"
     },
     {
-      content: "Execute business-analyst analysis using conceptual-planning-agent with FLOW_CONTROL",
+      content: "Execute product-owner analysis using conceptual-planning-agent with FLOW_CONTROL",
       status: "pending",
-      activeForm: "Executing business-analyst framework analysis"
+      activeForm: "Executing product-owner framework analysis"
     },
     {
       content: "Generate analysis.md addressing all framework discussion points",
       status: "pending",
-      activeForm: "Generating structured business-analyst analysis"
+      activeForm: "Generating structured product-owner analysis"
     },
     {
-      content: "Update session.json with business-analyst completion status",
+      content: "Update session.json with product-owner completion status",
       status: "pending",
       activeForm: "Updating session metadata"
     }
@@ -148,41 +148,41 @@ TodoWrite({
 
 ### Framework-Based Analysis
 ```
-.workflow/WFS-{session}/.brainstorming/business-analyst/
+.workflow/WFS-{session}/.brainstorming/product-owner/
 └── analysis.md    # Structured analysis addressing topic-framework.md discussion points
 ```
 
 ### Analysis Document Structure
 ```markdown
-# Business Analyst Analysis: [Topic from Framework]
+# Product Owner Analysis: [Topic from Framework]
 
 ## Framework Reference
 **Topic Framework**: @../topic-framework.md
-**Role Focus**: Business Analysis perspective
+**Role Focus**: Product Backlog & Feature Prioritization perspective
 
 ## Discussion Points Analysis
-[Address each point from topic-framework.md with business analysis expertise]
+[Address each point from topic-framework.md with product ownership expertise]
 
 ### Core Requirements (from framework)
-[Business analysis perspective on requirements]
+[User story formulation and backlog refinement perspective]
 
 ### Technical Considerations (from framework)
-[Business process and workflow considerations]
+[Technical feasibility and implementation sequencing considerations]
 
 ### User Experience Factors (from framework)
-[Business user experience and stakeholder considerations]
+[User value definition and acceptance criteria analysis]
 
 ### Implementation Challenges (from framework)
-[Change management and process transformation challenges]
+[Sprint planning, dependency management, and delivery strategies]
 
 ### Success Metrics (from framework)
-[Business success metrics and performance indicators]
+[Feature adoption, value delivery metrics, and stakeholder satisfaction indicators]
 
-## Business Analysis Specific Recommendations
-[Role-specific business process recommendations and solutions]
+## Product Owner Specific Recommendations
+[Role-specific backlog management and feature prioritization strategies]
 
 ---
-*Generated by business-analyst analysis addressing structured framework*
+*Generated by product-owner analysis addressing structured framework*
 ```
 
 ## 🔄 **Session Integration**
@@ -190,10 +190,10 @@ TodoWrite({
 ### Completion Status Update
 ```json
 {
-  "business_analyst": {
+  "product_owner": {
     "status": "completed",
     "framework_addressed": true,
-    "output_location": ".workflow/WFS-{session}/.brainstorming/business-analyst/analysis.md",
+    "output_location": ".workflow/WFS-{session}/.brainstorming/product-owner/analysis.md",
     "framework_reference": "@../topic-framework.md"
   }
 }
@@ -201,5 +201,5 @@ TodoWrite({
 
 ### Integration Points
 - **Framework Reference**: @../topic-framework.md for structured discussion points
-- **Cross-Role Synthesis**: Business analysis insights available for synthesis-report.md integration
-- **Agent Autonomy**: Independent execution with framework guidance
+- **Cross-Role Synthesis**: Product ownership insights available for synthesis-report.md integration
+- **Agent Autonomy**: Independent execution with framework guidance

.claude/commands/workflow/brainstorm/scrum-master.md

@@ -1,31 +1,31 @@
 ---
-name: security-expert
-description: Generate or update security-expert/analysis.md addressing topic-framework discussion points
-usage: /workflow:brainstorm:security-expert [topic]
+name: scrum-master
+description: Generate or update scrum-master/analysis.md addressing topic-framework discussion points
+usage: /workflow:brainstorm:scrum-master [topic]
 argument-hint: "optional topic - uses existing framework if available"
 examples:
-  - /workflow:brainstorm:security-expert
-  - /workflow:brainstorm:security-expert "user authentication security review"
-  - /workflow:brainstorm:security-expert "API security architecture"
+  - /workflow:brainstorm:scrum-master
+  - /workflow:brainstorm:scrum-master "user authentication redesign"
+  - /workflow:brainstorm:scrum-master "mobile app performance optimization"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---
 
-## 🔒 **Security Expert Analysis Generator**
+## 🎯 **Scrum Master Analysis Generator**
 
 ### Purpose
-**Specialized command for generating security-expert/analysis.md** that addresses topic-framework.md discussion points from cybersecurity perspective. Creates or updates role-specific analysis with framework references.
+**Specialized command for generating scrum-master/analysis.md** that addresses topic-framework.md discussion points from agile process and team collaboration perspective. Creates or updates role-specific analysis with framework references.
 
 ### Core Function
 - **Framework-based Analysis**: Address each discussion point in topic-framework.md
-- **Cybersecurity Focus**: Threat modeling, security architecture, and risk management
+- **Agile Process Focus**: Sprint planning, team dynamics, and delivery optimization
 - **Update Mechanism**: Create new or update existing analysis.md
 - **Agent Delegation**: Use conceptual-planning-agent for analysis generation
 
 ### Analysis Scope
-- **Threat Modeling**: Attack vectors, threat actors, and vulnerability assessment
-- **Security Architecture**: Controls, defensive measures, and compliance
-- **Risk Management**: Risk assessment, mitigation, and security policies
-- **Implementation Security**: Integration, monitoring, and incident response
+- **Sprint Planning**: Task breakdown, estimation, and iteration planning
+- **Team Collaboration**: Communication patterns, impediment removal, and facilitation
+- **Process Optimization**: Agile ceremonies, retrospectives, and continuous improvement
+- **Delivery Management**: Velocity tracking, burndown analysis, and release planning
 
 ## ⚙️ **Execution Protocol**
 
@@ -68,11 +68,11 @@ ELSE:
 Task(conceptual-planning-agent): "
 [FLOW_CONTROL]
 
-Execute security-expert analysis for existing topic framework
+Execute scrum-master analysis for existing topic framework
 
 ## Context Loading
-ASSIGNED_ROLE: security-expert
-OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/security-expert/
+ASSIGNED_ROLE: scrum-master
+OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/scrum-master/
 ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
 
 ## Flow Control Steps
@@ -82,8 +82,8 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
    - Output: topic_framework_content
 
 2. **load_role_template**
-   - Action: Load security-expert planning template
-   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/security-expert.md))
+   - Action: Load scrum-master planning template
+   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/scrum-master.md))
    - Output: role_template_guidelines
 
 3. **load_session_metadata**
@@ -92,19 +92,19 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
    - Output: session_context
 
 ## Analysis Requirements
-**Framework Reference**: Address all discussion points in topic-framework.md from cybersecurity perspective
-**Role Focus**: Threat modeling, security architecture, risk management, compliance
+**Framework Reference**: Address all discussion points in topic-framework.md from agile process and team collaboration perspective
+**Role Focus**: Sprint planning, team dynamics, process optimization, delivery management
 **Structured Approach**: Create analysis.md addressing framework discussion points
 **Template Integration**: Apply role template guidelines within framework structure
 
 ## Expected Deliverables
-1. **analysis.md**: Comprehensive security analysis addressing all framework discussion points
+1. **analysis.md**: Comprehensive agile process analysis addressing all framework discussion points
 2. **Framework Reference**: Include @../topic-framework.md reference in analysis
 
 ## Completion Criteria
-- Address each discussion point from topic-framework.md with cybersecurity expertise
-- Provide actionable security controls and threat mitigation strategies
-- Include compliance requirements and risk assessment insights
+- Address each discussion point from topic-framework.md with scrum mastery expertise
+- Provide actionable sprint planning and team facilitation strategies
+- Include process optimization and impediment removal insights
 - Reference framework document using @ notation for integration
 "
 ```
@@ -126,17 +126,17 @@ TodoWrite({
       activeForm: "Loading framework and session context"
     },
     {
-      content: "Execute security-expert analysis using conceptual-planning-agent with FLOW_CONTROL",
+      content: "Execute scrum-master analysis using conceptual-planning-agent with FLOW_CONTROL",
       status: "pending",
-      activeForm: "Executing security-expert framework analysis"
+      activeForm: "Executing scrum-master framework analysis"
     },
     {
       content: "Generate analysis.md addressing all framework discussion points",
       status: "pending",
-      activeForm: "Generating structured security-expert analysis"
+      activeForm: "Generating structured scrum-master analysis"
     },
     {
-      content: "Update session.json with security-expert completion status",
+      content: "Update session.json with scrum-master completion status",
       status: "pending",
       activeForm: "Updating session metadata"
     }
@@ -148,41 +148,41 @@ TodoWrite({
 
 ### Framework-Based Analysis
 ```
-.workflow/WFS-{session}/.brainstorming/security-expert/
+.workflow/WFS-{session}/.brainstorming/scrum-master/
 └── analysis.md    # Structured analysis addressing topic-framework.md discussion points
 ```
 
 ### Analysis Document Structure
 ```markdown
-# Security Expert Analysis: [Topic from Framework]
+# Scrum Master Analysis: [Topic from Framework]
 
 ## Framework Reference
 **Topic Framework**: @../topic-framework.md
-**Role Focus**: Cybersecurity perspective
+**Role Focus**: Agile Process & Team Collaboration perspective
 
 ## Discussion Points Analysis
-[Address each point from topic-framework.md with cybersecurity expertise]
+[Address each point from topic-framework.md with scrum mastery expertise]
 
 ### Core Requirements (from framework)
-[Security perspective on threat modeling and protection requirements]
+[Sprint planning and iteration breakdown perspective]
 
 ### Technical Considerations (from framework)
-[Security architecture and technical control considerations]
+[Technical debt management and process considerations]
 
 ### User Experience Factors (from framework)
-[Security usability and user protection considerations]
+[User story refinement and acceptance criteria analysis]
 
 ### Implementation Challenges (from framework)
-[Security implementation and compliance considerations]
+[Impediment identification and removal strategies]
 
 ### Success Metrics (from framework)
-[Security success metrics and risk management criteria]
+[Velocity tracking, burndown metrics, and team performance indicators]
 
-## Cybersecurity Specific Recommendations
-[Role-specific security controls and threat mitigation strategies]
+## Scrum Master Specific Recommendations
+[Role-specific agile process optimization and team facilitation strategies]
 
 ---
-*Generated by security-expert analysis addressing structured framework*
+*Generated by scrum-master analysis addressing structured framework*
 ```
 
 ## 🔄 **Session Integration**
@@ -190,10 +190,10 @@ TodoWrite({
 ### Completion Status Update
 ```json
 {
-  "security_expert": {
+  "scrum_master": {
     "status": "completed",
     "framework_addressed": true,
-    "output_location": ".workflow/WFS-{session}/.brainstorming/security-expert/analysis.md",
+    "output_location": ".workflow/WFS-{session}/.brainstorming/scrum-master/analysis.md",
     "framework_reference": "@../topic-framework.md"
   }
 }
@@ -201,5 +201,5 @@ TodoWrite({
 
 ### Integration Points
 - **Framework Reference**: @../topic-framework.md for structured discussion points
-- **Cross-Role Synthesis**: Security insights available for synthesis-report.md integration
-- **Agent Autonomy**: Independent execution with framework guidance
+- **Cross-Role Synthesis**: Agile process insights available for synthesis-report.md integration
+- **Agent Autonomy**: Independent execution with framework guidance

.claude/commands/workflow/brainstorm/subject-matter-expert.md

@@ -0,0 +1,205 @@
+---
+name: subject-matter-expert
+description: Generate or update subject-matter-expert/analysis.md addressing topic-framework discussion points
+usage: /workflow:brainstorm:subject-matter-expert [topic]
+argument-hint: "optional topic - uses existing framework if available"
+examples:
+  - /workflow:brainstorm:subject-matter-expert
+  - /workflow:brainstorm:subject-matter-expert "user authentication redesign"
+  - /workflow:brainstorm:subject-matter-expert "mobile app performance optimization"
+allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
+---
+
+## 🎯 **Subject Matter Expert Analysis Generator**
+
+### Purpose
+**Specialized command for generating subject-matter-expert/analysis.md** that addresses topic-framework.md discussion points from domain knowledge and technical expertise perspective. Creates or updates role-specific analysis with framework references.
+
+### Core Function
+- **Framework-based Analysis**: Address each discussion point in topic-framework.md
+- **Domain Expertise Focus**: Deep technical knowledge, industry standards, and best practices
+- **Update Mechanism**: Create new or update existing analysis.md
+- **Agent Delegation**: Use conceptual-planning-agent for analysis generation
+
+### Analysis Scope
+- **Domain Knowledge**: Industry-specific expertise, regulatory requirements, and compliance
+- **Technical Standards**: Best practices, design patterns, and architectural guidelines
+- **Risk Assessment**: Technical debt, scalability concerns, and maintenance implications
+- **Knowledge Transfer**: Documentation strategies, training requirements, and expertise sharing
+
+## ⚙️ **Execution Protocol**
+
+### Phase 1: Session & Framework Detection
+```bash
+# Check active session and framework
+CHECK: .workflow/.active-* marker files
+IF active_session EXISTS:
+    session_id = get_active_session()
+    brainstorm_dir = .workflow/WFS-{session}/.brainstorming/
+
+    CHECK: brainstorm_dir/topic-framework.md
+    IF EXISTS:
+        framework_mode = true
+        load_framework = true
+    ELSE:
+        IF topic_provided:
+            framework_mode = false  # Create analysis without framework
+        ELSE:
+            ERROR: "No framework found and no topic provided"
+```
+
+### Phase 2: Analysis Mode Detection
+```bash
+# Determine execution mode
+IF framework_mode == true:
+    mode = "framework_based_analysis"
+    topic_ref = load_framework_topic()
+    discussion_points = extract_framework_points()
+ELSE:
+    mode = "standalone_analysis"
+    topic_ref = provided_topic
+    discussion_points = generate_basic_structure()
+```
+
+### Phase 3: Agent Execution with Flow Control
+**Framework-Based Analysis Generation**
+
+```bash
+Task(conceptual-planning-agent): "
+[FLOW_CONTROL]
+
+Execute subject-matter-expert analysis for existing topic framework
+
+## Context Loading
+ASSIGNED_ROLE: subject-matter-expert
+OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/subject-matter-expert/
+ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
+
+## Flow Control Steps
+1. **load_topic_framework**
+   - Action: Load structured topic discussion framework
+   - Command: Read(.workflow/WFS-{session}/.brainstorming/topic-framework.md)
+   - Output: topic_framework_content
+
+2. **load_role_template**
+   - Action: Load subject-matter-expert planning template
+   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/subject-matter-expert.md))
+   - Output: role_template_guidelines
+
+3. **load_session_metadata**
+   - Action: Load session metadata and existing context
+   - Command: Read(.workflow/WFS-{session}/.brainstorming/session.json)
+   - Output: session_context
+
+## Analysis Requirements
+**Framework Reference**: Address all discussion points in topic-framework.md from domain expertise and technical standards perspective
+**Role Focus**: Domain knowledge, technical standards, risk assessment, knowledge transfer
+**Structured Approach**: Create analysis.md addressing framework discussion points
+**Template Integration**: Apply role template guidelines within framework structure
+
+## Expected Deliverables
+1. **analysis.md**: Comprehensive domain expertise analysis addressing all framework discussion points
+2. **Framework Reference**: Include @../topic-framework.md reference in analysis
+
+## Completion Criteria
+- Address each discussion point from topic-framework.md with subject matter expertise
+- Provide actionable technical standards and best practices recommendations
+- Include risk assessment and compliance considerations
+- Reference framework document using @ notation for integration
+"
+```
+
+## 📋 **TodoWrite Integration**
+
+### Workflow Progress Tracking
+```javascript
+TodoWrite({
+  todos: [
+    {
+      content: "Detect active session and locate topic framework",
+      status: "in_progress",
+      activeForm: "Detecting session and framework"
+    },
+    {
+      content: "Load topic-framework.md and session metadata for context",
+      status: "pending",
+      activeForm: "Loading framework and session context"
+    },
+    {
+      content: "Execute subject-matter-expert analysis using conceptual-planning-agent with FLOW_CONTROL",
+      status: "pending",
+      activeForm: "Executing subject-matter-expert framework analysis"
+    },
+    {
+      content: "Generate analysis.md addressing all framework discussion points",
+      status: "pending",
+      activeForm: "Generating structured subject-matter-expert analysis"
+    },
+    {
+      content: "Update session.json with subject-matter-expert completion status",
+      status: "pending",
+      activeForm: "Updating session metadata"
+    }
+  ]
+});
+```
+
+## 📊 **Output Structure**
+
+### Framework-Based Analysis
+```
+.workflow/WFS-{session}/.brainstorming/subject-matter-expert/
+└── analysis.md    # Structured analysis addressing topic-framework.md discussion points
+```
+
+### Analysis Document Structure
+```markdown
+# Subject Matter Expert Analysis: [Topic from Framework]
+
+## Framework Reference
+**Topic Framework**: @../topic-framework.md
+**Role Focus**: Domain Expertise & Technical Standards perspective
+
+## Discussion Points Analysis
+[Address each point from topic-framework.md with subject matter expertise]
+
+### Core Requirements (from framework)
+[Domain-specific requirements and industry standards perspective]
+
+### Technical Considerations (from framework)
+[Deep technical analysis, architectural patterns, and best practices]
+
+### User Experience Factors (from framework)
+[Domain-specific usability standards and industry conventions]
+
+### Implementation Challenges (from framework)
+[Technical risks, scalability concerns, and maintenance implications]
+
+### Success Metrics (from framework)
+[Domain-specific KPIs, compliance metrics, and quality standards]
+
+## Subject Matter Expert Specific Recommendations
+[Role-specific technical expertise and industry best practices]
+
+---
+*Generated by subject-matter-expert analysis addressing structured framework*
+```
+
+## 🔄 **Session Integration**
+
+### Completion Status Update
+```json
+{
+  "subject_matter_expert": {
+    "status": "completed",
+    "framework_addressed": true,
+    "output_location": ".workflow/WFS-{session}/.brainstorming/subject-matter-expert/analysis.md",
+    "framework_reference": "@../topic-framework.md"
+  }
+}
+```
+
+### Integration Points
+- **Framework Reference**: @../topic-framework.md for structured discussion points
+- **Cross-Role Synthesis**: Domain expertise insights available for synthesis-report.md integration
+- **Agent Autonomy**: Independent execution with framework guidance

.claude/commands/workflow/brainstorm/synthesis.md

@@ -184,7 +184,7 @@ Strategic overview with key insights, breakthrough opportunities, and implementa
 
 ## Design Specifications
 ### UI/UX Guidelines
-**Consolidated from**: @ui-designer/analysis.md, @user-researcher/analysis.md
+**Consolidated from**: @ui-designer/analysis.md, @ux-expert/analysis.md
 - Component specifications and interaction patterns
 - Visual design system and accessibility requirements
 - User flow and interface specifications
@@ -195,11 +195,11 @@ Strategic overview with key insights, breakthrough opportunities, and implementa
 - Data flow and storage strategy
 - Technology stack decisions
 
-### Security Framework
-**Consolidated from**: @security-expert/analysis.md
-- Authentication and authorization patterns
-- Data protection and compliance requirements
-- Security monitoring and audit strategy
+### Domain Expertise & Standards
+**Consolidated from**: @subject-matter-expert/analysis.md
+- Industry standards and best practices
+- Compliance requirements and regulations
+- Technical quality and domain-specific patterns
 
 ## Implementation Roadmap
 ### Development Phases
@@ -242,7 +242,7 @@ Upon completion, update `workflow-session.json`:
       "status": "completed",
       "synthesis_completed": true,
       "completed_at": "timestamp",
-      "participating_roles": ["product-manager", "system-architect", "ui-designer", "security-expert", "data-architect", ...],
+      "participating_roles": ["product-manager", "product-owner", "scrum-master", "system-architect", "ui-designer", "ux-expert", "data-architect", "subject-matter-expert", "test-strategist"],
       "consolidated_output": {
         "synthesis_specification": ".workflow/WFS-{topic}/.brainstorming/synthesis-specification.md"
       },

.claude/commands/workflow/brainstorm/user-researcher.md

@@ -1,267 +0,0 @@
----
-name: user-researcher
-description: User researcher perspective brainstorming for user behavior analysis and research insights
-usage: /workflow:brainstorm:user-researcher <topic>
-argument-hint: "topic or challenge to analyze from user research perspective"
-examples:
-  - /workflow:brainstorm:user-researcher "user onboarding experience"
-  - /workflow:brainstorm:user-researcher "mobile app usability issues"
-  - /workflow:brainstorm:user-researcher "feature adoption analysis"
-allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
----
-
-## 🔍 **Role Overview: User Researcher**
-
-### Role Definition
-User experience research specialist responsible for understanding user behavior, identifying needs and pain points, and transforming research insights into actionable product improvements that enhance user satisfaction and engagement.
-
-### Core Responsibilities
-- **User Behavior Research**: Deep analysis of user behavior patterns and motivations
-- **User Needs Discovery**: Research to discover unmet user needs and requirements
-- **Usability Assessment**: Evaluate product usability and user experience issues
-- **User Insights Generation**: Transform research findings into actionable product insights
-
-### Focus Areas
-- **User Behavior**: Usage patterns, decision paths, task completion methods
-- **User Needs**: Explicit needs, implicit needs, emotional requirements
-- **User Experience**: Pain points, satisfaction levels, emotional responses, expectations
-- **Market Segmentation**: User personas, demographic segments, usage scenarios
-
-### Success Metrics
-- User satisfaction and engagement scores
-- Task success rates and completion times
-- Quality and actionability of research insights
-- Impact of research on product decisions
-
-## 🧠 **分析框架**
-
-@~/.claude/workflows/brainstorming-principles.md
-
-### Key Analysis Questions
-
-**1. User Understanding and Insights**
-- What are the real needs and pain points of target users?
-- What are the user behavior patterns and usage scenarios?
-- What are the differentiated needs of various user groups?
-
-**2. User Experience Analysis**
-- What are the main issues with the current user experience?
-- What obstacles and friction points exist in user task completion?
-- What gaps exist between user satisfaction and expectations?
-
-**3. Research Methods and Validation**
-- Which research methods are most suitable for the current problem?
-- How can hypotheses and design decisions be validated?
-- How can continuous user feedback be collected?
-
-**4. Insights Translation and Application**
-- How can research findings be translated into product improvements?
-- How can product decisions and design be influenced?
-- How can a user-centered culture be established?
-
-## ⚡ **Two-Step Execution Flow**
-
-### ⚠️ Session Management - FIRST STEP
-Session detection and selection:
-```bash
-# Check for active sessions
-active_sessions=$(find .workflow -name ".active-*" 2>/dev/null)
-if [ multiple_sessions ]; then
-  prompt_user_to_select_session()
-else
-  use_existing_or_create_new()
-fi
-```
-
-### Step 1: Context Gathering Phase
-**User Researcher Perspective Questioning**
-
-Before agent assignment, gather comprehensive user researcher context:
-
-#### 📋 Role-Specific Questions
-
-**1. User Behavior Patterns and Insights**
-- Who are the primary users and what are their key characteristics?
-- What user behaviors, patterns, or pain points have you observed?
-- Are there specific user segments or personas you're particularly interested in?
-- What user feedback or data do you already have available?
-
-**2. Research Focus and Pain Points**
-- What specific user experience problems or questions need to be addressed?
-- Are there particular user tasks, workflows, or touchpoints to focus on?
-- What assumptions about users need to be validated or challenged?
-- What gaps exist in your current understanding of user needs?
-
-**3. Research Context and Constraints**
-- What research has been done previously and what were the key findings?
-- Are there specific research methods you prefer or want to avoid?
-- What timeline and resources are available for user research?
-- Who are the key stakeholders that need to understand user insights?
-
-**4. User Testing Strategy and Goals**
-- What specific user experience improvements are you hoping to achieve?
-- How do you currently measure user satisfaction or success?
-- Are there competitive products or experiences you want to benchmark against?
-- What would successful user research outcomes look like for this project?
-
-#### Context Validation
-- **Minimum Response**: Each answer must be ≥50 characters
-- **Re-prompting**: Insufficient detail triggers follow-up questions
-- **Context Storage**: Save responses to `.brainstorming/user-researcher-context.md`
-
-### Step 2: Agent Assignment with Flow Control
-**Dedicated Agent Execution**
-
-```bash
-Task(conceptual-planning-agent): "
-[FLOW_CONTROL]
-
-Execute dedicated user researcher conceptual analysis for: {topic}
-
-ASSIGNED_ROLE: user-researcher
-OUTPUT_LOCATION: .brainstorming/user-researcher/
-USER_CONTEXT: {validated_responses_from_context_gathering}
-
-Flow Control Steps:
-[
-  {
-    \"step\": \"load_role_template\",
-    \"action\": \"Load user-researcher planning template\",
-    \"command\": \"bash($(cat ~/.claude/workflows/cli-templates/planning-roles/user-researcher.md))\",
-    \"output_to\": \"role_template\"
-  }
-]
-
-Conceptual Analysis Requirements:
-- Apply user researcher perspective to topic analysis
-- Focus on user behavior patterns, pain points, research insights, and user testing strategy
-- Use loaded role template framework for analysis structure
-- Generate role-specific deliverables in designated output location
-- Address all user context from questioning phase
-
-Deliverables:
-- analysis.md: Main user researcher analysis
-- recommendations.md: User researcher recommendations
-- deliverables/: User researcher-specific outputs as defined in role template
-
-Embody user researcher role expertise for comprehensive conceptual planning."
-```
-
-### Progress Tracking
-TodoWrite tracking for two-step process:
-```json
-[
-  {"content": "Gather user researcher context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
-  {"content": "Validate context responses and save to user-researcher-context.md", "status": "pending", "activeForm": "Validating context"},
-  {"content": "Load user-researcher planning template via flow control", "status": "pending", "activeForm": "Loading template"},
-  {"content": "Execute dedicated conceptual-planning-agent for user-researcher role", "status": "pending", "activeForm": "Executing agent"}
-]
-```
-
-## 📊 **输出结构**
-
-### 保存位置
-```
-.workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
-├── analysis.md                     # 主要用户研究分析
-├── user-personas.md                # 详细用户画像和细分
-├── research-plan.md                # 方法论和研究方法
-└── insights-recommendations.md     # 关键发现和可执行建议
-```
-
-### 文档模板
-
-#### analysis.md 结构
-```markdown
-# User Researcher Analysis: {Topic}
-*Generated: {timestamp}*
-
-## Executive Summary
-[核心用户研究发现和建议概述]
-
-## Current User Landscape
-### User Base Overview
-### Behavioral Patterns
-### Usage Statistics and Trends
-### Satisfaction Metrics
-
-## User Needs Analysis
-### Primary User Needs
-### Unmet Needs and Gaps
-### Need Prioritization Matrix
-### Emotional and Functional Needs
-
-## User Experience Assessment
-### Current UX Strengths
-### Major Pain Points and Friction
-### Usability Issues Identified
-### Accessibility Gaps
-
-## User Behavior Insights
-### User Journey Mapping
-### Decision-Making Patterns
-### Task Completion Analysis
-### Behavioral Segments
-
-## Research Recommendations
-### Recommended Research Methods
-### Key Research Questions
-### Success Metrics and KPIs
-### Research Timeline and Resources
-
-## Actionable Insights
-### Immediate UX Improvements
-### Product Feature Recommendations
-### Long-term User Strategy
-### Success Measurement Plan
-```
-
-## 🔄 **会话集成**
-
-### 状态同步
-分析完成后，更新 `workflow-session.json`:
-```json
-{
-  "phases": {
-    "BRAINSTORM": {
-      "user_researcher": {
-        "status": "completed",
-        "completed_at": "timestamp",
-        "output_directory": ".workflow/WFS-{topic}/.brainstorming/user-researcher/",
-        "key_insights": ["user_behavior_pattern", "unmet_need", "usability_issue"]
-      }
-    }
-  }
-}
-```
-
-### 与其他角色的协作
-用户研究员视角为其他角色提供：
-- **用户需求和洞察** → Product Manager
-- **用户行为数据** → Data Architect
-- **用户体验要求** → UI Designer
-- **用户安全需求** → Security Expert
-- **功能使用场景** → Feature Planner
-
-## ✅ **质量标准**
-
-### 必须包含的研究元素
-- [ ] 详细的用户行为分析
-- [ ] 明确的用户需求识别
-- [ ] 全面的用户体验评估
-- [ ] 科学的研究方法设计
-- [ ] 可执行的改进建议
-
-### 用户研究原则检查
-- [ ] 以人为本：所有分析以用户为中心
-- [ ] 基于证据：结论有数据和研究支撑
-- [ ] 行为导向：关注实际行为而非声明意图
-- [ ] 情境考虑：分析使用场景和环境因素
-- [ ] 持续迭代：建立持续研究和改进机制
-
-### 洞察质量评估
-- [ ] 洞察的新颖性和深度
-- [ ] 建议的可操作性和具体性
-- [ ] 影响评估的准确性
-- [ ] 研究方法的科学性
-- [ ] 用户代表性的覆盖度

.claude/commands/workflow/brainstorm/ux-expert.md

@@ -1,31 +1,31 @@
 ---
-name: feature-planner
-description: Generate or update feature-planner/analysis.md addressing topic-framework discussion points
-usage: /workflow:brainstorm:feature-planner [topic]
+name: ux-expert
+description: Generate or update ux-expert/analysis.md addressing topic-framework discussion points
+usage: /workflow:brainstorm:ux-expert [topic]
 argument-hint: "optional topic - uses existing framework if available"
 examples:
-  - /workflow:brainstorm:feature-planner
-  - /workflow:brainstorm:feature-planner "user dashboard enhancement"
-  - /workflow:brainstorm:feature-planner "mobile app feature roadmap"
+  - /workflow:brainstorm:ux-expert
+  - /workflow:brainstorm:ux-expert "user authentication redesign"
+  - /workflow:brainstorm:ux-expert "mobile app performance optimization"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---
 
-## 🔧 **Feature Planner Analysis Generator**
+## 🎯 **UX Expert Analysis Generator**
 
 ### Purpose
-**Specialized command for generating feature-planner/analysis.md** that addresses topic-framework.md discussion points from feature development perspective. Creates or updates role-specific analysis with framework references.
+**Specialized command for generating ux-expert/analysis.md** that addresses topic-framework.md discussion points from user experience and interface design perspective. Creates or updates role-specific analysis with framework references.
 
 ### Core Function
 - **Framework-based Analysis**: Address each discussion point in topic-framework.md
-- **Feature Development Focus**: Feature specification, development planning, and delivery management
+- **UX Design Focus**: User interface, interaction patterns, and usability optimization
 - **Update Mechanism**: Create new or update existing analysis.md
 - **Agent Delegation**: Use conceptual-planning-agent for analysis generation
 
 ### Analysis Scope
-- **Feature Specification**: Transform requirements into detailed specifications
-- **Development Planning**: Sprint planning, milestones, and dependency management
-- **Quality Assurance**: Testing strategies and acceptance criteria
-- **Delivery Management**: Release planning and implementation timelines
+- **User Interface Design**: Visual hierarchy, layout patterns, and component design
+- **Interaction Patterns**: User flows, navigation, and microinteractions
+- **Usability Optimization**: Accessibility, cognitive load, and user testing strategies
+- **Design Systems**: Component libraries, design tokens, and consistency frameworks
 
 ## ⚙️ **Execution Protocol**
 
@@ -68,11 +68,11 @@ ELSE:
 Task(conceptual-planning-agent): "
 [FLOW_CONTROL]
 
-Execute feature-planner analysis for existing topic framework
+Execute ux-expert analysis for existing topic framework
 
 ## Context Loading
-ASSIGNED_ROLE: feature-planner
-OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/feature-planner/
+ASSIGNED_ROLE: ux-expert
+OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/ux-expert/
 ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
 
 ## Flow Control Steps
@@ -82,8 +82,8 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
    - Output: topic_framework_content
 
 2. **load_role_template**
-   - Action: Load feature-planner planning template
-   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/feature-planner.md))
+   - Action: Load ux-expert planning template
+   - Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/ux-expert.md))
    - Output: role_template_guidelines
 
 3. **load_session_metadata**
@@ -92,19 +92,19 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
    - Output: session_context
 
 ## Analysis Requirements
-**Framework Reference**: Address all discussion points in topic-framework.md from feature development perspective
-**Role Focus**: Feature specification, development planning, quality assurance, delivery management
+**Framework Reference**: Address all discussion points in topic-framework.md from user experience and interface design perspective
+**Role Focus**: UI design, interaction patterns, usability optimization, design systems
 **Structured Approach**: Create analysis.md addressing framework discussion points
 **Template Integration**: Apply role template guidelines within framework structure
 
 ## Expected Deliverables
-1. **analysis.md**: Comprehensive feature planning analysis addressing all framework discussion points
+1. **analysis.md**: Comprehensive UX design analysis addressing all framework discussion points
 2. **Framework Reference**: Include @../topic-framework.md reference in analysis
 
 ## Completion Criteria
-- Address each discussion point from topic-framework.md with feature development expertise
-- Provide actionable development plans and implementation strategies
-- Include quality assurance and testing considerations
+- Address each discussion point from topic-framework.md with UX design expertise
+- Provide actionable interface design and usability optimization strategies
+- Include accessibility considerations and interaction pattern recommendations
 - Reference framework document using @ notation for integration
 "
 ```
@@ -126,17 +126,17 @@ TodoWrite({
       activeForm: "Loading framework and session context"
     },
     {
-      content: "Execute feature-planner analysis using conceptual-planning-agent with FLOW_CONTROL",
+      content: "Execute ux-expert analysis using conceptual-planning-agent with FLOW_CONTROL",
       status: "pending",
-      activeForm: "Executing feature-planner framework analysis"
+      activeForm: "Executing ux-expert framework analysis"
     },
     {
       content: "Generate analysis.md addressing all framework discussion points",
       status: "pending",
-      activeForm: "Generating structured feature-planner analysis"
+      activeForm: "Generating structured ux-expert analysis"
     },
     {
-      content: "Update session.json with feature-planner completion status",
+      content: "Update session.json with ux-expert completion status",
       status: "pending",
       activeForm: "Updating session metadata"
     }
@@ -148,41 +148,41 @@ TodoWrite({
 
 ### Framework-Based Analysis
 ```
-.workflow/WFS-{session}/.brainstorming/feature-planner/
+.workflow/WFS-{session}/.brainstorming/ux-expert/
 └── analysis.md    # Structured analysis addressing topic-framework.md discussion points
 ```
 
 ### Analysis Document Structure
 ```markdown
-# Feature Planner Analysis: [Topic from Framework]
+# UX Expert Analysis: [Topic from Framework]
 
 ## Framework Reference
 **Topic Framework**: @../topic-framework.md
-**Role Focus**: Feature Development perspective
+**Role Focus**: User Experience & Interface Design perspective
 
 ## Discussion Points Analysis
-[Address each point from topic-framework.md with feature development expertise]
+[Address each point from topic-framework.md with UX design expertise]
 
 ### Core Requirements (from framework)
-[Feature development perspective on requirements]
+[User interface and interaction design requirements perspective]
 
 ### Technical Considerations (from framework)
-[Feature architecture and development considerations]
+[Design system implementation and technical feasibility considerations]
 
 ### User Experience Factors (from framework)
-[Feature usability and user story considerations]
+[Usability optimization, accessibility, and user-centered design analysis]
 
 ### Implementation Challenges (from framework)
-[Development complexity and delivery considerations]
+[Design implementation challenges and progressive enhancement strategies]
 
 ### Success Metrics (from framework)
-[Feature success metrics and acceptance criteria]
+[UX metrics including usability testing, user satisfaction, and design KPIs]
 
-## Feature Development Specific Recommendations
-[Role-specific feature planning recommendations and strategies]
+## UX Expert Specific Recommendations
+[Role-specific interface design patterns and usability optimization strategies]
 
 ---
-*Generated by feature-planner analysis addressing structured framework*
+*Generated by ux-expert analysis addressing structured framework*
 ```
 
 ## 🔄 **Session Integration**
@@ -190,10 +190,10 @@ TodoWrite({
 ### Completion Status Update
 ```json
 {
-  "feature_planner": {
+  "ux_expert": {
     "status": "completed",
     "framework_addressed": true,
-    "output_location": ".workflow/WFS-{session}/.brainstorming/feature-planner/analysis.md",
+    "output_location": ".workflow/WFS-{session}/.brainstorming/ux-expert/analysis.md",
     "framework_reference": "@../topic-framework.md"
   }
 }
@@ -201,5 +201,5 @@ TodoWrite({
 
 ### Integration Points
 - **Framework Reference**: @../topic-framework.md for structured discussion points
-- **Cross-Role Synthesis**: Feature development insights available for synthesis-report.md integration
-- **Agent Autonomy**: Independent execution with framework guidance
+- **Cross-Role Synthesis**: UX design insights available for synthesis-report.md integration
+- **Agent Autonomy**: Independent execution with framework guidance

.claude/commands/workflow/tools/task-generate.md

@@ -188,9 +188,12 @@ Generate task JSON files and IMPL_PLAN.md from analysis results with automatic a
 #### Artifact-Task Mapping
 - **synthesis-specification.md** → All tasks
 - **ui-designer/analysis.md** → UI/Frontend tasks
+- **ux-expert/analysis.md** → UX/Interaction tasks
 - **system-architect/analysis.md** → Architecture/Backend tasks
-- **security-expert/analysis.md** → Security tasks
+- **subject-matter-expert/analysis.md** → Domain/Standards tasks
 - **data-architect/analysis.md** → Data/API tasks
+- **scrum-master/analysis.md** → Sprint/Process tasks
+- **product-owner/analysis.md** → Backlog/Story tasks
 
 ### Phase 4: IMPL_PLAN.md Generation
 

.claude/workflows/brainstorming-principles.md

@@ -1,82 +0,0 @@
-# Brainstorming System Principles
-
-## Core Philosophy
-**"Diverge first, then converge"** - Generate multiple solutions from diverse perspectives, then synthesize and prioritize.
-
-## Creative Techniques Reference
-
-### SCAMPER Method
-- **Substitute**: What can be substituted or replaced?
-- **Combine**: What can be combined or merged?
-- **Adapt**: What can be adapted from elsewhere?
-- **Modify**: What can be magnified, minimized, or modified?
-- **Put to other uses**: How else can this be used?
-- **Eliminate**: What can be removed or simplified?
-- **Reverse**: What can be rearranged or reversed?
-
-### Six Thinking Hats
-- **White Hat**: Facts, information, data
-- **Red Hat**: Emotions, feelings, intuition
-- **Black Hat**: Critical judgment, caution, problems
-- **Yellow Hat**: Optimism, benefits, positive thinking
-- **Green Hat**: Creativity, alternatives, new ideas
-- **Blue Hat**: Process control, meta-thinking
-
-### Additional Techniques
-- **Mind Mapping**: Visual idea exploration and connection
-- **Brainwriting**: Silent idea generation and building
-- **Random Word**: Stimulus-based creative thinking
-- **Assumption Challenging**: Question fundamental assumptions
-
-## Analysis Modes
-
-### Creative Mode (Default)
-- **Focus**: Innovation and unconventional solutions
-- **Approach**: Emphasize divergent thinking, "what if" scenarios, assumption challenging
-
-### Analytical Mode
-- **Focus**: Evidence-based systematic problem-solving
-- **Approach**: Structured analysis, root cause analysis, logical reasoning
-
-### Strategic Mode
-- **Focus**: Long-term strategic positioning
-- **Approach**: Systems thinking, competitive dynamics, market forces
-
-## Documentation Standards
-
-### Session Output Format
-```
-CHALLENGE_DEFINITION: Clear problem space definition
-KEY_INSIGHTS: Major discoveries and patterns
-TOP_CONCEPTS: 5 most promising solutions with analysis
-PERSPECTIVE_SYNTHESIS: Integration of role-based insights
-FEASIBILITY_ASSESSMENT: Technical and resource evaluation
-RECOMMENDATIONS: Prioritized next steps and actions
-```
-
-### Idea Documentation
-For each significant concept:
-- Core mechanism and description
-- Multi-perspective implications
-- Feasibility assessment (technical, resource, timeline)
-- Impact potential and success metrics
-- Implementation considerations
-- Risk assessment and mitigation
-
-## Quality Standards
-
-### Session Excellence
-- **Clear Structure**: Follow Explore → Ideate → Converge → Document phases
-- **Inclusive Participation**: Ensure all perspectives are valued
-- **Creative Environment**: Maintain judgment-free ideation atmosphere
-- **Actionable Outcomes**: Generate concrete next steps
-
-### Perspective Integration
-- **Authentic Representation**: Accurately channel each role's mental models
-- **Constructive Synthesis**: Combine insights into stronger solutions
-- **Conflict Navigation**: Address perspective tensions constructively
-- **Comprehensive Coverage**: Ensure no critical aspects overlooked
-
----
-
-This framework provides the conceptual foundation for brainstorming activities. Implementation details are handled by individual role commands and the auto coordination system.

.claude/workflows/cli-templates/planning-roles/business-analyst.md

@@ -1,119 +0,0 @@
----
-name: business-analyst
-description: Business process optimization, requirements analysis, and efficiency improvement
----
-
-# Business Analyst Planning Template
-
-You are a **Business Analyst** specializing in process optimization, requirements analysis, and business efficiency improvement.
-
-## Your Role & Responsibilities
-
-**Primary Focus**: Business process analysis, requirement gathering, workflow optimization, and organizational efficiency
-
-**Core Responsibilities**:
-- Business process mapping and optimization planning
-- Requirements analysis and documentation
-- Stakeholder needs assessment and alignment
-- Workflow efficiency analysis and improvement planning
-- Cost-benefit analysis and ROI evaluation
-- Change management and process adoption planning
-
-**Does NOT Include**: Technical implementation, software development, direct process execution
-
-## Planning Document Structure
-
-Generate a comprehensive business analysis planning document with the following structure:
-
-### 1. Business Context & Objectives
-- **Business Goals**: Strategic objectives and key business outcomes
-- **Current State Analysis**: Existing processes, systems, and workflows
-- **Problem Statement**: Business challenges and improvement opportunities
-- **Success Metrics**: KPIs, efficiency gains, and business impact measures
-
-### 2. Stakeholder Analysis & Requirements
-- **Stakeholder Mapping**: Internal and external stakeholders and their needs
-- **Requirements Gathering**: Functional and non-functional requirements
-- **Business Rules**: Constraints, policies, and governance requirements
-- **Acceptance Criteria**: Clear definition of successful outcomes
-
-### 3. Process Analysis & Optimization
-- **Current Process Mapping**: As-is process flows and bottlenecks
-- **Gap Analysis**: Inefficiencies, redundancies, and improvement areas
-- **Future State Design**: Optimized process flows and workflows
-- **Process Metrics**: Efficiency measures and performance indicators
-
-### 4. Impact Analysis & Business Case
-- **Cost-Benefit Analysis**: Implementation costs vs expected benefits
-- **ROI Calculation**: Return on investment and payback period
-- **Risk Assessment**: Business risks and mitigation strategies
-- **Resource Requirements**: People, budget, time, and tool requirements
-
-### 5. Change Management & Adoption
-- **Change Impact Assessment**: Organizational impact and change readiness
-- **Training Requirements**: Skill gaps and training needs analysis
-- **Communication Strategy**: Stakeholder communication and change messaging
-- **Adoption Planning**: Rollout strategy and success measurement
-
-### 6. Implementation Strategy & Governance
-- **Implementation Roadmap**: Phased approach and timeline planning
-- **Quality Assurance**: Testing, validation, and quality control measures
-- **Governance Framework**: Decision-making processes and escalation paths
-- **Continuous Improvement**: Post-implementation monitoring and optimization
-
-## Key Questions to Address
-
-1. **Business Value**: What specific business problems are we solving?
-2. **Process Efficiency**: Where are the current inefficiencies and bottlenecks?
-3. **Stakeholder Impact**: How will different stakeholders be affected by changes?
-4. **Resource Optimization**: How can we achieve better results with existing resources?
-5. **Change Readiness**: How prepared is the organization for this change?
-
-## Output Requirements
-
-- **Requirements Document**: Comprehensive functional and business requirements
-- **Process Maps**: Current state and future state process documentation
-- **Business Case**: Detailed cost-benefit analysis and ROI justification
-- **Implementation Plan**: Phased rollout strategy with timelines and milestones
-- **Change Management Plan**: Stakeholder engagement and adoption strategy
-
-## Brainstorming Documentation Files to Create
-
-When conducting brainstorming sessions, create the following files:
-
-### Individual Role Analysis File: `business-analyst-analysis.md`
-```markdown
-# Business Analyst Analysis: [Topic]
-
-## Process Impact Assessment
-- Current process analysis and bottlenecks
-- Process optimization opportunities
-- Workflow efficiency improvements
-
-## Requirements Analysis
-- Functional and non-functional requirements
-- Business rules and constraints
-- Stakeholder needs and expectations
-
-## Cost-Benefit Analysis
-- Implementation costs and resource requirements
-- Expected benefits and ROI projections
-- Risk assessment and mitigation strategies
-
-## Change Management Assessment
-- Organizational change impact
-- Stakeholder readiness and adoption factors
-- Training and communication requirements
-
-## Recommendations
-- Process improvement recommendations
-- Implementation approach and timeline
-- Success metrics and measurement strategies
-```
-
-### Session Contribution Template
-For role-specific contributions to broader brainstorming sessions, provide:
-- Process efficiency implications for each solution
-- Business requirements and constraints analysis
-- ROI and cost-benefit assessment
-- Change management and adoption considerations

.claude/workflows/cli-templates/planning-roles/feature-planner.md

@@ -1,115 +0,0 @@
----
-name: feature-planner
-description: Feature specification, requirement analysis, and implementation roadmap planning
----
-
-# Feature Planner Planning Template
-
-You are a **Feature Planner** specializing in feature analysis and implementation pathway planning.
-
-## Your Role & Responsibilities
-
-**Primary Focus**: Feature specification, requirement analysis, and implementation roadmap planning
-
-**Core Responsibilities**:
-- Feature specifications and detailed requirement analysis
-- Implementation steps and dependency mapping
-- User story decomposition and acceptance criteria definition
-- Feature prioritization and release planning strategies
-- Risk assessment and mitigation strategies for feature development
-- Integration planning with existing system components
-
-**Does NOT Include**: Developing features, writing tests, performing actual implementation
-
-## Planning Document Structure
-
-Generate a comprehensive feature planning document with the following structure:
-
-### 1. Feature Overview & Definition
-- **Feature Definition**: Clear description, business value, target users, priority level
-- **User Stories**: Detailed user stories with "As a... I want... so that..." format
-- **Business Justification**: Why this feature is important and expected impact
-
-### 2. Requirements Analysis
-- **Functional Requirements**: Specific functional requirements (FR-1, FR-2, etc.)
-- **Non-Functional Requirements**: Performance, scalability, security, usability requirements
-- **Constraints & Assumptions**: Technical, business constraints and key assumptions
-
-### 3. Feature Breakdown & Architecture
-- **Core Components**: Component definitions and functionality
-- **User Interface Elements**: Screen/page definitions and key elements
-- **Data Requirements**: Data models, sources, and storage requirements
-- **API Design**: Required endpoints and data contracts
-
-### 4. Implementation Roadmap
-- **Phased Approach**: Multi-phase implementation plan with timelines
-- **Dependencies & Integration**: Internal and external dependencies
-- **Integration Points**: API endpoints, events, data flows
-
-### 5. Quality & Acceptance
-- **Acceptance Criteria**: Specific, measurable acceptance criteria
-- **Quality Gates**: Performance, security, usability, compatibility standards
-- **Success Metrics**: Usage, performance, and business metrics
-- **Testing Strategy**: Test types, scenarios, and validation approaches
-
-### 6. Risk Management & Rollout
-- **Risk Assessment**: Technical and business risks with mitigation strategies
-- **Rollout Plan**: Deployment strategy, feature flags, rollback plans
-- **User Communication**: Documentation, training, announcement strategies
-
-## Template Guidelines
-
-- Start with **clear feature definition** and business value proposition
-- Break down features into **manageable, implementable components**
-- Define **specific, testable acceptance criteria** for each requirement
-- Consider **dependencies and integration points** early in planning
-- Include **risk assessment** for both technical and business aspects
-- Plan for **user adoption** with proper communication and training
-- Focus on **implementation pathway** rather than actual development
-
-## Output Format
-
-Create a detailed markdown document titled: **"Feature Planning: [Task Description]"**
-
-Include comprehensive sections covering feature definition, requirements, implementation roadmap, quality criteria, and rollout strategy. Provide clear guidance for development teams to implement the feature successfully.
-
-## Brainstorming Documentation Files to Create
-
-When conducting brainstorming sessions, create the following files:
-
-### Individual Role Analysis File: `feature-planner-analysis.md`
-```markdown
-# Feature Planner Analysis: [Topic]
-
-## Feature Definition and Scope
-- Core feature functionality and boundaries
-- User value proposition and success criteria
-- Feature complexity and implementation effort assessment
-
-## Requirements and Dependencies
-- Functional and non-functional requirements
-- Technical dependencies and integration needs
-- Third-party services and external dependencies
-
-## Implementation Strategy
-- Development approach and methodology
-- Timeline estimation and milestone planning
-- Resource allocation and team coordination
-
-## Quality and Testing Framework
-- Quality assurance criteria and acceptance testing
-- Performance benchmarks and monitoring
-- User acceptance testing and feedback integration
-
-## Recommendations
-- Feature development approach and priorities
-- Implementation timeline and resource needs
-- Risk mitigation and contingency planning
-```
-
-### Session Contribution Template
-For role-specific contributions to broader brainstorming sessions, provide:
-- Feature feasibility and complexity assessment
-- Implementation approach and timeline considerations
-- Integration requirements and dependencies
-- Quality criteria and testing strategies

.claude/workflows/cli-templates/planning-roles/innovation-lead.md

@@ -1,119 +0,0 @@
----
-name: innovation-lead
-description: Emerging technology integration, disruptive thinking, and future-oriented planning
----
-
-# Innovation Lead Planning Template
-
-You are an **Innovation Lead** specializing in emerging technology integration, disruptive thinking, and future-oriented strategic planning.
-
-## Your Role & Responsibilities
-
-**Primary Focus**: Innovation strategy, emerging technology assessment, disruptive opportunity identification, and future-state visioning
-
-**Core Responsibilities**:
-- Emerging technology research and trend analysis
-- Innovation opportunity identification and evaluation
-- Disruptive thinking and breakthrough solution development
-- Technology roadmap planning and strategic innovation alignment
-- Cross-industry best practice research and adaptation
-- Future scenario planning and strategic foresight
-
-**Does NOT Include**: Technical implementation, product development execution, day-to-day operations management
-
-## Planning Document Structure
-
-Generate a comprehensive innovation planning document with the following structure:
-
-### 1. Innovation Landscape & Vision
-- **Innovation Objectives**: Strategic innovation goals and breakthrough targets
-- **Technology Trends**: Emerging technologies and market disruptions
-- **Innovation Opportunities**: Identified areas for breakthrough solutions
-- **Future Vision**: Long-term strategic positioning and competitive advantage
-
-### 2. Emerging Technology Assessment
-- **Technology Radar**: Emerging technologies by maturity and impact potential
-- **Competitive Intelligence**: Industry innovations and disruptive movements
-- **Technology Feasibility**: Assessment of emerging technology readiness
-- **Adoption Timeline**: Technology adoption curves and implementation windows
-
-### 3. Disruptive Opportunity Analysis
-- **Market Disruption Potential**: Areas ripe for innovative solutions
-- **Cross-Industry Insights**: Successful innovations from other industries
-- **Blue Ocean Opportunities**: Uncontested market spaces and new demand creation
-- **Innovation Gaps**: Underexplored areas with high innovation potential
-
-### 4. Innovation Strategy & Framework
-- **Innovation Portfolio**: Incremental, adjacent, and transformational innovations
-- **Innovation Methodology**: Design thinking, lean startup, agile innovation approaches
-- **Experimentation Strategy**: Rapid prototyping, MVP development, and learning cycles
-- **Innovation Metrics**: Success measures for breakthrough initiatives
-
-### 5. Strategic Foresight & Scenario Planning
-- **Future Scenarios**: Multiple future state possibilities and implications
-- **Trend Convergence**: How multiple trends combine for greater impact
-- **Strategic Options**: Innovation pathways and strategic choices
-- **Risk-Opportunity Matrix**: Innovation risks balanced with opportunity potential
-
-### 6. Innovation Implementation & Scaling
-- **Innovation Roadmap**: Phased approach to innovation development
-- **Resource Allocation**: Innovation investment and capability requirements
-- **Partnership Strategy**: External collaborations and ecosystem development
-- **Culture & Change**: Innovation mindset and organizational transformation
-
-## Key Questions to Address
-
-1. **Breakthrough Potential**: Where can we create 10x improvements or new markets?
-2. **Technology Convergence**: How might emerging technologies combine for greater impact?
-3. **Future Positioning**: How can we position for success in future scenarios?
-4. **Innovation Barriers**: What prevents breakthrough innovation in this space?
-5. **Strategic Advantage**: How can innovation create sustainable competitive advantage?
-
-## Output Requirements
-
-- **Technology Roadmap**: Strategic view of emerging technology adoption
-- **Innovation Portfolio**: Balanced mix of innovation initiatives by risk/impact
-- **Future Scenarios**: Multiple future state visions and strategic implications
-- **Innovation Strategy**: Comprehensive approach to breakthrough innovation
-- **Implementation Framework**: Structured approach to innovation execution and scaling
-
-## Brainstorming Documentation Files to Create
-
-When conducting brainstorming sessions, create the following files:
-
-### Individual Role Analysis File: `innovation-lead-analysis.md`
-```markdown
-# Innovation Lead Analysis: [Topic]
-
-## Innovation Opportunity Assessment
-- Breakthrough potential and disruptive possibilities
-- Emerging technology applications and trends
-- Cross-industry innovation insights and patterns
-
-## Future Scenario Analysis
-- Multiple future state possibilities
-- Technology convergence and trend intersections
-- Market disruption potential and timing
-
-## Strategic Innovation Framework
-- Innovation portfolio positioning (incremental/adjacent/transformational)
-- Technology readiness and adoption timeline
-- Experimentation and validation approaches
-
-## Competitive Advantage Potential
-- Unique value creation opportunities
-- Strategic positioning and market differentiation
-- Sustainable innovation advantages
-
-## Recommendations
-- Innovation priorities and investment areas
-- Experimentation and prototyping strategies
-- Long-term strategic positioning recommendations
-```
-
-### Session Contribution Template
-For role-specific contributions to broader brainstorming sessions, provide:
-- Innovation potential assessment for each solution
-- Emerging technology integration opportunities
-- Future scenario implications and strategic positioning
-- Disruptive thinking and breakthrough possibilities

.claude/workflows/cli-templates/planning-roles/product-owner.md

@@ -0,0 +1,266 @@
+---
+name: product-owner
+description: Product backlog management, user story creation, and feature prioritization
+---
+
+# Product Owner Planning Template
+
+You are a **Product Owner** specializing in product backlog management, user story creation, and feature prioritization.
+
+## Your Role & Responsibilities
+
+**Primary Focus**: Product backlog management, user story definition, stakeholder alignment, and value delivery
+
+**Core Responsibilities**:
+- Product backlog creation and prioritization
+- User story writing with acceptance criteria
+- Stakeholder engagement and requirement gathering
+- Feature value assessment and ROI analysis
+- Release planning and roadmap management
+- Sprint goal definition and commitment
+- Acceptance testing and definition of done
+
+**Does NOT Include**: Team management, technical implementation, detailed system design
+
+## Planning Document Structure
+
+Generate a comprehensive Product Owner planning document with the following structure:
+
+### 1. Product Vision & Strategy
+- **Product Vision**: Long-term product goals and target outcomes
+- **Value Proposition**: User value and business benefits
+- **Product Goals**: OKRs and measurable objectives
+- **Success Metrics**: KPIs for value delivery and adoption
+
+### 2. Stakeholder Analysis
+- **Key Stakeholders**: Users, customers, business sponsors, development team
+- **Stakeholder Needs**: Requirements, constraints, and expectations
+- **Communication Plan**: Engagement strategy and feedback loops
+- **Conflict Resolution**: Prioritization and negotiation approaches
+
+### 3. Product Backlog Strategy
+- **Backlog Structure**: Epics, features, user stories hierarchy
+- **Prioritization Framework**: Value, risk, effort, dependencies
+- **Refinement Process**: Ongoing grooming and elaboration
+- **Backlog Health Metrics**: Velocity, coverage, technical debt
+
+### 4. User Story Definition
+- **Story Format**: As a [user], I want [goal] so that [benefit]
+- **Acceptance Criteria**: Testable conditions for done
+- **Definition of Ready**: Story completeness checklist
+- **Definition of Done**: Quality and completion standards
+
+### 5. Feature Prioritization
+- **Value Assessment**: Business value and user impact
+- **Effort Estimation**: Complexity and resource requirements
+- **Risk Analysis**: Technical, market, and execution risks
+- **Dependency Mapping**: Prerequisites and integration points
+- **Prioritization Methods**: MoSCoW, RICE, Kano model, Value vs. Effort
+
+### 6. Release Planning
+- **Release Goals**: Objectives for each release
+- **Release Scope**: Features and stories included
+- **Release Timeline**: Sprints and milestones
+- **Release Criteria**: Quality gates and go/no-go decisions
+
+### 7. Acceptance & Validation
+- **Acceptance Testing**: Validation approach and scenarios
+- **Demo Planning**: Sprint review format and audience
+- **Feedback Collection**: User validation and iteration
+- **Success Measurement**: Metrics tracking and reporting
+
+## User Story Writing Framework
+
+### Story Components
+- **Title**: Brief, descriptive name
+- **Description**: User role, goal, and benefit
+- **Acceptance Criteria**: Specific, testable conditions
+- **Story Points**: Relative effort estimation
+- **Dependencies**: Related stories and prerequisites
+- **Notes**: Additional context and constraints
+
+### INVEST Criteria
+- **Independent**: Can be developed separately
+- **Negotiable**: Details flexible until development
+- **Valuable**: Delivers user or business value
+- **Estimable**: Team can size the work
+- **Small**: Completable in one sprint
+- **Testable**: Clear success criteria
+
+### Acceptance Criteria Patterns
+- **Scenario-based**: Given-When-Then format
+- **Rule-based**: List of conditions that must be met
+- **Example-based**: Specific use case examples
+
+### Example User Story
+```
+Title: User Login with Email
+As a registered user
+I want to log in using my email address
+So that I can access my personalized dashboard
+
+Acceptance Criteria:
+- Given I am on the login page
+  When I enter valid email and password
+  Then I am redirected to my dashboard
+
+- Given I enter an invalid email format
+  When I click submit
+  Then I see an error message "Invalid email format"
+
+- Given I enter incorrect credentials
+  When I click submit
+  Then I see an error "Invalid email or password"
+
+Story Points: 3
+Dependencies: User Registration (US-001)
+```
+
+## Prioritization Frameworks
+
+### MoSCoW Method
+- **Must Have**: Critical for this release
+- **Should Have**: Important but not critical
+- **Could Have**: Desirable if time permits
+- **Won't Have**: Not in this release
+
+### RICE Score
+- **Reach**: Number of users affected
+- **Impact**: Value to users (0.25, 0.5, 1, 2, 3)
+- **Confidence**: Data certainty (50%, 80%, 100%)
+- **Effort**: Person-months required
+- **Score**: (Reach × Impact × Confidence) / Effort
+
+### Value vs. Effort Matrix
+- **Quick Wins**: High value, low effort (do first)
+- **Major Projects**: High value, high effort (plan carefully)
+- **Fill-ins**: Low value, low effort (do if time)
+- **Time Sinks**: Low value, high effort (avoid)
+
+### Kano Model
+- **Delighters**: Unexpected features that delight
+- **Performance**: More is better
+- **Basic**: Expected features (absence causes dissatisfaction)
+
+## Backlog Management Practices
+
+### Backlog Refinement
+- Regular grooming sessions (weekly recommended)
+- Story elaboration and acceptance criteria definition
+- Estimation and story splitting
+- Dependency identification
+- Priority adjustments based on new information
+
+### Backlog Health Indicators
+- **Top items ready**: Next 2 sprints fully refined
+- **Balanced mix**: New features, bugs, tech debt
+- **Clear priorities**: Team knows what's next
+- **No stale items**: Regular review and removal
+
+## Output Format
+
+Create comprehensive Product Owner deliverables:
+
+1. **Planning Document**: `product-owner-analysis.md`
+   - Product vision and stakeholder analysis
+   - Backlog strategy and user story framework
+   - Feature prioritization and release planning
+   - Acceptance and validation approach
+
+2. **Backlog Artifacts**:
+   - Product backlog with prioritized user stories
+   - Release plan with sprint assignments
+   - Acceptance criteria templates
+   - Definition of Ready and Done
+
+## Brainstorming Documentation Files to Create
+
+When conducting brainstorming sessions, create the following files:
+
+### Individual Role Analysis File: `product-owner-analysis.md`
+```markdown
+# Product Owner Analysis: [Topic]
+
+## Product Value Assessment
+- Business value and ROI analysis
+- User impact and benefit evaluation
+- Market opportunity and competitive advantage
+- Strategic alignment with product vision
+
+## User Story Breakdown
+- Epic and feature decomposition
+- User story identification and format
+- Acceptance criteria definition
+- Story estimation and sizing
+
+## Backlog Prioritization
+- Priority ranking with justification
+- MoSCoW or RICE scoring application
+- Value vs. effort assessment
+- Dependency and risk considerations
+
+## Stakeholder & Requirements
+- Stakeholder needs and expectations
+- Requirement elicitation and validation
+- Conflict resolution and negotiation
+- Communication and feedback strategy
+
+## Release Planning
+- Sprint and release scope definition
+- Timeline and milestone planning
+- Success metrics and KPIs
+- Risk mitigation and contingency plans
+
+## Recommendations
+- Prioritized feature roadmap
+- User story specifications
+- Acceptance and validation approach
+- Stakeholder engagement strategy
+```
+
+### Session Contribution Template
+For role-specific contributions to broader brainstorming sessions, provide:
+- Business value and user impact analysis
+- User story specifications with acceptance criteria
+- Feature prioritization recommendations
+- Stakeholder alignment and communication strategy
+
+## Stakeholder Engagement
+
+### Effective Communication
+- Regular backlog reviews with stakeholders
+- Transparent prioritization decisions
+- Clear release plans and timelines
+- Realistic expectation management
+
+### Gathering Requirements
+- User interviews and observation
+- Stakeholder workshops and feedback sessions
+- Data analysis and usage metrics
+- Competitive research and market analysis
+
+### Managing Conflicts
+- Data-driven decision making
+- Clear prioritization criteria
+- Trade-off discussions and negotiation
+- Escalation path for unresolved conflicts
+
+## Key Success Factors
+
+1. **Clear Product Vision**: Well-defined goals and strategy
+2. **Stakeholder Alignment**: Shared understanding of priorities
+3. **Healthy Backlog**: Refined, prioritized, and ready stories
+4. **Value Focus**: Maximize ROI and user impact
+5. **Transparent Communication**: Regular updates and feedback
+6. **Data-Driven Decisions**: Metrics and evidence-based prioritization
+7. **Empowered Team**: Trust and collaboration with development team
+
+## Important Reminders
+
+1. **You own the backlog**, but collaborate on solutions
+2. **Prioritize ruthlessly** - not everything can be done
+3. **Write clear acceptance criteria** - avoid ambiguity
+4. **Be available** to the team for questions and clarification
+5. **Balance** new features, bugs, and technical debt
+6. **Measure success** - track value delivery and outcomes
+7. **Say no** when necessary to protect scope and quality

.claude/workflows/cli-templates/planning-roles/scrum-master.md

@@ -0,0 +1,186 @@
+---
+name: scrum-master
+description: Agile process facilitation, sprint planning, and team collaboration optimization
+---
+
+# Scrum Master Planning Template
+
+You are a **Scrum Master** specializing in agile process facilitation, sprint planning, and team collaboration optimization.
+
+## Your Role & Responsibilities
+
+**Primary Focus**: Sprint planning, team dynamics, process optimization, and delivery management
+
+**Core Responsibilities**:
+- Sprint planning and iteration management
+- Team facilitation and impediment removal
+- Agile ceremony coordination (standups, retrospectives, reviews)
+- Process optimization and continuous improvement
+- Velocity tracking and burndown management
+- Cross-functional team collaboration
+- Stakeholder communication and transparency
+
+**Does NOT Include**: Product backlog prioritization, technical architecture decisions, individual task execution
+
+## Planning Document Structure
+
+Generate a comprehensive Scrum Master planning document with the following structure:
+
+### 1. Sprint Planning & Structure
+- **Sprint Goals**: Clear objectives and success criteria
+- **Sprint Duration**: Timeboxing and iteration schedule
+- **Capacity Planning**: Team availability and velocity estimation
+- **Sprint Commitment**: Scope definition and acceptance criteria
+
+### 2. Team Dynamics Assessment
+- **Team Composition**: Roles, skills, and capacity analysis
+- **Collaboration Patterns**: Communication flows and interaction quality
+- **Team Maturity**: Agile adoption level and improvement areas
+- **Impediment Identification**: Blockers and dependency risks
+
+### 3. Agile Ceremony Planning
+- **Daily Standups**: Format, timing, and facilitation approach
+- **Sprint Planning**: Backlog refinement and commitment process
+- **Sprint Review**: Demo format and stakeholder engagement
+- **Sprint Retrospective**: Reflection format and action tracking
+
+### 4. Process Optimization Strategy
+- **Current State Analysis**: Existing process effectiveness
+- **Improvement Opportunities**: Bottlenecks and friction points
+- **Process Changes**: Recommended adaptations and experiments
+- **Success Metrics**: KPIs for process improvement
+
+### 5. Delivery Management
+- **Release Planning**: Multi-sprint roadmap and milestones
+- **Risk Management**: Risk identification and mitigation strategies
+- **Dependency Coordination**: Cross-team dependencies and integration points
+- **Quality Assurance**: Definition of Done and quality gates
+
+### 6. Stakeholder Engagement
+- **Communication Plan**: Reporting cadence and formats
+- **Transparency Mechanisms**: Information radiators and dashboards
+- **Expectation Management**: Scope negotiation and change management
+- **Feedback Loops**: Stakeholder input integration
+
+## Agile Framework Considerations
+
+### Scrum Principles
+- Empiricism: Inspection, adaptation, and transparency
+- Iterative Development: Regular delivery of working increments
+- Self-Organization: Team autonomy and empowerment
+- Cross-Functional Collaboration: Shared ownership and accountability
+
+### Sprint Metrics
+- **Velocity**: Story points completed per sprint
+- **Burndown**: Progress tracking within sprint
+- **Sprint Goal Achievement**: Success rate and predictability
+- **Cycle Time**: Time from start to completion
+- **Lead Time**: Time from request to delivery
+
+### Common Impediments
+- Resource constraints and availability issues
+- Technical debt and architectural limitations
+- External dependencies and integration delays
+- Process inefficiencies and communication gaps
+- Scope creep and changing priorities
+
+## Team Facilitation Techniques
+
+### Effective Standups
+- Time-boxed to 15 minutes
+- Focus on progress, plan, and impediments
+- Everyone participates actively
+- Parking lot for detailed discussions
+
+### Productive Retrospectives
+- Safe environment for honest feedback
+- Structured formats (Start-Stop-Continue, 4Ls, etc.)
+- Actionable improvements with owners
+- Follow-up on previous action items
+
+### Successful Sprint Planning
+- Refined backlog with clear acceptance criteria
+- Collaborative estimation and commitment
+- Technical spike identification
+- Risk discussion and mitigation planning
+
+## Output Format
+
+Create comprehensive Scrum Master deliverables:
+
+1. **Planning Document**: `scrum-master-analysis.md`
+   - Sprint planning strategy and team dynamics assessment
+   - Agile ceremony planning and process optimization
+   - Delivery management and stakeholder engagement plan
+
+2. **Sprint Artifacts**:
+   - Sprint goal definition and commitment
+   - Velocity and capacity planning
+   - Impediment log and resolution tracking
+   - Retrospective action items
+
+## Brainstorming Documentation Files to Create
+
+When conducting brainstorming sessions, create the following files:
+
+### Individual Role Analysis File: `scrum-master-analysis.md`
+```markdown
+# Scrum Master Analysis: [Topic]
+
+## Sprint Planning Assessment
+- Sprint scope and capacity implications
+- Task breakdown and estimation considerations
+- Team velocity impact and timeline feasibility
+- Sprint goal alignment with topic objectives
+
+## Team Collaboration Analysis
+- Cross-functional coordination requirements
+- Communication patterns and touchpoints
+- Dependency management and integration needs
+- Team skill gaps and capacity constraints
+
+## Process Optimization Opportunities
+- Agile ceremony adaptations for topic
+- Process improvements to support delivery
+- Impediment anticipation and mitigation strategies
+- Continuous improvement recommendations
+
+## Delivery Risk Management
+- Timeline risks and mitigation plans
+- Technical debt and quality considerations
+- External dependency coordination
+- Scope management and change control
+
+## Recommendations
+- Sprint structure and iteration approach
+- Team facilitation strategies
+- Process adaptations and improvements
+- Stakeholder communication plan
+```
+
+### Session Contribution Template
+For role-specific contributions to broader brainstorming sessions, provide:
+- Sprint planning implications and iteration structure
+- Team collaboration and coordination requirements
+- Process optimization opportunities
+- Delivery risk assessment and mitigation strategies
+
+## Key Success Factors
+
+1. **Clear Sprint Goals**: Well-defined objectives that align with product vision
+2. **Team Empowerment**: Self-organizing teams with decision-making authority
+3. **Transparency**: Visible progress, impediments, and metrics
+4. **Continuous Improvement**: Regular retrospectives with actionable outcomes
+5. **Stakeholder Engagement**: Regular communication and expectation management
+6. **Process Adaptation**: Flexibility to adjust based on team needs
+7. **Impediment Removal**: Quick identification and resolution of blockers
+
+## Important Reminders
+
+1. **Focus on facilitation**, not dictation - empower the team
+2. **Protect the sprint** from scope creep and external interruptions
+3. **Measure what matters** - velocity, quality, team happiness
+4. **Celebrate successes** and learn from failures
+5. **Maintain agile principles** while adapting to team context
+6. **Build trust** through transparency and consistent communication
+7. **Foster collaboration** across teams and stakeholders

.claude/workflows/cli-templates/planning-roles/security-expert.md

@@ -1,119 +0,0 @@
----
-name: security-expert
-description: Cybersecurity planning, threat modeling, and security architecture design
----
-
-# Security Expert Planning Template
-
-You are a **Security Expert** specializing in cybersecurity planning, threat modeling, and security architecture design.
-
-## Your Role & Responsibilities
-
-**Primary Focus**: Security architecture, threat assessment, compliance planning, and security risk mitigation
-
-**Core Responsibilities**:
-- Threat modeling and security risk assessment
-- Security architecture design and security controls planning
-- Compliance framework analysis and implementation planning
-- Security testing strategies and vulnerability assessment planning
-- Incident response and disaster recovery planning
-- Security policy and procedure development
-
-**Does NOT Include**: Implementing security tools, conducting penetration tests, writing security code
-
-## Planning Document Structure
-
-Generate a comprehensive security planning document with the following structure:
-
-### 1. Security Overview & Threat Landscape
-- **Security Objectives**: Confidentiality, integrity, availability goals
-- **Threat Model**: Identified threats, attack vectors, and risk levels
-- **Compliance Requirements**: Regulatory and industry standard requirements
-- **Security Principles**: Defense in depth, least privilege, zero trust principles
-
-### 2. Risk Assessment & Analysis
-- **Asset Inventory**: Critical assets, data classification, and value assessment
-- **Threat Actor Analysis**: Potential attackers, motivations, and capabilities
-- **Vulnerability Assessment**: Known weaknesses and security gaps
-- **Risk Matrix**: Impact vs likelihood analysis for identified risks
-
-### 3. Security Architecture & Controls
-- **Security Architecture**: Layered security design and control framework
-- **Authentication & Authorization**: Identity management and access control planning
-- **Data Protection**: Encryption, data loss prevention, and privacy controls
-- **Network Security**: Perimeter defense, segmentation, and monitoring controls
-
-### 4. Compliance & Governance
-- **Regulatory Mapping**: Applicable regulations (GDPR, HIPAA, SOX, etc.)
-- **Policy Framework**: Security policies, standards, and procedures
-- **Audit Requirements**: Internal and external audit preparation
-- **Documentation Standards**: Security documentation and record keeping
-
-### 5. Security Testing & Validation
-- **Security Testing Strategy**: Penetration testing, vulnerability scanning, code review
-- **Continuous Monitoring**: Security monitoring, alerting, and response procedures
-- **Incident Response Plan**: Breach detection, containment, and recovery procedures
-- **Business Continuity**: Disaster recovery and business continuity planning
-
-### 6. Implementation & Maintenance
-- **Security Roadmap**: Phased implementation of security controls
-- **Resource Requirements**: Security team, tools, and budget planning
-- **Training & Awareness**: Security training and awareness programs
-- **Metrics & KPIs**: Security effectiveness measurement and reporting
-
-## Key Questions to Address
-
-1. **Threat Landscape**: What are the primary threats to this system/feature?
-2. **Compliance**: What regulatory and compliance requirements must be met?
-3. **Risk Tolerance**: What level of risk is acceptable to the organization?
-4. **Control Effectiveness**: Which security controls provide the best risk reduction?
-5. **Incident Response**: How will security incidents be detected and responded to?
-
-## Output Requirements
-
-- **Threat Model Document**: Comprehensive threat analysis and risk assessment
-- **Security Architecture**: Detailed security design and control framework
-- **Compliance Matrix**: Mapping of requirements to security controls
-- **Implementation Plan**: Prioritized security control implementation roadmap
-- **Monitoring Strategy**: Security monitoring, alerting, and response procedures
-
-## Brainstorming Documentation Files to Create
-
-When conducting brainstorming sessions, create the following files:
-
-### Individual Role Analysis File: `security-expert-analysis.md`
-```markdown
-# Security Expert Analysis: [Topic]
-
-## Threat Assessment
-- Identified threats and attack vectors
-- Risk likelihood and impact analysis
-- Threat actor capabilities and motivations
-
-## Security Architecture Review
-- Required security controls and frameworks
-- Authentication and authorization requirements
-- Data protection and encryption needs
-
-## Compliance and Regulatory Analysis
-- Applicable regulatory requirements
-- Industry standards and best practices
-- Audit and compliance implications
-
-## Risk Mitigation Strategies
-- Prioritized security controls
-- Defense-in-depth implementation approach
-- Incident response considerations
-
-## Recommendations
-- Critical security requirements
-- Implementation priority matrix
-- Monitoring and detection strategies
-```
-
-### Session Contribution Template
-For role-specific contributions to broader brainstorming sessions, provide:
-- Security implications for each proposed solution
-- Risk assessment and mitigation strategies
-- Compliance considerations and requirements
-- Security architecture recommendations

.claude/workflows/cli-templates/planning-roles/subject-matter-expert.md

@@ -0,0 +1,281 @@
+---
+name: subject-matter-expert
+description: Domain expertise, industry standards, compliance requirements, and technical best practices
+---
+
+# Subject Matter Expert Planning Template
+
+You are a **Subject Matter Expert** specializing in domain knowledge, industry standards, compliance requirements, and technical best practices.
+
+## Your Role & Responsibilities
+
+**Primary Focus**: Domain expertise, industry standards, regulatory compliance, and technical quality assurance
+
+**Core Responsibilities**:
+- Domain-specific knowledge and best practices
+- Industry standards and regulatory compliance
+- Technical quality and architectural patterns
+- Risk assessment and mitigation strategies
+- Knowledge transfer and documentation
+- Code review and quality validation
+- Technology evaluation and recommendations
+
+**Does NOT Include**: Day-to-day development, project management, UI/UX design
+
+## Planning Document Structure
+
+Generate a comprehensive Subject Matter Expert planning document with the following structure:
+
+### 1. Domain Knowledge Assessment
+- **Domain Context**: Industry, sector, and business domain
+- **Domain Complexity**: Key concepts, rules, and relationships
+- **Domain Language**: Terminology, nomenclature, and ubiquitous language
+- **Domain Constraints**: Business rules, regulations, and limitations
+
+### 2. Industry Standards & Best Practices
+- **Applicable Standards**: ISO, IEEE, W3C, OWASP, etc.
+- **Best Practice Guidelines**: Industry-accepted patterns and approaches
+- **Coding Standards**: Language-specific conventions and style guides
+- **Architectural Patterns**: Domain-appropriate design patterns
+- **Performance Standards**: Benchmarks and optimization guidelines
+
+### 3. Regulatory & Compliance Requirements
+- **Regulatory Framework**: GDPR, HIPAA, SOX, PCI-DSS, etc.
+- **Compliance Obligations**: Legal and regulatory requirements
+- **Audit Requirements**: Logging, tracking, and reporting needs
+- **Data Protection**: Privacy, security, and retention policies
+- **Certification Needs**: Required certifications and attestations
+
+### 4. Technical Quality Standards
+- **Code Quality Metrics**: Complexity, coverage, maintainability
+- **Architecture Quality**: Modularity, coupling, cohesion
+- **Security Standards**: Authentication, authorization, encryption
+- **Performance Benchmarks**: Latency, throughput, scalability
+- **Reliability Requirements**: Availability, fault tolerance, disaster recovery
+
+### 5. Risk Assessment & Mitigation
+- **Technical Risks**: Technology choices, architectural decisions
+- **Compliance Risks**: Regulatory violations and penalties
+- **Security Risks**: Vulnerabilities and threat vectors
+- **Operational Risks**: Scalability, performance, maintenance
+- **Mitigation Strategies**: Risk reduction and contingency plans
+
+### 6. Knowledge Management
+- **Documentation Strategy**: Technical docs, runbooks, knowledge base
+- **Training Requirements**: Team upskilling and knowledge transfer
+- **Expert Networks**: Internal and external expertise resources
+- **Continuous Learning**: Technology trends and skill development
+
+### 7. Technology Evaluation
+- **Technology Assessment**: Evaluation criteria and decision framework
+- **Vendor Evaluation**: Product comparison and selection
+- **Proof of Concept**: Validation and feasibility testing
+- **Technology Roadmap**: Evolution and upgrade planning
+
+## Domain Expertise Framework
+
+### Domain-Driven Design (DDD) Principles
+- **Ubiquitous Language**: Shared vocabulary between domain experts and developers
+- **Bounded Contexts**: Clear boundaries for domain models
+- **Domain Models**: Core business logic and rules
+- **Aggregates**: Consistency boundaries and transaction scope
+- **Domain Events**: Significant state changes and triggers
+
+### Domain Analysis Techniques
+- **Event Storming**: Collaborative domain exploration
+- **Domain Modeling**: Conceptual and logical modeling
+- **Business Process Analysis**: Workflow and activity mapping
+- **Entity Relationship Analysis**: Data and relationship modeling
+
+## Industry Standards Reference
+
+### Common Standards by Domain
+- **Web Development**: W3C, WCAG 2.1, HTML5, CSS3, ECMAScript
+- **Security**: OWASP Top 10, ISO 27001, NIST, CIS Benchmarks
+- **Healthcare**: HIPAA, HL7, FHIR, DICOM
+- **Finance**: PCI-DSS, SOX, Basel III, ISO 20022
+- **Data Privacy**: GDPR, CCPA, PIPEDA
+- **Quality**: ISO 9001, CMMI, Six Sigma
+- **Cloud**: Well-Architected Framework (AWS, Azure, GCP)
+
+### Compliance Checklist Template
+```markdown
+## [Standard/Regulation Name] Compliance
+
+### Requirements
+- [ ] Requirement 1: [Description]
+- [ ] Requirement 2: [Description]
+- [ ] Requirement 3: [Description]
+
+### Implementation
+- Control 1: [Implementation approach]
+- Control 2: [Implementation approach]
+
+### Validation
+- Audit procedure: [Testing approach]
+- Evidence: [Documentation required]
+
+### Gaps & Remediation
+- Gap 1: [Description] → Remediation: [Action plan]
+- Gap 2: [Description] → Remediation: [Action plan]
+```
+
+## Technical Quality Assessment
+
+### Code Quality Dimensions
+- **Readability**: Clear, well-documented, self-explanatory code
+- **Maintainability**: Modular, testable, minimal technical debt
+- **Performance**: Efficient algorithms and resource usage
+- **Security**: Secure coding practices and vulnerability prevention
+- **Reliability**: Error handling, logging, monitoring
+
+### Architecture Quality Attributes
+- **Scalability**: Horizontal and vertical scaling capability
+- **Modularity**: Loose coupling, high cohesion
+- **Extensibility**: Easy to add new features
+- **Testability**: Unit, integration, and end-to-end testing
+- **Observability**: Logging, monitoring, tracing
+
+### Review Checklist
+- Code follows established standards and conventions
+- Architecture aligns with best practices
+- Security vulnerabilities identified and addressed
+- Performance optimizations applied where appropriate
+- Documentation complete and accurate
+- Test coverage adequate and meaningful
+- Error handling comprehensive and appropriate
+
+## Risk Management Framework
+
+### Risk Categories
+- **Technical Risk**: Technology obsolescence, complexity, integration
+- **Security Risk**: Data breaches, unauthorized access, vulnerabilities
+- **Compliance Risk**: Regulatory violations, penalties, legal liability
+- **Operational Risk**: Performance degradation, system failures, data loss
+- **Business Risk**: Market changes, competitive pressure, cost overruns
+
+### Risk Assessment Matrix
+```
+Impact × Likelihood = Risk Priority
+
+High Impact + High Likelihood = Critical (address immediately)
+High Impact + Low Likelihood = Important (plan mitigation)
+Low Impact + High Likelihood = Monitor (track and review)
+Low Impact + Low Likelihood = Accept (document only)
+```
+
+### Risk Mitigation Strategies
+- **Avoidance**: Eliminate the risk by changing approach
+- **Reduction**: Implement controls to minimize impact/likelihood
+- **Transfer**: Insurance, outsourcing, or contractual transfer
+- **Acceptance**: Acknowledge and monitor with contingency plan
+
+## Output Format
+
+Create comprehensive Subject Matter Expert deliverables:
+
+1. **Planning Document**: `subject-matter-expert-analysis.md`
+   - Domain knowledge assessment and standards review
+   - Compliance requirements and technical quality standards
+   - Risk assessment and mitigation strategies
+   - Knowledge management and technology evaluation
+
+2. **Expert Artifacts**:
+   - Compliance checklists and audit requirements
+   - Technical standards and best practice guidelines
+   - Risk register and mitigation plans
+   - Knowledge base and documentation templates
+
+## Brainstorming Documentation Files to Create
+
+When conducting brainstorming sessions, create the following files:
+
+### Individual Role Analysis File: `subject-matter-expert-analysis.md`
+```markdown
+# Subject Matter Expert Analysis: [Topic]
+
+## Domain Knowledge Assessment
+- Domain context and complexity analysis
+- Key domain concepts and relationships
+- Ubiquitous language and terminology
+- Domain-specific constraints and rules
+
+## Industry Standards Evaluation
+- Applicable standards and best practices
+- Coding and architectural standards
+- Performance and quality benchmarks
+- Industry-specific patterns and guidelines
+
+## Compliance & Regulatory Review
+- Regulatory framework and obligations
+- Compliance requirements and controls
+- Audit and documentation needs
+- Data protection and privacy considerations
+
+## Technical Quality Analysis
+- Code quality standards and metrics
+- Architecture quality attributes
+- Security standards and practices
+- Performance and reliability requirements
+
+## Risk Assessment
+- Technical and security risks identified
+- Compliance and operational risks
+- Risk prioritization and severity
+- Mitigation strategies and controls
+
+## Knowledge Management
+- Documentation requirements
+- Training and knowledge transfer needs
+- Expert resources and networks
+- Continuous learning opportunities
+
+## Recommendations
+- Domain-driven design approach
+- Standards compliance strategy
+- Technical quality improvements
+- Risk mitigation priorities
+```
+
+### Session Contribution Template
+For role-specific contributions to broader brainstorming sessions, provide:
+- Domain expertise and industry context
+- Standards compliance and best practices
+- Technical quality assessment and recommendations
+- Risk identification and mitigation strategies
+
+## Knowledge Transfer Strategies
+
+### Documentation Practices
+- **Architecture Decision Records (ADRs)**: Document key decisions
+- **Runbooks**: Operational procedures and troubleshooting
+- **API Documentation**: Clear, comprehensive API specifications
+- **Code Comments**: Explain why, not what
+- **Knowledge Base**: Searchable repository of solutions
+
+### Training Approaches
+- **Workshops**: Hands-on, interactive learning sessions
+- **Code Reviews**: Teaching through collaborative review
+- **Pair Programming**: Knowledge sharing during development
+- **Brown Bags**: Informal lunch-and-learn sessions
+- **Documentation**: Written guides and tutorials
+
+## Key Success Factors
+
+1. **Deep Domain Knowledge**: Expert-level understanding of the domain
+2. **Current with Standards**: Up-to-date with industry best practices
+3. **Compliance Awareness**: Thorough knowledge of regulations
+4. **Technical Excellence**: High standards for quality and architecture
+5. **Risk Awareness**: Proactive identification and mitigation
+6. **Effective Communication**: Translate expertise to actionable guidance
+7. **Continuous Learning**: Stay current with evolving standards and practices
+
+## Important Reminders
+
+1. **Balance perfection with pragmatism** - good enough today vs. perfect tomorrow
+2. **Document decisions** - capture rationale for future reference
+3. **Share knowledge proactively** - don't silo expertise
+4. **Stay current** - technology and standards evolve rapidly
+5. **Consider context** - standards should fit the problem and organization
+6. **Focus on risk** - prioritize based on impact and likelihood
+7. **Enable the team** - provide guidance without blocking progress

.claude/workflows/cli-templates/planning-roles/user-researcher.md

@@ -1,119 +0,0 @@
----
-name: user-researcher
-description: User behavior analysis, research methodology, and user-centered design insights
----
-
-# User Researcher Planning Template
-
-You are a **User Researcher** specializing in user behavior analysis, research methodology, and user-centered design insights.
-
-## Your Role & Responsibilities
-
-**Primary Focus**: User behavior analysis, research strategy, data-driven user insights, and user experience validation
-
-**Core Responsibilities**:
-- User research methodology design and planning
-- User persona development and user journey mapping
-- User testing strategy and usability evaluation planning
-- Behavioral analysis and user insight synthesis
-- Research data collection and analysis planning
-- User feedback integration and recommendation development
-
-**Does NOT Include**: Conducting actual user interviews, implementing UI changes, writing research tools
-
-## Planning Document Structure
-
-Generate a comprehensive user research planning document with the following structure:
-
-### 1. Research Objectives & Strategy
-- **Research Goals**: Primary research questions and hypotheses
-- **User Segments**: Target user groups and demographic analysis
-- **Research Methodology**: Qualitative vs quantitative approaches
-- **Success Criteria**: Measurable research outcomes and insights
-
-### 2. User Analysis & Personas
-- **Current User Base**: Existing user behavior patterns and characteristics
-- **User Personas**: Detailed primary, secondary, and edge case personas
-- **Behavioral Patterns**: User workflows, pain points, and motivations
-- **User Needs Hierarchy**: Primary, secondary, and latent user needs
-
-### 3. Research Methodology & Approach
-- **Research Methods**: Interviews, surveys, usability testing, analytics review
-- **Data Collection Strategy**: Quantitative metrics and qualitative insights
-- **Sample Size & Demographics**: Participant recruitment and representation
-- **Research Timeline**: Phases, milestones, and deliverable schedule
-
-### 4. User Journey & Experience Mapping
-- **Current State Journey**: Existing user flows and touchpoints
-- **Pain Point Analysis**: Friction areas and user frustrations
-- **Opportunity Identification**: Improvement areas and enhancement opportunities
-- **Future State Vision**: Desired user experience and journey optimization
-
-### 5. Usability & Testing Strategy
-- **Usability Testing Plan**: Test scenarios, tasks, and success metrics
-- **A/B Testing Strategy**: Hypothesis-driven testing and validation approach
-- **Accessibility Evaluation**: Inclusive design and accessibility considerations
-- **Performance Impact**: User experience impact of technical decisions
-
-### 6. Insights & Recommendations
-- **Behavioral Insights**: Key findings about user behavior and preferences
-- **Design Implications**: User research impact on design decisions
-- **Feature Prioritization**: User-driven feature importance and sequencing
-- **Continuous Research**: Ongoing user feedback and iteration planning
-
-## Key Questions to Address
-
-1. **User Understanding**: What are users really trying to accomplish?
-2. **Behavior Patterns**: How do users currently interact with similar systems?
-3. **Pain Points**: What are the biggest user frustrations and barriers?
-4. **Value Perception**: What do users value most in this experience?
-5. **Validation Approach**: How will we validate our assumptions about users?
-
-## Output Requirements
-
-- **User Persona Documents**: Detailed user profiles with behavioral insights
-- **Journey Maps**: Visual representation of user experience and touchpoints
-- **Research Plan**: Comprehensive methodology and timeline for user research
-- **Testing Strategy**: Usability testing and validation approach
-- **Insight Reports**: Actionable recommendations based on user research findings
-
-## Brainstorming Documentation Files to Create
-
-When conducting brainstorming sessions, create the following files:
-
-### Individual Role Analysis File: `user-researcher-analysis.md`
-```markdown
-# User Researcher Analysis: [Topic]
-
-## User Behavior Analysis
-- Current user behavior patterns and preferences
-- Pain points and friction areas in user experience
-- User motivation and goal alignment
-
-## Research Methodology Assessment
-- Recommended research approaches and methods
-- User testing scenarios and validation strategies
-- Data collection and analysis frameworks
-
-## User Experience Impact
-- UX implications for proposed solutions
-- Accessibility and inclusivity considerations
-- User adoption and learning curve assessment
-
-## Persona and Journey Insights
-- Relevant user personas and their needs
-- Critical user journey touchpoints
-- Behavioral pattern implications
-
-## Recommendations
-- User-centered design recommendations
-- Research priorities and validation approaches
-- UX optimization opportunities
-```
-
-### Session Contribution Template
-For role-specific contributions to broader brainstorming sessions, provide:
-- User behavior insights for each proposed solution
-- Usability assessment and user experience implications
-- Research validation recommendations
-- Accessibility and inclusion considerations

.claude/workflows/cli-templates/planning-roles/ux-expert.md

@@ -0,0 +1,240 @@
+---
+name: ux-expert
+description: User experience optimization, usability testing, and interaction design patterns
+---
+
+# UX Expert Planning Template
+
+You are a **UX Expert** specializing in user experience optimization, usability testing, and interaction design patterns.
+
+## Your Role & Responsibilities
+
+**Primary Focus**: User experience optimization, interaction design, usability testing, and design system consistency
+
+**Core Responsibilities**:
+- User experience optimization and journey mapping
+- Interaction design patterns and microinteractions
+- Usability testing strategies and validation
+- Design system governance and consistency
+- Accessibility compliance (WCAG 2.1 AA/AAA)
+- User research synthesis and insights application
+- Information architecture and navigation design
+
+**Does NOT Include**: Visual branding, graphic design, production frontend code
+
+## Planning Document Structure
+
+Generate a comprehensive UX Expert planning document with the following structure:
+
+### 1. User Experience Strategy
+- **UX Vision**: Experience goals and quality attributes
+- **User-Centered Design Approach**: Research-driven methodology
+- **Experience Principles**: Core guidelines and decision criteria
+- **Success Metrics**: Usability KPIs and experience measurements
+
+### 2. User Research & Insights
+- **User Personas**: Behavioral patterns and mental models
+- **User Needs Analysis**: Pain points, goals, and motivations
+- **Competitive UX Analysis**: Industry patterns and best practices
+- **User Journey Mapping**: Touchpoints, emotions, and opportunities
+
+### 3. Interaction Design
+- **Interaction Patterns**: Navigation, forms, feedback, and transitions
+- **Microinteractions**: Hover states, loading indicators, error handling
+- **Gesture Design**: Touch, swipe, drag-and-drop interactions
+- **State Management**: Empty states, loading states, error states
+- **Feedback Mechanisms**: Visual, auditory, and haptic feedback
+
+### 4. Information Architecture
+- **Content Structure**: Hierarchy, grouping, and relationships
+- **Navigation Systems**: Primary, secondary, and contextual navigation
+- **Search & Findability**: Search patterns and content discovery
+- **Taxonomy & Labeling**: Terminology and information organization
+
+### 5. Usability & Accessibility
+- **Usability Heuristics**: Nielsen's 10 principles application
+- **Accessibility Standards**: WCAG compliance and inclusive design
+- **Cognitive Load Optimization**: Simplification and clarity strategies
+- **Error Prevention**: Constraints, confirmations, and safeguards
+- **Learnability**: Onboarding, progressive disclosure, and help systems
+
+### 6. Design System & Patterns
+- **Component Patterns**: Reusable interaction patterns
+- **Design Tokens**: Spacing, typography, color for consistency
+- **Pattern Library**: Documented interaction patterns
+- **Design System Governance**: Usage guidelines and quality standards
+
+### 7. Usability Testing Strategy
+- **Testing Methods**: Moderated, unmoderated, A/B testing
+- **Test Scenarios**: Critical user flows and edge cases
+- **Success Criteria**: Task completion, error rates, satisfaction
+- **Iteration Plan**: Feedback incorporation and validation cycles
+
+## UX Analysis Framework
+
+### Experience Quality Attributes
+- **Usability**: Easy to learn and efficient to use
+- **Accessibility**: Inclusive for all users and abilities
+- **Desirability**: Aesthetically pleasing and engaging
+- **Findability**: Easy to navigate and discover content
+- **Credibility**: Trustworthy and reliable
+- **Usefulness**: Solves user problems effectively
+
+### Interaction Design Principles
+- **Clarity**: Clear purpose and obvious next steps
+- **Consistency**: Predictable patterns and behaviors
+- **Feedback**: Immediate response to user actions
+- **Efficiency**: Minimize steps to complete tasks
+- **Forgiveness**: Easy error recovery and undo
+- **Control**: User agency and autonomy
+
+### Usability Heuristics (Nielsen)
+1. Visibility of system status
+2. Match between system and real world
+3. User control and freedom
+4. Consistency and standards
+5. Error prevention
+6. Recognition rather than recall
+7. Flexibility and efficiency of use
+8. Aesthetic and minimalist design
+9. Help users recognize, diagnose, and recover from errors
+10. Help and documentation
+
+## Usability Testing Techniques
+
+### Methods
+- **Moderated Usability Testing**: Facilitator-guided sessions
+- **Unmoderated Remote Testing**: Asynchronous user testing
+- **A/B Testing**: Variant comparison for optimization
+- **Eye Tracking**: Visual attention analysis
+- **First Click Testing**: Navigation effectiveness
+- **Card Sorting**: Information architecture validation
+
+### Metrics
+- **Task Success Rate**: Percentage of completed tasks
+- **Time on Task**: Efficiency measurement
+- **Error Rate**: Mistakes and recovery actions
+- **Satisfaction (SUS)**: System Usability Scale score
+- **Net Promoter Score (NPS)**: User recommendation likelihood
+
+## Accessibility Guidelines
+
+### WCAG 2.1 AA Compliance
+- **Perceivable**: Information presentable to all users
+- **Operable**: Interface functional for all input methods
+- **Understandable**: Clear information and operation
+- **Robust**: Compatible with assistive technologies
+
+### Key Accessibility Patterns
+- Semantic HTML and ARIA labels
+- Keyboard navigation and focus management
+- Color contrast ratios (4.5:1 minimum)
+- Text alternatives for non-text content
+- Responsive and scalable interfaces
+- Consistent navigation and identification
+
+## Output Format
+
+Create comprehensive UX Expert deliverables:
+
+1. **Planning Document**: `ux-expert-analysis.md`
+   - UX strategy and user research insights
+   - Interaction design patterns and information architecture
+   - Usability and accessibility planning
+   - Testing strategy and validation approach
+
+2. **UX Artifacts**:
+   - User journey maps and flow diagrams
+   - Interaction pattern specifications
+   - Usability test plans and scenarios
+   - Accessibility audit checklists
+
+## Brainstorming Documentation Files to Create
+
+When conducting brainstorming sessions, create the following files:
+
+### Individual Role Analysis File: `ux-expert-analysis.md`
+```markdown
+# UX Expert Analysis: [Topic]
+
+## User Experience Assessment
+- User journey implications and touchpoints
+- Interaction complexity and cognitive load
+- Usability challenges and friction points
+- Experience quality attributes and goals
+
+## Interaction Design Analysis
+- Interaction patterns and microinteractions
+- Navigation structure and information architecture
+- State management and feedback mechanisms
+- Gesture and input method considerations
+
+## Usability & Accessibility Evaluation
+- Usability heuristics application
+- WCAG compliance requirements and challenges
+- Cognitive load optimization opportunities
+- Error prevention and recovery strategies
+
+## Design System Integration
+- Component pattern requirements
+- Interaction consistency and standards
+- Design token implications
+- Pattern library extensions needed
+
+## Testing & Validation Strategy
+- Usability testing approach and scenarios
+- Success metrics and KPIs
+- A/B testing opportunities
+- Iteration and refinement plan
+
+## Recommendations
+- UX optimization strategies and patterns
+- Interaction design improvements
+- Accessibility enhancements
+- Usability testing priorities
+```
+
+### Session Contribution Template
+For role-specific contributions to broader brainstorming sessions, provide:
+- User experience implications and journey analysis
+- Interaction design patterns and recommendations
+- Usability and accessibility considerations
+- Testing strategy and validation approach
+
+## Design Pattern Library
+
+### Common Interaction Patterns
+- **Progressive Disclosure**: Reveal complexity gradually
+- **Inline Editing**: Direct manipulation of content
+- **Contextual Actions**: Actions near relevant content
+- **Smart Defaults**: Intelligent pre-filled values
+- **Undo/Redo**: Easy error recovery
+- **Guided Workflows**: Step-by-step processes
+
+### Microinteraction Examples
+- Button press feedback (scale, shadow)
+- Loading spinners and progress indicators
+- Form validation (inline, real-time)
+- Hover effects and tooltips
+- Drag-and-drop visual feedback
+- Success/error notifications
+
+## Key Success Factors
+
+1. **User-Centered Focus**: Design decisions based on user needs
+2. **Iterative Testing**: Regular validation with real users
+3. **Accessibility First**: Inclusive design from the start
+4. **Consistency**: Predictable patterns across the experience
+5. **Clear Feedback**: Users always know system status
+6. **Error Prevention**: Minimize mistakes through good design
+7. **Performance**: Fast, responsive interactions
+
+## Important Reminders
+
+1. **Test with real users** - assumptions are not validation
+2. **Accessibility is not optional** - design inclusively from the start
+3. **Measure usability** - use quantitative and qualitative data
+4. **Iterate based on feedback** - continuous improvement cycle
+5. **Document patterns** - create reusable interaction library
+6. **Consider edge cases** - error states, empty states, loading states
+7. **Balance innovation with familiarity** - leverage existing mental models

.claude/workflows/conceptual-planning-agent.md

@@ -1,189 +0,0 @@
-# Conceptual Planning Agent
-
-**Agent Definition**: See @~/.claude/agents/conceptual-planning-agent.md
-**Integration Principles**: See @~/.claude/workflows/brainstorming-principles.md
-
-## Purpose
-Agent for executing single-role conceptual planning and brainstorming analysis based on assigned perspectives.
-
-## Core Capabilities
-- **Single-Role Analysis** → Deep analysis from one assigned role perspective
-- **Context Integration** → Incorporate user requirements and constraints
-- **Documentation Generation** → Create role-specific analysis outputs
-- **Framework Application** → Apply techniques from @~/.claude/workflows/brainstorming-framework.md
-
-## Execution Patterns
-
-### Agent Invocation
-This agent is called by role-specific brainstorm commands with:
-- **ASSIGNED_ROLE**: The specific role to embody
-- **Topic**: Challenge or opportunity to analyze
-- **Context**: User requirements and constraints
-- **Output Location**: Where to save analysis files
-
-### Execution Flow
-See @~/.claude/workflows/brainstorming-framework.md for detailed execution patterns and techniques.
-
-### Role References
-
-**Available Roles**: Each role has its own command file with detailed definitions:
-- `business-analyst` - See `.claude/commands/workflow/brainstorm/business-analyst.md`
-- `data-architect` - See `.claude/commands/workflow/brainstorm/data-architect.md`
-- `feature-planner` - See `.claude/commands/workflow/brainstorm/feature-planner.md`
-- `innovation-lead` - See `.claude/commands/workflow/brainstorm/innovation-lead.md`
-- `product-manager` - See `.claude/commands/workflow/brainstorm/product-manager.md`
-- `security-expert` - See `.claude/commands/workflow/brainstorm/security-expert.md`
-- `system-architect` - See `.claude/commands/workflow/brainstorm/system-architect.md`
-- `ui-designer` - See `.claude/commands/workflow/brainstorm/ui-designer.md`
-- `user-researcher` - See `.claude/commands/workflow/brainstorm/user-researcher.md`
-
-### Creative Techniques
-
-For detailed creative techniques including SCAMPER, Six Thinking Hats, and other methods, see:
-@~/.claude/workflows/brainstorming-framework.md#creative-techniques
-
-### Execution Modes
-
-For detailed execution modes (Creative, Analytical, Strategic), see:
-@~/.claude/workflows/brainstorming-framework.md#execution-modes
-
-## Documentation Standards
-
-### Session Summary Generation
-Generate comprehensive session documentation including:
-- Session metadata and configuration
-- Challenge definition and scope
-- Key insights and patterns
-- Generated ideas with descriptions
-- Perspective analysis from each role
-- Evaluation and prioritization
-- Recommendations and next steps
-
-### Idea Documentation
-For each significant idea, create detailed documentation:
-- Concept description and core mechanism
-- Multi-perspective analysis and implications
-- Feasibility assessment (technical, resource, timeline)
-- Impact potential (user, business, technical)
-- Implementation considerations and prerequisites
-- Success metrics and validation approach
-- Risk assessment and mitigation strategies
-
-### Integration Preparation
-When brainstorming integrates with workflows:
-- Synthesize requirements suitable for planning phase
-- Prioritize solutions by feasibility and impact
-- Prepare structured input for workflow systems
-- Maintain traceability between brainstorming and implementation
-
-## Output Format Standards
-
-### Brainstorming Session Output
-```
-BRAINSTORMING_SUMMARY: [Comprehensive session overview]
-CHALLENGE_DEFINITION: [Clear problem space definition]
-KEY_INSIGHTS: [Major discoveries and patterns]
-IDEA_INVENTORY: [Structured list of all generated ideas]
-TOP_CONCEPTS: [5 most promising solutions with analysis]
-PERSPECTIVE_SYNTHESIS: [Integration of role-based insights]
-FEASIBILITY_ASSESSMENT: [Technical and resource evaluation]
-IMPACT_ANALYSIS: [Expected outcomes and benefits]
-RECOMMENDATIONS: [Prioritized next steps and actions]
-WORKFLOW_INTEGRATION: [If applicable, workflow handoff preparation]
-```
-
-### Multi-Role Analysis Output
-```
-ROLE_COORDINATION: [How perspectives were integrated]
-PERSPECTIVE_INSIGHTS: [Key insights from each role]
-SYNTHESIS_RESULTS: [Combined perspective analysis]
-CONFLICT_RESOLUTION: [How role conflicts were addressed]
-COMPREHENSIVE_COVERAGE: [Confirmation all aspects considered]
-```
-
-## Quality Standards
-
-### Effective Session Facilitation
-- **Clear Structure** → Follow defined phases and maintain session flow
-- **Inclusive Participation** → Ensure all perspectives are heard and valued  
-- **Creative Environment** → Maintain judgment-free ideation atmosphere
-- **Productive Tension** → Balance creativity with practical constraints
-- **Actionable Outcomes** → Generate concrete next steps and recommendations
-
-### Perspective Integration
-- **Authentic Representation** → Accurately channel each role's mental models
-- **Balanced Coverage** → Give appropriate attention to all perspectives
-- **Constructive Synthesis** → Combine insights into stronger solutions
-- **Conflict Navigation** → Address perspective tensions constructively
-- **Comprehensive Analysis** → Ensure no critical aspects are overlooked
-
-### Documentation Quality
-- **Structured Capture** → Organize insights and ideas systematically
-- **Clear Communication** → Present complex ideas in accessible format
-- **Decision Support** → Provide frameworks for evaluating options
-- **Implementation Ready** → Prepare outputs for next development phases
-- **Traceability** → Maintain clear links between ideas and analysis
-
-## Dynamic Role Definition Loading
-
-### Role-Based Planning Template Integration
-The conceptual planning agent dynamically loads role-specific capabilities using the planning template system:
-
-**Dynamic Role Loading Process:**
-1. **Role Identification** → Receive required role(s) from brainstorming coordination command
-2. **Template Loading** → Use Bash tool to execute `~/.claude/scripts/plan-executor.sh [role]`
-3. **Capability Integration** → Apply loaded role template to current brainstorming context
-4. **Perspective Analysis** → Conduct analysis from the specified role perspective
-5. **Multi-Role Synthesis** → When multiple roles specified, integrate perspectives coherently
-
-**Supported Roles:**
-- `product-manager`, `system-architect`, `ui-designer`, `data-architect`
-- `security-expert`, `user-researcher`, `business-analyst`, `innovation-lead`
-- `feature-planner`, `test-strategist`
-
-**Role Loading Example:**
-```
-For role "product-manager":
-1. Execute: Bash(~/.claude/scripts/plan-executor.sh product-manager)
-2. Receive: Product Manager Planning Template with responsibilities and focus areas
-3. Apply: Template guidance to current brainstorming topic
-4. Generate: Analysis from product management perspective
-```
-
-**Multi-Role Coordination:**
-When conducting multi-perspective brainstorming:
-1. Load each required role template sequentially
-2. Apply each perspective to the brainstorming topic
-3. Synthesize insights across all loaded perspectives
-4. Identify convergent themes and resolve conflicts
-5. Generate integrated recommendations
-
-## Brainstorming Documentation Creation
-
-### Mandatory File Creation Requirements
-Following @~/.claude/workflows/brainstorming-principles.md, the conceptual planning agent MUST create structured documentation for all brainstorming sessions.
-
-**Role-Specific Documentation**: Each role template loaded via plan-executor.sh contains its specific documentation requirements and file creation instructions.
-
-### File Creation Protocol
-1. **Load Role Requirements**: When loading each role template, extract the "Brainstorming Documentation Files to Create" section
-2. **Create Role Analysis Files**: Generate the specific analysis files as defined by each loaded role (e.g., `product-manager-analysis.md`)
-3. **Follow Role Templates**: Each role specifies its exact file structure, naming convention, and content template
-
-### Integration with Brainstorming Principles
-
-**Must Follow Brainstorming Modes:**
-- **Creative Mode**: Apply SCAMPER, Six Thinking Hats, divergent thinking
-- **Analytical Mode**: Use root cause analysis, data-driven insights, logical frameworks
-- **Strategic Mode**: Apply systems thinking, strategic frameworks, scenario planning
-
-**Quality Standards Compliance:**
-- **Clear Structure**: Follow defined phases (Explore → Ideate → Converge → Document)
-- **Diverse Perspectives**: Ensure all loaded roles contribute unique insights
-- **Judgment-Free Ideation**: Encourage wild ideas during creative phases
-- **Actionable Outputs**: Generate concrete next steps and decision frameworks
-
-### File Creation Tools
-The conceptual planning agent has access to Write, MultiEdit, and other file creation tools to generate the complete brainstorming documentation structure.
-
-This conceptual planning agent provides comprehensive brainstorming and strategic analysis capabilities with dynamic role-based perspectives, mandatory documentation creation following brainstorming principles, and full integration with the planning template system and workflow management system.

.claude/workflows/doc_agent.md

@@ -1,255 +0,0 @@
-# Documentation Agent
-
-## Agent Overview
-Specialized agent for hierarchical documentation generation with bottom-up analysis approach.
-
-## Core Capabilities
-- **Modular Analysis**: Analyze individual modules and components
-- **Hierarchical Synthesis**: Build documentation from modules to system level
-- **Multi-tool Integration**: Combine Agent tasks, CLI tools, and direct analysis
-- **Progress Tracking**: Use TodoWrite throughout the documentation process
-
-## Analysis Strategy
-
-### Two-Level Hierarchy
-1. **Level 1 (Module)**: Individual component/module documentation
-2. **Level 2 (System)**: Integrated system-wide documentation
-
-### Bottom-Up Process
-1. **Module Discovery**: Identify all modules/components in the system
-2. **Module Analysis**: Deep dive into each module individually
-3. **Module Documentation**: Generate detailed module docs
-4. **Integration Analysis**: Analyze relationships between modules
-5. **System Synthesis**: Create unified system documentation
-
-## Tool Selection Strategy
-
-### For Module Analysis (Simple, focused scope)
-- **CLI Tools**: Direct Gemini/Codex commands for individual modules
-- **File Patterns**: Focused file sets per module
-- **Fast Processing**: Quick analysis of contained scope
-
-### For System Integration (Complex, multi-module)
-- **Agent Tasks**: Complex analysis requiring multiple tools
-- **Cross-module Analysis**: Relationship mapping between modules
-- **Synthesis Tasks**: Combining multiple module analyses
-
-## Documentation Structure
-
-### Module Level (Level 1)
-```
-.workflow/docs/modules/
-├── [module-name]/
-│   ├── overview.md        # Module overview
-│   ├── api.md            # Module APIs
-│   ├── dependencies.md   # Module dependencies
-│   └── examples.md       # Usage examples
-```
-
-### System Level (Level 2)
-```
-.workflow/docs/
-├── README.md             # Complete system overview
-├── architecture/
-│   ├── system-design.md  # High-level architecture
-│   ├── module-map.md     # Module relationships
-│   ├── data-flow.md      # System data flow
-│   └── tech-stack.md     # Technology decisions
-└── api/
-    ├── unified-api.md    # Complete API documentation
-    └── openapi.yaml      # OpenAPI specification
-```
-
-## Process Flow Templates
-
-### Phase 1: Module Discovery & Todo Setup
-```json
-{
-  "step": "module_discovery",
-  "method": "cli",
-  "command": "find src/ -type d -name '*' | grep -v node_modules | head -20",
-  "purpose": "Identify all modules for documentation",
-  "todo_action": "create_module_todos"
-}
-```
-
-### Phase 2: Module Analysis (Parallel)
-```json
-{
-  "step": "module_analysis",
-  "method": "cli_parallel",
-  "pattern": "per_module",
-  "command_template": "~/.claude/scripts/gemini-wrapper -p 'ANALYZE_MODULE: {module_path}'",
-  "purpose": "Analyze each module individually",
-  "todo_action": "track_module_progress"
-}
-```
-
-### Phase 3: Module Documentation (Parallel)
-```json
-{
-  "step": "module_documentation",
-  "method": "cli_parallel",
-  "pattern": "per_module",
-  "command_template": "codex --full-auto exec 'DOCUMENT_MODULE: {module_path}' -s danger-full-access",
-  "purpose": "Generate documentation for each module",
-  "todo_action": "mark_module_complete"
-}
-```
-
-### Phase 4: System Integration (Agent)
-```json
-{
-  "step": "system_integration",
-  "method": "agent",
-  "agent_type": "general-purpose",
-  "purpose": "Analyze cross-module relationships and create system view",
-  "todo_action": "track_integration_progress"
-}
-```
-
-### Phase 5: System Documentation (Agent)
-```json
-{
-  "step": "system_documentation",
-  "method": "agent",
-  "agent_type": "general-purpose",
-  "purpose": "Generate unified system documentation",
-  "todo_action": "mark_system_complete"
-}
-```
-
-## CLI Command Templates
-
-### Module Analysis Template
-```bash
-~/.claude/scripts/gemini-wrapper -p "
-PURPOSE: Analyze individual module for documentation
-TASK: Deep analysis of module structure, APIs, and dependencies
-CONTEXT: @{{{module_path}}/**/*}
-EXPECTED: Module analysis for documentation generation
-
-MODULE ANALYSIS RULES:
-1. Module Scope Definition:
-   - Identify module boundaries and entry points
-   - Map internal file organization
-   - Extract module's primary purpose and responsibilities
-
-2. API Surface Analysis:
-   - Identify exported functions, classes, and interfaces
-   - Document public API contracts
-   - Map input/output types and parameters
-
-3. Dependency Analysis:
-   - Extract internal dependencies within module
-   - Identify external dependencies from other modules
-   - Map configuration and environment dependencies
-
-4. Usage Pattern Analysis:
-   - Find example usage within codebase
-   - Identify common patterns and utilities
-   - Document error handling approaches
-
-OUTPUT FORMAT:
-- Module overview with clear scope definition
-- API documentation with types and examples
-- Dependency map with clear relationships
-- Usage examples from actual codebase
-" 
-```
-
-### Module Documentation Template
-```bash
-codex --full-auto exec "
-PURPOSE: Generate comprehensive module documentation
-TASK: Create detailed documentation for analyzed module
-CONTEXT: Module analysis results from Gemini
-EXPECTED: Complete module documentation in .workflow/docs/modules/{module_name}/
-
-DOCUMENTATION GENERATION RULES:
-1. Create module directory structure
-2. Generate overview.md with module purpose and architecture
-3. Create api.md with detailed API documentation
-4. Generate dependencies.md with dependency analysis
-5. Create examples.md with practical usage examples
-6. Ensure consistent formatting and cross-references
-" -s danger-full-access 
-```
-
-## Agent Task Templates
-
-### System Integration Agent Task
-```json
-{
-  "description": "Analyze cross-module relationships",
-  "prompt": "You are analyzing a software system to understand relationships between modules. Your task is to:\n\n1. Read all module documentation from .workflow/docs/modules/\n2. Identify integration points and data flow between modules\n3. Map system-wide architecture patterns\n4. Create unified view of system structure\n\nAnalyze the modules and create:\n- Module relationship map\n- System data flow documentation\n- Integration points analysis\n- Architecture pattern identification\n\nUse TodoWrite to track your progress through the analysis.",
-  "subagent_type": "general-purpose"
-}
-```
-
-### System Documentation Agent Task
-```json
-{
-  "description": "Generate unified system documentation",
-  "prompt": "You are creating comprehensive system documentation based on module analyses. Your task is to:\n\n1. Synthesize information from .workflow/docs/modules/ \n2. Create unified system architecture documentation\n3. Generate complete API documentation\n4. Create system overview and navigation\n\nGenerate:\n- README.md with system overview\n- architecture/ directory with system design docs\n- api/ directory with unified API documentation\n- Cross-references between all documentation\n\nUse TodoWrite to track documentation generation progress.",
-  "subagent_type": "general-purpose"
-}
-```
-
-## Progress Tracking Templates
-
-### Module Todo Structure
-```json
-{
-  "content": "Analyze {module_name} module",
-  "activeForm": "Analyzing {module_name} module",
-  "status": "pending"
-}
-```
-
-### Integration Todo Structure
-```json
-{
-  "content": "Integrate module analyses into system view",
-  "activeForm": "Integrating module analyses",
-  "status": "pending"
-}
-```
-
-### Documentation Todo Structure
-```json
-{
-  "content": "Generate unified system documentation",
-  "activeForm": "Generating system documentation",
-  "status": "pending"
-}
-```
-
-## Error Handling & Recovery
-
-### Module Analysis Failures
-- Skip failed modules with warning
-- Continue with successful modules
-- Retry failed modules with different approach
-
-### Integration Failures
-- Fall back to manual integration
-- Use partial results where available
-- Generate documentation with known limitations
-
-### Documentation Generation Failures
-- Generate partial documentation
-- Include clear indicators of incomplete sections
-- Provide recovery instructions
-
-## Quality Assurance
-
-### Module Documentation Quality
-- Verify all modules have complete documentation
-- Check API documentation completeness
-- Validate examples and cross-references
-
-### System Documentation Quality
-- Ensure module integration is complete
-- Verify system overview accuracy
-- Check documentation navigation and links

CHANGELOG.md

@@ -5,6 +5,67 @@ All notable changes to Claude Code Workflow (CCW) will be documented in this fil
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.0.1] - 2025-10-01
+
+### 🔧 Command Updates
+
+#### Changed
+- **Brainstorming Roles**: Removed `test-strategist` and `user-researcher` roles
+  - `test-strategist` functionality integrated into automated test generation (`/workflow:test-gen`)
+  - `user-researcher` functionality consolidated into `ux-expert` role
+- **Available Roles**: Updated to 8 core roles for focused, efficient brainstorming
+  - 🏗️ System Architect
+  - 🗄️ Data Architect
+  - 🎓 Subject Matter Expert
+  - 📊 Product Manager
+  - 📋 Product Owner
+  - 🏃 Scrum Master
+  - 🎨 UI Designer
+  - 💫 UX Expert
+
+### 📚 Documentation
+
+#### Improved
+- **README Optimization**: Streamlined README.md and README_CN.md by 81% (from ~750 lines to ~140 lines)
+- **Better Structure**: Reorganized content with clearer sections and improved navigation
+- **Quick Start Guide**: Added immediate usability guide for new users
+- **Simplified Command Reference**: Consolidated command tables for easier reference
+- **Maintained Essential Information**: Preserved all installation steps, badges, links, and critical functionality
+
+#### Benefits
+- **Faster Onboarding**: New users can get started in minutes with the Quick Start section
+- **Reduced Cognitive Load**: Less verbose documentation with focused, actionable information
+- **Consistent Bilingual Structure**: English and Chinese versions now have identical organization
+- **Professional Presentation**: Cleaner, more modern documentation format
+
+---
+
+## [3.0.0] - 2025-09-30
+
+### 🚀 Major Release - Unified CLI Command Structure
+
+This is a **breaking change release** introducing a unified CLI command structure.
+
+#### Added
+- **Unified CLI Commands**: New `/cli:*` command set consolidating all tool interactions
+- **Tool Selection Flag**: Use `--tool <gemini|qwen|codex>` to select AI tools
+- **Command Verification**: Comprehensive workflow guide and command validation
+- **MCP Tools Integration** *(Experimental)*: Enhanced codebase analysis through Model Context Protocol
+
+#### Changed
+- **BREAKING**: Tool-specific commands (`/gemini:*`, `/qwen:*`, `/codex:*`) deprecated
+- **Command Structure**: All CLI commands now use unified `/cli:*` prefix
+- **Default Tool**: Commands default to `gemini` when `--tool` flag not specified
+
+#### Migration
+| Old Command (v2) | New Command (v3.0.0) |
+|---|---|
+| `/gemini:analyze "..."` | `/cli:analyze "..."` |
+| `/qwen:analyze "..."` | `/cli:analyze "..." --tool qwen` |
+| `/codex:chat "..."` | `/cli:chat "..." --tool codex` |
+
+---
+
 ## [2.0.0] - 2025-09-28
 
 ### 🚀 Major Release - Architectural Evolution

Install-Claude.ps1

@@ -48,15 +48,17 @@
 #>
 
 param(
-    [ValidateSet("Global")]
-    [string]$InstallMode = "Global",
-    
+    [ValidateSet("Global", "Path")]
+    [string]$InstallMode = "",
+
+    [string]$TargetPath = "",
+
     [switch]$Force,
-    
+
     [switch]$NonInteractive,
-    
+
     [switch]$BackupAll,
-    
+
     [switch]$NoBackup
 )
 
@@ -95,13 +97,54 @@ function Write-ColorOutput {
     Write-Host $Message -ForegroundColor $Color
 }
 
+function Show-Banner {
+    Write-Host ""
+    # CLAUDE - Cyan color
+    Write-Host '  ______   __                            __                   ' -ForegroundColor Cyan
+    Write-Host ' /      \ |  \                          |  \                 ' -ForegroundColor Cyan
+    Write-Host '|  $$$$$$\| $$  ______   __    __   ____| $$  ______        ' -ForegroundColor Cyan
+    Write-Host '| $$   \$$| $$ |      \ |  \  |  \ /      $$ /      \       ' -ForegroundColor Cyan
+    Write-Host '| $$      | $$  \$$$$$$\| $$  | $$|  $$$$$$$|  $$$$$$\      ' -ForegroundColor Cyan
+    Write-Host '| $$   __ | $$ /      $$| $$  | $$| $$  | $$| $$    $$      ' -ForegroundColor Cyan
+    Write-Host '| $$__/  \| $$|  $$$$$$$| $$__/ $$| $$__| $$| $$$$$$$$      ' -ForegroundColor Cyan
+    Write-Host ' \$$    $$| $$ \$$    $$ \$$    $$ \$$    $$ \$$     \       ' -ForegroundColor Cyan
+    Write-Host '  \$$$$$$  \$$  \$$$$$$$  \$$$$$$   \$$$$$$$  \$$$$$$$        ' -ForegroundColor Cyan
+    Write-Host ""
+
+    # CODE - Green color
+    Write-Host ' ______                   __                  ' -ForegroundColor Green
+    Write-Host '/      \                 |  \                ' -ForegroundColor Green
+    Write-Host '|  $$$$$$\  ______    ____| $$  ______        ' -ForegroundColor Green
+    Write-Host '| $$   \$$ /      \  /      $$ /      \       ' -ForegroundColor Green
+    Write-Host '| $$      |  $$$$$$\|  $$$$$$$|  $$$$$$\      ' -ForegroundColor Green
+    Write-Host '| $$   __ | $$  | $$| $$  | $$| $$    $$      ' -ForegroundColor Green
+    Write-Host '| $$__/  \| $$__/ $$| $$__| $$| $$$$$$$$      ' -ForegroundColor Green
+    Write-Host ' \$$    $$ \$$    $$ \$$    $$ \$$     \      ' -ForegroundColor Green
+    Write-Host '  \$$$$$$   \$$$$$$   \$$$$$$$  \$$$$$$$       ' -ForegroundColor Green
+    Write-Host ""
+
+    # WORKFLOW - Yellow color
+    Write-Host '__       __                      __         ______   __                         ' -ForegroundColor Yellow
+    Write-Host '|  \  _  |  \                    |  \       /      \ |  \                        ' -ForegroundColor Yellow
+    Write-Host '| $$ / \ | $$  ______    ______  | $$   __ |  $$$$$$\| $$  ______   __   __   __ ' -ForegroundColor Yellow
+    Write-Host '| $$/  $\| $$ /      \  /      \ | $$  /  \| $$_  \$$| $$ /      \ |  \ |  \ |  \' -ForegroundColor Yellow
+    Write-Host '| $$  $$$\ $$|  $$$$$$\|  $$$$$$\| $$_/  $$| $$ \    | $$|  $$$$$$\| $$ | $$ | $$' -ForegroundColor Yellow
+    Write-Host '| $$ $$\$$\$$| $$  | $$| $$   \$$| $$   $$ | $$$$    | $$| $$  | $$| $$ | $$ | $$' -ForegroundColor Yellow
+    Write-Host '| $$$$  \$$$$| $$__/ $$| $$      | $$$$$$\ | $$      | $$| $$__/ $$| $$_/ $$_/ $$' -ForegroundColor Yellow
+    Write-Host '| $$$    \$$$ \$$    $$| $$      | $$  \$$\| $$      | $$ \$$    $$ \$$   $$   $$' -ForegroundColor Yellow
+    Write-Host ' \$$      \$$  \$$$$$$  \$$       \$$   \$$ \$$       \$$  \$$$$$$   \$$$$$\$$$$' -ForegroundColor Yellow
+    Write-Host ""
+}
+
 function Show-Header {
-    Write-ColorOutput "==== $ScriptName v$Version ====" $ColorInfo
-    Write-ColorOutput "========================================================" $ColorInfo
+    Show-Banner
+    Write-ColorOutput "    $ScriptName v$Version" $ColorInfo
+    Write-ColorOutput "    Unified workflow system with comprehensive coordination" $ColorInfo
+    Write-ColorOutput "========================================================================" $ColorInfo
     if ($NoBackup) {
-        Write-ColorOutput "WARNING: Backup disabled - existing files will be overwritten without backup!" $ColorWarning
+        Write-ColorOutput "WARNING: Backup disabled - existing files will be overwritten!" $ColorWarning
     } else {
-        Write-ColorOutput "Auto-backup enabled - existing files will be backed up before replacement" $ColorSuccess
+        Write-ColorOutput "Auto-backup enabled - existing files will be backed up" $ColorSuccess
     }
     Write-Host ""
 }
@@ -133,18 +176,130 @@ function Test-Prerequisites {
     return $true
 }
 
+function Get-UserChoiceWithArrows {
+    param(
+        [string]$Prompt,
+        [string[]]$Options,
+        [int]$DefaultIndex = 0
+    )
+
+    if ($NonInteractive) {
+        Write-ColorOutput "Non-interactive mode: Using default '$($Options[$DefaultIndex])'" $ColorInfo
+        return $Options[$DefaultIndex]
+    }
+
+    # Test if we can use console features (interactive terminal)
+    $canUseConsole = $true
+    try {
+        $null = [Console]::CursorVisible
+        $null = $Host.UI.RawUI.ReadKey
+    }
+    catch {
+        $canUseConsole = $false
+    }
+
+    # Fallback to simple numbered menu if console not available
+    if (-not $canUseConsole) {
+        Write-ColorOutput "Arrow navigation not available in this environment. Using numbered menu." $ColorWarning
+        return Get-UserChoice -Prompt $Prompt -Options $Options -Default $Options[$DefaultIndex]
+    }
+
+    $selectedIndex = $DefaultIndex
+    $cursorVisible = $true
+
+    try {
+        $cursorVisible = [Console]::CursorVisible
+        [Console]::CursorVisible = $false
+    }
+    catch {
+        # Silently continue if cursor control fails
+    }
+
+    try {
+        Write-Host ""
+        Write-ColorOutput $Prompt $ColorPrompt
+        Write-Host ""
+
+        while ($true) {
+            # Display options
+            for ($i = 0; $i -lt $Options.Count; $i++) {
+                $prefix = if ($i -eq $selectedIndex) { "  > " } else { "    " }
+                $color = if ($i -eq $selectedIndex) { $ColorSuccess } else { "White" }
+
+                # Clear line and write option
+                Write-Host "`r$prefix$($Options[$i])".PadRight(80) -ForegroundColor $color
+            }
+
+            Write-Host ""
+            Write-Host "  Use " -NoNewline -ForegroundColor DarkGray
+            Write-Host "UP/DOWN" -NoNewline -ForegroundColor Yellow
+            Write-Host " arrows to navigate, " -NoNewline -ForegroundColor DarkGray
+            Write-Host "ENTER" -NoNewline -ForegroundColor Yellow
+            Write-Host " to select, or type " -NoNewline -ForegroundColor DarkGray
+            Write-Host "1-$($Options.Count)" -NoNewline -ForegroundColor Yellow
+            Write-Host "" -ForegroundColor DarkGray
+
+            # Read key
+            $key = $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
+
+            # Handle arrow keys
+            if ($key.VirtualKeyCode -eq 38) {
+                # Up arrow
+                $selectedIndex = if ($selectedIndex -gt 0) { $selectedIndex - 1 } else { $Options.Count - 1 }
+            }
+            elseif ($key.VirtualKeyCode -eq 40) {
+                # Down arrow
+                $selectedIndex = if ($selectedIndex -lt ($Options.Count - 1)) { $selectedIndex + 1 } else { 0 }
+            }
+            elseif ($key.VirtualKeyCode -eq 13) {
+                # Enter key
+                Write-Host ""
+                return $Options[$selectedIndex]
+            }
+            elseif ($key.Character -match '^\d$') {
+                # Number key
+                $num = [int]::Parse($key.Character)
+                if ($num -ge 1 -and $num -le $Options.Count) {
+                    Write-Host ""
+                    return $Options[$num - 1]
+                }
+            }
+
+            # Move cursor back up to redraw menu
+            $linesToMove = $Options.Count + 2
+            try {
+                for ($i = 0; $i -lt $linesToMove; $i++) {
+                    [Console]::SetCursorPosition(0, [Console]::CursorTop - 1)
+                }
+            }
+            catch {
+                # If cursor positioning fails, just continue
+                break
+            }
+        }
+    }
+    finally {
+        try {
+            [Console]::CursorVisible = $cursorVisible
+        }
+        catch {
+            # Silently continue if cursor control fails
+        }
+    }
+}
+
 function Get-UserChoice {
     param(
         [string]$Prompt,
         [string[]]$Options,
         [string]$Default = $null
     )
-    
+
     if ($NonInteractive -and $Default) {
         Write-ColorOutput "Non-interactive mode: Using default '$Default'" $ColorInfo
         return $Default
     }
-    
+
     Write-ColorOutput $Prompt $ColorPrompt
     for ($i = 0; $i -lt $Options.Count; $i++) {
         if ($Default -and $Options[$i] -eq $Default) {
@@ -154,18 +309,18 @@ function Get-UserChoice {
         }
         Write-Host "  $($i + 1). $($Options[$i])$marker"
     }
-    
+
     do {
         $input = Read-Host "Please select (1-$($Options.Count))"
         if ([string]::IsNullOrWhiteSpace($input) -and $Default) {
             return $Default
         }
-        
+
         $index = $null
         if ([int]::TryParse($input, [ref]$index) -and $index -ge 1 -and $index -le $Options.Count) {
             return $Options[$index - 1]
         }
-        
+
         Write-ColorOutput "Invalid selection. Please enter a number between 1 and $($Options.Count)" $ColorWarning
     } while ($true)
 }
@@ -457,19 +612,19 @@ function Merge-DirectoryContents {
 
 function Install-Global {
     Write-ColorOutput "Installing Claude Code Workflow System globally..." $ColorInfo
-    
+
     # Determine user profile directory
     $userProfile = [Environment]::GetFolderPath("UserProfile")
     $globalClaudeDir = Join-Path $userProfile ".claude"
     $globalClaudeMd = Join-Path $globalClaudeDir "CLAUDE.md"
-    
+
     Write-ColorOutput "Global installation path: $userProfile" $ColorInfo
-    
+
     # Source paths
     $sourceDir = $PSScriptRoot
     $sourceClaudeDir = Join-Path $sourceDir ".claude"
     $sourceClaudeMd = Join-Path $sourceDir "CLAUDE.md"
-    
+
     # Create backup folder if needed (default behavior unless NoBackup is specified)
     $backupFolder = $null
     if (-not $NoBackup) {
@@ -485,15 +640,15 @@ function Install-Global {
             Write-ColorOutput "Backup folder created: $backupFolder" $ColorInfo
         }
     }
-    
+
     # Merge .claude directory contents (don't replace entire directory)
     Write-ColorOutput "Merging .claude directory contents..." $ColorInfo
     $claudeMerged = Merge-DirectoryContents -Source $sourceClaudeDir -Destination $globalClaudeDir -Description ".claude directory contents" -BackupFolder $backupFolder
-    
+
     # Handle CLAUDE.md file in .claude directory
     Write-ColorOutput "Installing CLAUDE.md to global .claude directory..." $ColorInfo
     $claudeMdInstalled = Copy-FileToDestination -Source $sourceClaudeMd -Destination $globalClaudeMd -Description "CLAUDE.md" -BackupFolder $backupFolder
-    
+
     if ($backupFolder -and (Test-Path $backupFolder)) {
         $backupFiles = Get-ChildItem $backupFolder -Recurse -File -ErrorAction SilentlyContinue
         if (-not $backupFiles -or ($backupFiles | Measure-Object).Count -eq 0) {
@@ -502,16 +657,207 @@ function Install-Global {
             Write-ColorOutput "Removed empty backup folder" $ColorInfo
         }
     }
-    
+
+    return $true
+}
+
+function Install-Path {
+    param(
+        [string]$TargetDirectory
+    )
+
+    Write-ColorOutput "Installing Claude Code Workflow System in hybrid mode..." $ColorInfo
+    Write-ColorOutput "Local path: $TargetDirectory" $ColorInfo
+
+    # Determine user profile directory for global files
+    $userProfile = [Environment]::GetFolderPath("UserProfile")
+    $globalClaudeDir = Join-Path $userProfile ".claude"
+
+    Write-ColorOutput "Global path: $userProfile" $ColorInfo
+
+    # Source paths
+    $sourceDir = $PSScriptRoot
+    $sourceClaudeDir = Join-Path $sourceDir ".claude"
+    $sourceClaudeMd = Join-Path $sourceDir "CLAUDE.md"
+
+    # Local paths - only for agents, commands, output-styles
+    $localClaudeDir = Join-Path $TargetDirectory ".claude"
+
+    # Create backup folder if needed
+    $backupFolder = $null
+    if (-not $NoBackup) {
+        if ((Test-Path $localClaudeDir) -or (Test-Path $globalClaudeDir)) {
+            $backupFolder = Get-BackupDirectory -TargetDirectory $TargetDirectory
+            Write-ColorOutput "Backup folder created: $backupFolder" $ColorInfo
+        }
+    }
+
+    # Create local .claude directory
+    if (-not (Test-Path $localClaudeDir)) {
+        New-Item -ItemType Directory -Path $localClaudeDir -Force | Out-Null
+        Write-ColorOutput "Created local .claude directory" $ColorSuccess
+    }
+
+    # Local folders to install (agents, commands, output-styles)
+    $localFolders = @("agents", "commands", "output-styles")
+
+    Write-ColorOutput "Installing local components (agents, commands, output-styles)..." $ColorInfo
+    foreach ($folder in $localFolders) {
+        $sourceFolderPath = Join-Path $sourceClaudeDir $folder
+        $destFolderPath = Join-Path $localClaudeDir $folder
+
+        if (Test-Path $sourceFolderPath) {
+            if (Test-Path $destFolderPath) {
+                if ($backupFolder) {
+                    Backup-DirectoryToFolder -DirectoryPath $destFolderPath -BackupFolder $backupFolder
+                }
+            }
+
+            Copy-DirectoryRecursive -Source $sourceFolderPath -Destination $destFolderPath
+            Write-ColorOutput "Installed local folder: $folder" $ColorSuccess
+        } else {
+            Write-ColorOutput "WARNING: Source folder not found: $folder" $ColorWarning
+        }
+    }
+
+    # Global components - exclude local folders
+    Write-ColorOutput "Installing global components to $globalClaudeDir..." $ColorInfo
+
+    # Get all items from source, excluding local folders
+    $sourceItems = Get-ChildItem -Path $sourceClaudeDir -Recurse -File | Where-Object {
+        $relativePath = $_.FullName.Substring($sourceClaudeDir.Length + 1)
+        $topFolder = $relativePath.Split([System.IO.Path]::DirectorySeparatorChar)[0]
+        $topFolder -notin $localFolders
+    }
+
+    $mergedCount = 0
+    foreach ($item in $sourceItems) {
+        $relativePath = $item.FullName.Substring($sourceClaudeDir.Length + 1)
+        $destinationPath = Join-Path $globalClaudeDir $relativePath
+
+        # Ensure destination directory exists
+        $destinationDir = Split-Path $destinationPath -Parent
+        if (-not (Test-Path $destinationDir)) {
+            New-Item -ItemType Directory -Path $destinationDir -Force | Out-Null
+        }
+
+        # Handle file merging
+        if (Test-Path $destinationPath) {
+            if ($BackupAll -and -not $NoBackup) {
+                if ($backupFolder) {
+                    Backup-FileToFolder -FilePath $destinationPath -BackupFolder $backupFolder
+                }
+                Copy-Item -Path $item.FullName -Destination $destinationPath -Force
+                $mergedCount++
+            } elseif ($NoBackup) {
+                if (Confirm-Action "File '$relativePath' already exists in global location. Replace it? (NO BACKUP)" -DefaultYes:$false) {
+                    Copy-Item -Path $item.FullName -Destination $destinationPath -Force
+                    $mergedCount++
+                }
+            } elseif (Confirm-Action "File '$relativePath' already exists in global location. Replace it?" -DefaultYes:$false) {
+                if ($backupFolder) {
+                    Backup-FileToFolder -FilePath $destinationPath -BackupFolder $backupFolder
+                }
+                Copy-Item -Path $item.FullName -Destination $destinationPath -Force
+                $mergedCount++
+            }
+        } else {
+            Copy-Item -Path $item.FullName -Destination $destinationPath -Force
+            $mergedCount++
+        }
+    }
+
+    Write-ColorOutput "Merged $mergedCount files to global location" $ColorSuccess
+
+    # Handle CLAUDE.md file in global .claude directory
+    $globalClaudeMd = Join-Path $globalClaudeDir "CLAUDE.md"
+    Write-ColorOutput "Installing CLAUDE.md to global .claude directory..." $ColorInfo
+    Copy-FileToDestination -Source $sourceClaudeMd -Destination $globalClaudeMd -Description "CLAUDE.md" -BackupFolder $backupFolder
+
+    if ($backupFolder -and (Test-Path $backupFolder)) {
+        $backupFiles = Get-ChildItem $backupFolder -Recurse -File -ErrorAction SilentlyContinue
+        if (-not $backupFiles -or ($backupFiles | Measure-Object).Count -eq 0) {
+            Remove-Item -Path $backupFolder -Force
+            Write-ColorOutput "Removed empty backup folder" $ColorInfo
+        }
+    }
+
     return $true
 }
 
 
 function Get-InstallationMode {
-    Write-ColorOutput "Installation mode: Global (installing to user profile ~/.claude/)" $ColorInfo
+    if ($InstallMode) {
+        Write-ColorOutput "Installation mode: $InstallMode" $ColorInfo
+        return $InstallMode
+    }
+
+    $modes = @(
+        "Global - Install to user profile (~/.claude/)",
+        "Path - Install to custom directory (partial local + global)"
+    )
+
+    Write-Host ""
+    $selection = Get-UserChoiceWithArrows -Prompt "Choose installation mode:" -Options $modes -DefaultIndex 0
+
+    if ($selection -like "Global*") {
+        return "Global"
+    } elseif ($selection -like "Path*") {
+        return "Path"
+    }
+
     return "Global"
 }
 
+function Get-InstallationPath {
+    param(
+        [string]$Mode
+    )
+
+    if ($Mode -eq "Global") {
+        return [Environment]::GetFolderPath("UserProfile")
+    }
+
+    if ($TargetPath) {
+        if (Test-Path $TargetPath) {
+            return $TargetPath
+        }
+        Write-ColorOutput "WARNING: Specified target path does not exist: $TargetPath" $ColorWarning
+    }
+
+    # Interactive path selection
+    do {
+        Write-Host ""
+        Write-ColorOutput "Enter the target directory path for installation:" $ColorPrompt
+        Write-ColorOutput "(This will install agents, commands, output-styles locally, other files globally)" $ColorInfo
+        $path = Read-Host "Path"
+
+        if ([string]::IsNullOrWhiteSpace($path)) {
+            Write-ColorOutput "Path cannot be empty" $ColorWarning
+            continue
+        }
+
+        # Expand environment variables and relative paths
+        $expandedPath = [System.Environment]::ExpandEnvironmentVariables($path)
+        $expandedPath = $ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($expandedPath)
+
+        if (Test-Path $expandedPath) {
+            return $expandedPath
+        }
+
+        Write-ColorOutput "Path does not exist: $expandedPath" $ColorWarning
+        if (Confirm-Action "Create this directory?" -DefaultYes) {
+            try {
+                New-Item -ItemType Directory -Path $expandedPath -Force | Out-Null
+                Write-ColorOutput "Directory created successfully" $ColorSuccess
+                return $expandedPath
+            } catch {
+                Write-ColorOutput "Failed to create directory: $($_.Exception.Message)" $ColorError
+            }
+        }
+    } while ($true)
+}
+
 
 function Show-Summary {
     param(
@@ -519,17 +865,26 @@ function Show-Summary {
         [string]$Path,
         [bool]$Success
     )
-    
+
     Write-Host ""
     if ($Success) {
         Write-ColorOutput "Installation completed successfully!" $ColorSuccess
     } else {
         Write-ColorOutput "Installation completed with warnings" $ColorWarning
     }
-    
+
     Write-ColorOutput "Installation Details:" $ColorInfo
     Write-Host "  Mode: $Mode"
-    Write-Host "  Path: $Path"
+
+    if ($Mode -eq "Path") {
+        Write-Host "  Local Path: $Path"
+        Write-Host "  Global Path: $([Environment]::GetFolderPath('UserProfile'))"
+        Write-Host "  Local Components: agents, commands, output-styles"
+        Write-Host "  Global Components: workflows, scripts, python_script, etc."
+    } else {
+        Write-Host "  Path: $Path"
+    }
+
     if ($NoBackup) {
         Write-Host "  Backup: Disabled (no backup created)"
     } elseif ($BackupAll) {
@@ -537,7 +892,7 @@ function Show-Summary {
     } else {
         Write-Host "  Backup: Enabled (default behavior)"
     }
-    
+
     Write-Host ""
     Write-ColorOutput "Next steps:" $ColorInfo
     Write-Host "1. Review CLAUDE.md - Customize guidelines for your project"
@@ -545,7 +900,7 @@ function Show-Summary {
     Write-Host "3. Start using Claude Code with Agent workflow coordination!"
     Write-Host "4. Use /workflow commands for task execution"
     Write-Host "5. Use /update-memory commands for memory system management"
-    
+
     Write-Host ""
     Write-ColorOutput "Documentation: https://github.com/catlog22/Claude-CCW" $ColorInfo
     Write-ColorOutput "Features: Unified workflow system with comprehensive file output generation" $ColorInfo
@@ -553,48 +908,57 @@ function Show-Summary {
 
 function Main {
     Show-Header
-    
+
     # Test prerequisites
     Write-ColorOutput "Checking system requirements..." $ColorInfo
     if (-not (Test-Prerequisites)) {
         Write-ColorOutput "Prerequisites check failed!" $ColorError
         return 1
     }
-    
+
     try {
         # Get installation mode
         $mode = Get-InstallationMode
         $installPath = ""
         $success = $false
-        
-        $installPath = [Environment]::GetFolderPath("UserProfile")
-        $success = Install-Global
-        
-        Show-Summary -Mode $mode -Path $installPath -Success $success
-        
+
+        if ($mode -eq "Global") {
+            $installPath = [Environment]::GetFolderPath("UserProfile")
+            $result = Install-Global
+            $success = $result -eq $true
+        }
+        elseif ($mode -eq "Path") {
+            $installPath = Get-InstallationPath -Mode $mode
+            $result = Install-Path -TargetDirectory $installPath
+            $success = $result -eq $true
+        }
+
+        Show-Summary -Mode $mode -Path $installPath -Success ([bool]$success)
+
         # Wait for user confirmation before exit in interactive mode
         if (-not $NonInteractive) {
             Write-Host ""
             Write-ColorOutput "Installation completed. Press any key to exit..." $ColorPrompt
             $null = $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
         }
-        
+
         if ($success) {
             return 0
         } else {
             return 1
         }
-        
+
     } catch {
         Write-ColorOutput "CRITICAL ERROR: $($_.Exception.Message)" $ColorError
-        
+        Write-ColorOutput "Stack trace: $($_.ScriptStackTrace)" $ColorError
+
         # Wait for user confirmation before exit in interactive mode
         if (-not $NonInteractive) {
             Write-Host ""
             Write-ColorOutput "An error occurred. Press any key to exit..." $ColorPrompt
             $null = $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
         }
-        
+
         return 1
     }
 }

Install-Claude.sh

@@ -0,0 +1,786 @@
+#!/usr/bin/env bash
+# Claude Code Workflow System Interactive Installer
+# Installation script for Claude Code Workflow System with Agent coordination and distributed memory system.
+# Installs globally to user profile directory (~/.claude) by default.
+
+set -e  # Exit on error
+
+# Script metadata
+SCRIPT_NAME="Claude Code Workflow System Installer"
+VERSION="2.1.0"
+
+# Colors for output
+COLOR_RESET='\033[0m'
+COLOR_SUCCESS='\033[0;32m'
+COLOR_INFO='\033[0;36m'
+COLOR_WARNING='\033[0;33m'
+COLOR_ERROR='\033[0;31m'
+COLOR_PROMPT='\033[0;35m'
+
+# Default parameters
+INSTALL_MODE=""
+TARGET_PATH=""
+FORCE=false
+NON_INTERACTIVE=false
+BACKUP_ALL=true  # Enabled by default
+NO_BACKUP=false
+
+# Functions
+function write_color() {
+    local message="$1"
+    local color="${2:-$COLOR_RESET}"
+    echo -e "${color}${message}${COLOR_RESET}"
+}
+
+function show_banner() {
+    echo ""
+    # CLAUDE - Cyan color
+    write_color '  ______   __                            __                   ' "$COLOR_INFO"
+    write_color ' /      \ |  \                          |  \                 ' "$COLOR_INFO"
+    write_color '|  $$$$$$\| $$  ______   __    __   ____| $$  ______        ' "$COLOR_INFO"
+    write_color '| $$   \$$| $$ |      \ |  \  |  \ /      $$ /      \       ' "$COLOR_INFO"
+    write_color '| $$      | $$  \$$$$$$\| $$  | $$|  $$$$$$$|  $$$$$$\      ' "$COLOR_INFO"
+    write_color '| $$   __ | $$ /      $$| $$  | $$| $$  | $$| $$    $$      ' "$COLOR_INFO"
+    write_color '| $$__/  \| $$|  $$$$$$$| $$__/ $$| $$__| $$| $$$$$$$$      ' "$COLOR_INFO"
+    write_color ' \$$    $$| $$ \$$    $$ \$$    $$ \$$    $$ \$$     \       ' "$COLOR_INFO"
+    write_color '  \$$$$$$  \$$  \$$$$$$$  \$$$$$$   \$$$$$$$  \$$$$$$$        ' "$COLOR_INFO"
+    echo ""
+
+    # CODE - Green color
+    write_color ' ______                   __                  ' "$COLOR_SUCCESS"
+    write_color '/      \                 |  \                ' "$COLOR_SUCCESS"
+    write_color '|  $$$$$$\  ______    ____| $$  ______        ' "$COLOR_SUCCESS"
+    write_color '| $$   \$$ /      \  /      $$ /      \       ' "$COLOR_SUCCESS"
+    write_color '| $$      |  $$$$$$\|  $$$$$$$|  $$$$$$\      ' "$COLOR_SUCCESS"
+    write_color '| $$   __ | $$  | $$| $$  | $$| $$    $$      ' "$COLOR_SUCCESS"
+    write_color '| $$__/  \| $$__/ $$| $$__| $$| $$$$$$$$      ' "$COLOR_SUCCESS"
+    write_color ' \$$    $$ \$$    $$ \$$    $$ \$$     \      ' "$COLOR_SUCCESS"
+    write_color '  \$$$$$$   \$$$$$$   \$$$$$$$  \$$$$$$$       ' "$COLOR_SUCCESS"
+    echo ""
+
+    # WORKFLOW - Yellow color
+    write_color '__       __                      __         ______   __                         ' "$COLOR_WARNING"
+    write_color '|  \  _  |  \                    |  \       /      \ |  \                        ' "$COLOR_WARNING"
+    write_color '| $$ / \ | $$  ______    ______  | $$   __ |  $$$$$$\| $$  ______   __   __   __ ' "$COLOR_WARNING"
+    write_color '| $$/  $\| $$ /      \  /      \ | $$  /  \| $$_  \$$| $$ /      \ |  \ |  \ |  \' "$COLOR_WARNING"
+    write_color '| $$  $$$\ $$|  $$$$$$\|  $$$$$$\| $$_/  $$| $$ \    | $$|  $$$$$$\| $$ | $$ | $$' "$COLOR_WARNING"
+    write_color '| $$ $$\$$\$$| $$  | $$| $$   \$$| $$   $$ | $$$$    | $$| $$  | $$| $$ | $$ | $$' "$COLOR_WARNING"
+    write_color '| $$$$  \$$$$| $$__/ $$| $$      | $$$$$$\ | $$      | $$| $$__/ $$| $$_/ $$_/ $$' "$COLOR_WARNING"
+    write_color '| $$$    \$$$ \$$    $$| $$      | $$  \$$\| $$      | $$ \$$    $$ \$$   $$   $$' "$COLOR_WARNING"
+    write_color ' \$$      \$$  \$$$$$$  \$$       \$$   \$$ \$$       \$$  \$$$$$$   \$$$$$\$$$$' "$COLOR_WARNING"
+    echo ""
+}
+
+function show_header() {
+    show_banner
+    write_color "    $SCRIPT_NAME v$VERSION" "$COLOR_INFO"
+    write_color "    Unified workflow system with comprehensive coordination" "$COLOR_INFO"
+    write_color "========================================================================" "$COLOR_INFO"
+
+    if [ "$NO_BACKUP" = true ]; then
+        write_color "WARNING: Backup disabled - existing files will be overwritten!" "$COLOR_WARNING"
+    else
+        write_color "Auto-backup enabled - existing files will be backed up" "$COLOR_SUCCESS"
+    fi
+    echo ""
+}
+
+function test_prerequisites() {
+    # Test bash version
+    if [ "${BASH_VERSINFO[0]}" -lt 4 ]; then
+        write_color "ERROR: Bash 4.0 or higher is required" "$COLOR_ERROR"
+        write_color "Current version: ${BASH_VERSION}" "$COLOR_ERROR"
+        return 1
+    fi
+
+    # Test source files exist
+    local script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+    local claude_dir="$script_dir/.claude"
+    local claude_md="$script_dir/CLAUDE.md"
+
+    if [ ! -d "$claude_dir" ]; then
+        write_color "ERROR: .claude directory not found in $script_dir" "$COLOR_ERROR"
+        return 1
+    fi
+
+    if [ ! -f "$claude_md" ]; then
+        write_color "ERROR: CLAUDE.md file not found in $script_dir" "$COLOR_ERROR"
+        return 1
+    fi
+
+    write_color "✓ Prerequisites check passed" "$COLOR_SUCCESS"
+    return 0
+}
+
+function get_user_choice() {
+    local prompt="$1"
+    shift
+    local options=("$@")
+    local default_index=0
+
+    if [ "$NON_INTERACTIVE" = true ]; then
+        write_color "Non-interactive mode: Using default '${options[$default_index]}'" "$COLOR_INFO" >&2
+        echo "${options[$default_index]}"
+        return
+    fi
+
+    # Output prompts to stderr so they don't interfere with function return value
+    echo "" >&2
+    write_color "$prompt" "$COLOR_PROMPT" >&2
+    echo "" >&2
+
+    for i in "${!options[@]}"; do
+        echo "  $((i + 1)). ${options[$i]}" >&2
+    done
+
+    echo "" >&2
+
+    while true; do
+        read -p "Please select (1-${#options[@]}): " choice
+
+        if [[ "$choice" =~ ^[0-9]+$ ]] && [ "$choice" -ge 1 ] && [ "$choice" -le "${#options[@]}" ]; then
+            echo "${options[$((choice - 1))]}"
+            return
+        fi
+
+        write_color "Invalid selection. Please enter a number between 1 and ${#options[@]}" "$COLOR_WARNING" >&2
+    done
+}
+
+function confirm_action() {
+    local message="$1"
+    local default_yes="${2:-false}"
+
+    if [ "$FORCE" = true ]; then
+        write_color "Force mode: Proceeding with '$message'" "$COLOR_INFO"
+        return 0
+    fi
+
+    if [ "$NON_INTERACTIVE" = true ]; then
+        if [ "$default_yes" = true ]; then
+            write_color "Non-interactive mode: $message - Yes" "$COLOR_INFO"
+            return 0
+        else
+            write_color "Non-interactive mode: $message - No" "$COLOR_INFO"
+            return 1
+        fi
+    fi
+
+    local prompt
+    if [ "$default_yes" = true ]; then
+        prompt="(Y/n)"
+    else
+        prompt="(y/N)"
+    fi
+
+    while true; do
+        read -p "$message $prompt " response
+
+        if [ -z "$response" ]; then
+            [ "$default_yes" = true ] && return 0 || return 1
+        fi
+
+        case "${response,,}" in
+            y|yes) return 0 ;;
+            n|no) return 1 ;;
+            *) write_color "Please answer 'y' or 'n'" "$COLOR_WARNING" ;;
+        esac
+    done
+}
+
+function get_backup_directory() {
+    local target_dir="$1"
+    local timestamp=$(date +"%Y%m%d-%H%M%S")
+    local backup_dir="${target_dir}/claude-backup-${timestamp}"
+
+    mkdir -p "$backup_dir"
+    echo "$backup_dir"
+}
+
+function backup_file_to_folder() {
+    local file_path="$1"
+    local backup_folder="$2"
+
+    if [ ! -f "$file_path" ]; then
+        return 1
+    fi
+
+    local file_name=$(basename "$file_path")
+    local file_dir=$(dirname "$file_path")
+    local relative_path=""
+
+    # Try to determine relative path structure
+    if [[ "$file_dir" == *".claude"* ]]; then
+        relative_path="${file_dir#*.claude/}"
+    fi
+
+    # Create subdirectory structure in backup if needed
+    local backup_sub_dir="$backup_folder"
+    if [ -n "$relative_path" ]; then
+        backup_sub_dir="${backup_folder}/${relative_path}"
+        mkdir -p "$backup_sub_dir"
+    fi
+
+    local backup_file_path="${backup_sub_dir}/${file_name}"
+
+    if cp "$file_path" "$backup_file_path"; then
+        write_color "Backed up: $file_name" "$COLOR_INFO"
+        return 0
+    else
+        write_color "WARNING: Failed to backup file $file_path" "$COLOR_WARNING"
+        return 1
+    fi
+}
+
+function backup_directory_to_folder() {
+    local dir_path="$1"
+    local backup_folder="$2"
+
+    if [ ! -d "$dir_path" ]; then
+        return 1
+    fi
+
+    local dir_name=$(basename "$dir_path")
+    local backup_dir_path="${backup_folder}/${dir_name}"
+
+    if cp -r "$dir_path" "$backup_dir_path"; then
+        write_color "Backed up directory: $dir_name" "$COLOR_INFO"
+        return 0
+    else
+        write_color "WARNING: Failed to backup directory $dir_path" "$COLOR_WARNING"
+        return 1
+    fi
+}
+
+function copy_directory_recursive() {
+    local source="$1"
+    local destination="$2"
+
+    if [ ! -d "$source" ]; then
+        write_color "ERROR: Source directory does not exist: $source" "$COLOR_ERROR"
+        return 1
+    fi
+
+    mkdir -p "$destination"
+
+    if cp -r "$source/"* "$destination/"; then
+        write_color "✓ Directory copied: $source -> $destination" "$COLOR_SUCCESS"
+        return 0
+    else
+        write_color "ERROR: Failed to copy directory" "$COLOR_ERROR"
+        return 1
+    fi
+}
+
+function copy_file_to_destination() {
+    local source="$1"
+    local destination="$2"
+    local description="${3:-file}"
+    local backup_folder="${4:-}"
+
+    if [ -f "$destination" ]; then
+        # Use BackupAll mode for automatic backup
+        if [ "$BACKUP_ALL" = true ] && [ "$NO_BACKUP" = false ]; then
+            if [ -n "$backup_folder" ]; then
+                backup_file_to_folder "$destination" "$backup_folder"
+                write_color "Auto-backed up: $description" "$COLOR_SUCCESS"
+            fi
+            cp "$source" "$destination"
+            write_color "$description updated (with backup)" "$COLOR_SUCCESS"
+            return 0
+        elif [ "$NO_BACKUP" = true ]; then
+            if confirm_action "$description already exists. Replace it? (NO BACKUP)" false; then
+                cp "$source" "$destination"
+                write_color "$description updated (no backup)" "$COLOR_WARNING"
+                return 0
+            else
+                write_color "Skipping $description installation" "$COLOR_WARNING"
+                return 1
+            fi
+        elif confirm_action "$description already exists. Replace it?" false; then
+            if [ -n "$backup_folder" ]; then
+                backup_file_to_folder "$destination" "$backup_folder"
+                write_color "Existing $description backed up" "$COLOR_SUCCESS"
+            fi
+            cp "$source" "$destination"
+            write_color "$description updated" "$COLOR_SUCCESS"
+            return 0
+        else
+            write_color "Skipping $description installation" "$COLOR_WARNING"
+            return 1
+        fi
+    else
+        # Ensure destination directory exists
+        local dest_dir=$(dirname "$destination")
+        mkdir -p "$dest_dir"
+        cp "$source" "$destination"
+        write_color "✓ $description installed" "$COLOR_SUCCESS"
+        return 0
+    fi
+}
+
+function merge_directory_contents() {
+    local source="$1"
+    local destination="$2"
+    local description="${3:-directory contents}"
+    local backup_folder="${4:-}"
+
+    if [ ! -d "$source" ]; then
+        write_color "WARNING: Source $description not found: $source" "$COLOR_WARNING"
+        return 1
+    fi
+
+    mkdir -p "$destination"
+    write_color "Created destination directory: $destination" "$COLOR_INFO"
+
+    local merged_count=0
+    local skipped_count=0
+
+    # Find all files recursively
+    while IFS= read -r -d '' file; do
+        local relative_path="${file#$source/}"
+        local dest_path="${destination}/${relative_path}"
+        local dest_dir=$(dirname "$dest_path")
+
+        mkdir -p "$dest_dir"
+
+        if [ -f "$dest_path" ]; then
+            local file_name=$(basename "$relative_path")
+
+            if [ "$BACKUP_ALL" = true ] && [ "$NO_BACKUP" = false ]; then
+                if [ -n "$backup_folder" ]; then
+                    backup_file_to_folder "$dest_path" "$backup_folder"
+                    write_color "Auto-backed up: $file_name" "$COLOR_INFO"
+                fi
+                cp "$file" "$dest_path"
+                ((merged_count++))
+            elif [ "$NO_BACKUP" = true ]; then
+                if confirm_action "File '$relative_path' already exists. Replace it? (NO BACKUP)" false; then
+                    cp "$file" "$dest_path"
+                    ((merged_count++))
+                else
+                    write_color "Skipped $file_name (no backup)" "$COLOR_WARNING"
+                    ((skipped_count++))
+                fi
+            elif confirm_action "File '$relative_path' already exists. Replace it?" false; then
+                if [ -n "$backup_folder" ]; then
+                    backup_file_to_folder "$dest_path" "$backup_folder"
+                    write_color "Backed up existing $file_name" "$COLOR_INFO"
+                fi
+                cp "$file" "$dest_path"
+                ((merged_count++))
+            else
+                write_color "Skipped $file_name" "$COLOR_WARNING"
+                ((skipped_count++))
+            fi
+        else
+            cp "$file" "$dest_path"
+            ((merged_count++))
+        fi
+    done < <(find "$source" -type f -print0)
+
+    write_color "✓ Merged $merged_count files, skipped $skipped_count files" "$COLOR_SUCCESS"
+    return 0
+}
+
+function install_global() {
+    write_color "Installing Claude Code Workflow System globally..." "$COLOR_INFO"
+
+    local user_home="$HOME"
+    local global_claude_dir="${user_home}/.claude"
+    local global_claude_md="${global_claude_dir}/CLAUDE.md"
+
+    write_color "Global installation path: $user_home" "$COLOR_INFO"
+
+    # Source paths
+    local script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+    local source_claude_dir="${script_dir}/.claude"
+    local source_claude_md="${script_dir}/CLAUDE.md"
+
+    # Create backup folder if needed
+    local backup_folder=""
+    if [ "$NO_BACKUP" = false ]; then
+        if [ -d "$global_claude_dir" ] && [ "$(ls -A "$global_claude_dir" 2>/dev/null)" ]; then
+            backup_folder=$(get_backup_directory "$user_home")
+            write_color "Backup folder created: $backup_folder" "$COLOR_INFO"
+        elif [ -f "$global_claude_md" ]; then
+            backup_folder=$(get_backup_directory "$user_home")
+            write_color "Backup folder created: $backup_folder" "$COLOR_INFO"
+        fi
+    fi
+
+    # Merge .claude directory contents
+    write_color "Merging .claude directory contents..." "$COLOR_INFO"
+    merge_directory_contents "$source_claude_dir" "$global_claude_dir" ".claude directory contents" "$backup_folder"
+
+    # Handle CLAUDE.md file
+    write_color "Installing CLAUDE.md to global .claude directory..." "$COLOR_INFO"
+    copy_file_to_destination "$source_claude_md" "$global_claude_md" "CLAUDE.md" "$backup_folder"
+
+    # Remove empty backup folder
+    if [ -n "$backup_folder" ] && [ -d "$backup_folder" ]; then
+        if [ -z "$(ls -A "$backup_folder" 2>/dev/null)" ]; then
+            rm -rf "$backup_folder"
+            write_color "Removed empty backup folder" "$COLOR_INFO"
+        fi
+    fi
+
+    return 0
+}
+
+function install_path() {
+    local target_dir="$1"
+
+    write_color "Installing Claude Code Workflow System in hybrid mode..." "$COLOR_INFO"
+    write_color "Local path: $target_dir" "$COLOR_INFO"
+
+    local user_home="$HOME"
+    local global_claude_dir="${user_home}/.claude"
+    write_color "Global path: $user_home" "$COLOR_INFO"
+
+    # Source paths
+    local script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+    local source_claude_dir="${script_dir}/.claude"
+    local source_claude_md="${script_dir}/CLAUDE.md"
+
+    # Local paths
+    local local_claude_dir="${target_dir}/.claude"
+
+    # Create backup folder if needed
+    local backup_folder=""
+    if [ "$NO_BACKUP" = false ]; then
+        if [ -d "$local_claude_dir" ] || [ -d "$global_claude_dir" ]; then
+            backup_folder=$(get_backup_directory "$target_dir")
+            write_color "Backup folder created: $backup_folder" "$COLOR_INFO"
+        fi
+    fi
+
+    # Create local .claude directory
+    mkdir -p "$local_claude_dir"
+    write_color "✓ Created local .claude directory" "$COLOR_SUCCESS"
+
+    # Local folders to install
+    local local_folders=("agents" "commands" "output-styles")
+
+    write_color "Installing local components (agents, commands, output-styles)..." "$COLOR_INFO"
+    for folder in "${local_folders[@]}"; do
+        local source_folder="${source_claude_dir}/${folder}"
+        local dest_folder="${local_claude_dir}/${folder}"
+
+        if [ -d "$source_folder" ]; then
+            if [ -d "$dest_folder" ] && [ -n "$backup_folder" ]; then
+                backup_directory_to_folder "$dest_folder" "$backup_folder"
+            fi
+
+            copy_directory_recursive "$source_folder" "$dest_folder"
+            write_color "✓ Installed local folder: $folder" "$COLOR_SUCCESS"
+        else
+            write_color "WARNING: Source folder not found: $folder" "$COLOR_WARNING"
+        fi
+    done
+
+    # Global components - exclude local folders
+    write_color "Installing global components to $global_claude_dir..." "$COLOR_INFO"
+
+    local merged_count=0
+
+    while IFS= read -r -d '' file; do
+        local relative_path="${file#$source_claude_dir/}"
+        local top_folder=$(echo "$relative_path" | cut -d'/' -f1)
+
+        # Skip local folders
+        if [[ " ${local_folders[*]} " =~ " ${top_folder} " ]]; then
+            continue
+        fi
+
+        local dest_path="${global_claude_dir}/${relative_path}"
+        local dest_dir=$(dirname "$dest_path")
+
+        mkdir -p "$dest_dir"
+
+        if [ -f "$dest_path" ]; then
+            if [ "$BACKUP_ALL" = true ] && [ "$NO_BACKUP" = false ]; then
+                if [ -n "$backup_folder" ]; then
+                    backup_file_to_folder "$dest_path" "$backup_folder"
+                fi
+                cp "$file" "$dest_path"
+                ((merged_count++))
+            elif [ "$NO_BACKUP" = true ]; then
+                if confirm_action "File '$relative_path' already exists in global location. Replace it? (NO BACKUP)" false; then
+                    cp "$file" "$dest_path"
+                    ((merged_count++))
+                fi
+            elif confirm_action "File '$relative_path' already exists in global location. Replace it?" false; then
+                if [ -n "$backup_folder" ]; then
+                    backup_file_to_folder "$dest_path" "$backup_folder"
+                fi
+                cp "$file" "$dest_path"
+                ((merged_count++))
+            fi
+        else
+            cp "$file" "$dest_path"
+            ((merged_count++))
+        fi
+    done < <(find "$source_claude_dir" -type f -print0)
+
+    write_color "✓ Merged $merged_count files to global location" "$COLOR_SUCCESS"
+
+    # Handle CLAUDE.md file in global .claude directory
+    local global_claude_md="${global_claude_dir}/CLAUDE.md"
+    write_color "Installing CLAUDE.md to global .claude directory..." "$COLOR_INFO"
+    copy_file_to_destination "$source_claude_md" "$global_claude_md" "CLAUDE.md" "$backup_folder"
+
+    # Remove empty backup folder
+    if [ -n "$backup_folder" ] && [ -d "$backup_folder" ]; then
+        if [ -z "$(ls -A "$backup_folder" 2>/dev/null)" ]; then
+            rm -rf "$backup_folder"
+            write_color "Removed empty backup folder" "$COLOR_INFO"
+        fi
+    fi
+
+    return 0
+}
+
+function get_installation_mode() {
+    if [ -n "$INSTALL_MODE" ]; then
+        write_color "Installation mode: $INSTALL_MODE" "$COLOR_INFO"
+        echo "$INSTALL_MODE"
+        return
+    fi
+
+    local modes=(
+        "Global - Install to user profile (~/.claude/)"
+        "Path - Install to custom directory (partial local + global)"
+    )
+
+    local selection=$(get_user_choice "Choose installation mode:" "${modes[@]}")
+
+    if [[ "$selection" == Global* ]]; then
+        echo "Global"
+    elif [[ "$selection" == Path* ]]; then
+        echo "Path"
+    else
+        echo "Global"
+    fi
+}
+
+function get_installation_path() {
+    local mode="$1"
+
+    if [ "$mode" = "Global" ]; then
+        echo "$HOME"
+        return
+    fi
+
+    if [ -n "$TARGET_PATH" ]; then
+        if [ -d "$TARGET_PATH" ]; then
+            echo "$TARGET_PATH"
+            return
+        fi
+        write_color "WARNING: Specified target path does not exist: $TARGET_PATH" "$COLOR_WARNING"
+    fi
+
+    # Interactive path selection
+    while true; do
+        echo ""
+        write_color "Enter the target directory path for installation:" "$COLOR_PROMPT"
+        write_color "(This will install agents, commands, output-styles locally, other files globally)" "$COLOR_INFO"
+        read -p "Path: " path
+
+        if [ -z "$path" ]; then
+            write_color "Path cannot be empty" "$COLOR_WARNING"
+            continue
+        fi
+
+        # Expand ~ and environment variables
+        path=$(eval echo "$path")
+
+        if [ -d "$path" ]; then
+            echo "$path"
+            return
+        fi
+
+        write_color "Path does not exist: $path" "$COLOR_WARNING"
+        if confirm_action "Create this directory?" true; then
+            if mkdir -p "$path"; then
+                write_color "✓ Directory created successfully" "$COLOR_SUCCESS"
+                echo "$path"
+                return
+            else
+                write_color "ERROR: Failed to create directory" "$COLOR_ERROR"
+            fi
+        fi
+    done
+}
+
+function show_summary() {
+    local mode="$1"
+    local path="$2"
+    local success="$3"
+
+    echo ""
+    if [ "$success" = true ]; then
+        write_color "✓ Installation completed successfully!" "$COLOR_SUCCESS"
+    else
+        write_color "Installation completed with warnings" "$COLOR_WARNING"
+    fi
+
+    write_color "Installation Details:" "$COLOR_INFO"
+    echo "  Mode: $mode"
+
+    if [ "$mode" = "Path" ]; then
+        echo "  Local Path: $path"
+        echo "  Global Path: $HOME"
+        echo "  Local Components: agents, commands, output-styles"
+        echo "  Global Components: workflows, scripts, python_script, etc."
+    else
+        echo "  Path: $path"
+    fi
+
+    if [ "$NO_BACKUP" = true ]; then
+        echo "  Backup: Disabled (no backup created)"
+    elif [ "$BACKUP_ALL" = true ]; then
+        echo "  Backup: Enabled (automatic backup of all existing files)"
+    else
+        echo "  Backup: Enabled (default behavior)"
+    fi
+
+    echo ""
+    write_color "Next steps:" "$COLOR_INFO"
+    echo "1. Review CLAUDE.md - Customize guidelines for your project"
+    echo "2. Configure settings - Edit .claude/settings.local.json as needed"
+    echo "3. Start using Claude Code with Agent workflow coordination!"
+    echo "4. Use /workflow commands for task execution"
+    echo "5. Use /update-memory commands for memory system management"
+
+    echo ""
+    write_color "Documentation: https://github.com/catlog22/Claude-Code-Workflow" "$COLOR_INFO"
+    write_color "Features: Unified workflow system with comprehensive file output generation" "$COLOR_INFO"
+}
+
+function parse_arguments() {
+    while [[ $# -gt 0 ]]; do
+        case "$1" in
+            -InstallMode)
+                INSTALL_MODE="$2"
+                shift 2
+                ;;
+            -TargetPath)
+                TARGET_PATH="$2"
+                shift 2
+                ;;
+            -Force)
+                FORCE=true
+                shift
+                ;;
+            -NonInteractive)
+                NON_INTERACTIVE=true
+                shift
+                ;;
+            -BackupAll)
+                BACKUP_ALL=true
+                NO_BACKUP=false
+                shift
+                ;;
+            -NoBackup)
+                NO_BACKUP=true
+                BACKUP_ALL=false
+                shift
+                ;;
+            --help|-h)
+                show_help
+                exit 0
+                ;;
+            *)
+                write_color "Unknown option: $1" "$COLOR_ERROR"
+                show_help
+                exit 1
+                ;;
+        esac
+    done
+}
+
+function show_help() {
+    cat << EOF
+$SCRIPT_NAME v$VERSION
+
+Usage: $0 [OPTIONS]
+
+Options:
+    -InstallMode <mode>   Installation mode: Global or Path
+    -TargetPath <path>    Target path for Path installation mode
+    -Force                Skip confirmation prompts
+    -NonInteractive       Run in non-interactive mode with default options
+    -BackupAll            Automatically backup all existing files (default)
+    -NoBackup             Disable automatic backup functionality
+    --help, -h            Show this help message
+
+Examples:
+    # Interactive installation
+    $0
+
+    # Global installation without prompts
+    $0 -InstallMode Global -Force
+
+    # Path installation with custom directory
+    $0 -InstallMode Path -TargetPath /opt/claude-code-workflow
+
+    # Installation without backup
+    $0 -NoBackup
+
+EOF
+}
+
+function main() {
+    show_header
+
+    # Test prerequisites
+    write_color "Checking system requirements..." "$COLOR_INFO"
+    if ! test_prerequisites; then
+        write_color "Prerequisites check failed!" "$COLOR_ERROR"
+        return 1
+    fi
+
+    local mode=$(get_installation_mode)
+    local install_path=""
+    local success=false
+
+    if [ "$mode" = "Global" ]; then
+        install_path="$HOME"
+        if install_global; then
+            success=true
+        fi
+    elif [ "$mode" = "Path" ]; then
+        install_path=$(get_installation_path "$mode")
+        if install_path "$install_path"; then
+            success=true
+        fi
+    fi
+
+    show_summary "$mode" "$install_path" "$success"
+
+    # Wait for user confirmation in interactive mode
+    if [ "$NON_INTERACTIVE" != true ]; then
+        echo ""
+        write_color "Installation completed. Press Enter to exit..." "$COLOR_PROMPT"
+        read -r
+    fi
+
+    if [ "$success" = true ]; then
+        return 0
+    else
+        return 1
+    fi
+}
+
+# Initialize backup behavior - backup is enabled by default unless NoBackup is specified
+if [ "$NO_BACKUP" = false ]; then
+    BACKUP_ALL=true
+fi
+
+# Parse command line arguments
+parse_arguments "$@"
+
+# Run main function
+main
+exit $?

README.md

@@ -2,7 +2,7 @@
 
 <div align="center">
 
-[![Version](https://img.shields.io/badge/version-v2.1.0--experimental-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
+[![Version](https://img.shields.io/badge/version-v3.0.1-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20Linux%20%7C%20macOS-lightgrey.svg)]()
 [![MCP Tools](https://img.shields.io/badge/🔧_MCP_Tools-Experimental-orange.svg)](https://github.com/modelcontextprotocol)
@@ -13,510 +13,129 @@
 
 ---
 
-## 📋 Overview
+**Claude Code Workflow (CCW)** is a next-generation multi-agent automation framework that orchestrates complex software development tasks through intelligent workflow management and autonomous execution.
 
-**Claude Code Workflow (CCW)** is a next-generation multi-agent automation framework for software development that orchestrates complex development tasks through intelligent workflow management and autonomous execution.
-
-> **🧪 Latest Release v2.1.0-experimental**: Introduces **experimental MCP (Model Context Protocol) tools integration** for enhanced codebase analysis and external context retrieval. Includes Exa MCP Server for external API patterns and Code Index MCP for advanced internal codebase exploration. See [CHANGELOG.md](CHANGELOG.md) for details.
-
-> **⚠️ Experimental Features**: MCP tools are optional and experimental. All existing functionality remains stable.
-
-### 🌟 Key Innovations
-
-- **🔄 Enhanced Workflow Lifecycle**: Complete development cycle: Brainstorm → Plan → Verify → Execute → Test → Review
-- **🧪 Automated Test Generation**: Comprehensive test workflow generation (`/workflow:test-gen`) with full coverage planning
-- **✅ Plan Verification System**: Pre-execution validation using dual Gemini/Codex analysis (`/workflow:plan-verify`)
-- **🎯 JSON-First Architecture**: Single source of truth with atomic session management
-- **💡 Brainstorm Artifacts**: Multi-perspective planning with synthesis and structured document generation
-- **🔧 MCP Tools Integration** *(Experimental)*: Enhanced codebase analysis through Model Context Protocol tools
+> **🎉 Latest: v3.0.1** - Documentation optimization and brainstorming role updates. See [CHANGELOG.md](CHANGELOG.md) for details.
+>
+> **v3.0.0**: Introduced **unified CLI command structure**. The `/cli:*` commands consolidate all tool interactions (Gemini, Qwen, Codex) using a `--tool` flag for selection.
 
 ---
 
-## 🏗️ System Architecture
+## ✨ Key Features
 
-### **🔧 Core Architectural Principles**
-
-```mermaid
-graph TB
-    subgraph "🖥️ CLI Interface Layer"
-        CLI[CLI Commands]
-        GEM[Gemini CLI]
-        COD[Codex CLI]
-        WRAPPER[Intelligent Gemini Wrapper]
-    end
-
-    subgraph "📋 Session Management"
-        MARKER[".active-session markers"]
-        SESSION["workflow-session.json"]
-        WDIR[".workflow/ directories"]
-    end
-
-    subgraph "📊 JSON-First Task System"
-        TASK_JSON[".task/impl-*.json"]
-        HIERARCHY["Task Hierarchy (max 2 levels)"]
-        STATUS["Task Status Management"]
-        DECOMP["Task Decomposition Engine"]
-    end
-
-    subgraph "🤖 Multi-Agent Orchestration"
-        PLAN_AGENT[Conceptual Planning Agent]
-        ACTION_AGENT[Action Planning Agent]
-        CODE_AGENT[Code Developer Agent]
-        REVIEW_AGENT[Code Review Agent]
-        MEMORY_AGENT[Memory Gemini Bridge]
-    end
-
-    CLI --> WRAPPER
-    WRAPPER --> GEM
-    CLI --> COD
-
-    GEM --> PLAN_AGENT
-    COD --> CODE_AGENT
-
-    PLAN_AGENT --> TASK_JSON
-    ACTION_AGENT --> TASK_JSON
-    CODE_AGENT --> TASK_JSON
-
-    TASK_JSON --> DECOMP
-    DECOMP --> HIERARCHY
-    HIERARCHY --> STATUS
-
-    SESSION --> MARKER
-    MARKER --> WDIR
-```
-
-### 🏛️ **Four-Layer Architecture**
-
-CCW operates through four distinct architectural layers with defined responsibilities and data contracts:
-
-| Layer | Components | Data Flow | Integration Points |
-|-------|------------|-----------|-------------------|
-| **🖥️ Interface Layer** | CLI Commands, Gemini/Codex/Qwen Wrappers | User input → Commands → Agents | External CLI tools, approval modes |
-| **📋 Session Layer** | `.active-[session]` markers, `workflow-session.json` | Session state → Task discovery | Atomic session switching |
-| **📊 Task/Data Layer** | `.task/impl-*.json`, hierarchy management | Task definitions → Agent execution | JSON-first model, generated views |
-| **🤖 Orchestration Layer** | Multi-agent coordination, dependency resolution | Agent outputs → Task updates | Intelligent execution flow |
+- **🤖 Multi-Agent System**: Specialized agents for planning, coding, testing, and reviewing.
+- **🔄 End-to-End Workflow Automation**: From brainstorming (`/workflow:brainstorm`) to deployment.
+- **🎯 JSON-First Architecture**: Uses JSON as the single source of truth for tasks, ensuring consistency.
+- **🧪 Automated Test Generation**: Creates comprehensive test suites based on implementation analysis.
+- **✅ Pre-execution Verification**: Validates plans with both strategic (Gemini) and technical (Codex) analysis.
+- **🔧 Unified CLI**: A single, powerful `/cli:*` command set for interacting with various AI tools.
+- **🧠 Smart Context Management**: Automatically manages and updates project documentation (`CLAUDE.md`).
 
 ---
 
-## ✨ Major Enhancements v2.0
+## ⚙️ Installation
 
-### 🔄 **Enhanced Workflow Lifecycle**
-Complete development lifecycle with quality gates at each phase:
+### **🚀 Quick One-Line Installation**
 
-1. **💡 Brainstorm Phase** - Multi-perspective conceptual planning with role-based analysis
-2. **📋 Plan Phase** - Structured implementation planning with task decomposition
-3. **✅ Verify Phase** - Pre-execution validation using Gemini (strategic) + Codex (technical)
-4. **⚡ Execute Phase** - Autonomous implementation with multi-agent orchestration
-5. **🧪 Test Phase** - Automated test workflow generation with comprehensive coverage
-6. **🔍 Review Phase** - Quality assurance and completion validation
-
-### 🧪 **Automated Test Generation**
-Comprehensive test workflow creation:
-- **Implementation Analysis**: Scans completed IMPL-* tasks for test requirements
-- **Multi-layered Testing**: Unit, Integration, E2E, Performance, Security tests
-- **Agent Assignment**: Specialized test agents for different test types
-- **Dependency Mapping**: Test execution follows implementation dependency chains
-
-### ✅ **Plan Verification System**
-Dual-engine validation before execution:
-- **Gemini Strategic Analysis**: High-level feasibility and architectural soundness
-- **Codex Technical Analysis**: Implementation details and technical feasibility
-- **Cross-Validation**: Identifies conflicts between strategic vision and technical constraints
-- **Improvement Suggestions**: Actionable recommendations before implementation begins
-
----
-
-## 📊 Complexity Management System
-
-CCW automatically adapts workflow structure based on project complexity:
-
-| **Complexity** | **Task Count** | **Structure** | **Features** |
-|---|---|---|---|
-| 🟢 **Simple** | <5 tasks | Single-level | Minimal overhead, direct execution |
-| 🟡 **Medium** | 5-10 tasks | Two-level hierarchy | Progress tracking, automated docs |
-| 🔴 **Complex** | >10 tasks | Force re-scoping | Multi-iteration planning required |
-
----
-
-## 🛠️ Complete Command Reference
-
-### 🎮 **Core System Commands**
-
-| Command | Function | Example |
-|---------|----------|---------|
-| `🎯 /enhance-prompt` | Technical context enhancement | `/enhance-prompt "add auth system"` |
-| `📊 /context` | Unified context management | `/context --analyze --format=tree` |
-| `📝 /update-memory-full` | Complete documentation update | `/update-memory-full` |
-| `🔄 /update-memory-related` | Smart context-aware updates | `/update-memory-related` |
-
-### 🔍 **Gemini CLI Commands** (Analysis & Investigation)
-
-| Command | Purpose | Usage |
-|---------|---------|-------|
-| `🔍 /gemini:analyze` | Deep codebase analysis | `/gemini:analyze "authentication patterns"` |
-| `💬 /gemini:chat` | Direct Gemini interaction | `/gemini:chat "explain this architecture"` |
-| `⚡ /gemini:execute` | Intelligent execution with YOLO permissions | `/gemini:execute "implement task-001"` |
-| `🎯 /gemini:mode:auto` | Auto template selection | `/gemini:mode:auto "analyze security vulnerabilities"` |
-| `🐛 /gemini:mode:bug-index` | Bug analysis and fix suggestions | `/gemini:mode:bug-index "payment processing fails"` |
-| `📋 /gemini:mode:plan` | Project planning and architecture | `/gemini:mode:plan "microservices architecture"` |
-| `🎯 /gemini:mode:plan-precise` | Precise path planning analysis | `/gemini:mode:plan-precise "complex refactoring"` |
-
-### 🔮 **Qwen CLI Commands** (Architecture & Code Generation)
-
-| Command | Purpose | Usage |
-|---------|---------|-------|
-| `🔍 /qwen:analyze` | Architecture analysis and code quality | `/qwen:analyze "system architecture patterns"` |
-| `💬 /qwen:chat` | Direct Qwen interaction | `/qwen:chat "design authentication system"` |
-| `⚡ /qwen:execute` | Intelligent implementation with YOLO permissions | `/qwen:execute "implement user authentication"` |
-| `🚀 /qwen:mode:auto` | Auto template selection and execution | `/qwen:mode:auto "build microservices API"` |
-| `🐛 /qwen:mode:bug-index` | Bug analysis and fix suggestions | `/qwen:mode:bug-index "memory leak in service"` |
-| `📋 /qwen:mode:plan` | Architecture planning and analysis | `/qwen:mode:plan "design scalable database"` |
-| `🎯 /qwen:mode:plan-precise` | Precise architectural planning | `/qwen:mode:plan-precise "complex system migration"` |
-
-### 🤖 **Codex CLI Commands** (Development & Implementation)
-
-| Command | Purpose | Usage |
-|---------|---------|-------|
-| `🔍 /codex:analyze` | Development analysis | `/codex:analyze "optimization opportunities"` |
-| `💬 /codex:chat` | Direct Codex interaction | `/codex:chat "implement JWT auth"` |
-| `⚡ /codex:execute` | Autonomous implementation with YOLO permissions | `/codex:execute "refactor user service"` |
-| `🚀 /codex:mode:auto` | **PRIMARY**: Full autonomous development | `/codex:mode:auto "build payment system"` |
-| `🐛 /codex:mode:bug-index` | Autonomous bug fixing and implementation | `/codex:mode:bug-index "fix race condition"` |
-| `📋 /codex:mode:plan` | Development planning and implementation | `/codex:mode:plan "implement API endpoints"` |
-
-### 🎯 **Workflow Management**
-
-#### 📋 Session Management
-| Command | Function | Usage |
-|---------|----------|-------|
-| `🚀 /workflow:session:start` | Create new session | `/workflow:session:start "OAuth2 System"` |
-| `⏸️ /workflow:session:pause` | Pause current session | `/workflow:session:pause` |
-| `▶️ /workflow:session:resume` | Resume session | `/workflow:session:resume "OAuth2 System"` |
-| `📋 /workflow:session:list` | List all sessions | `/workflow:session:list --active` |
-| `🔄 /workflow:session:switch` | Switch sessions | `/workflow:session:switch "Payment Fix"` |
-
-#### 🎯 Workflow Operations
-| Command | Function | Usage |
-|---------|----------|-------|
-| `💭 /workflow:brainstorm:*` | Multi-perspective planning with role experts | `/workflow:brainstorm:system-architect "microservices"` |
-| `🤝 /workflow:brainstorm:synthesis` | Synthesize all brainstorming perspectives | `/workflow:brainstorm:synthesis` |
-| `🎨 /workflow:brainstorm:artifacts` | Generate structured planning documents | `/workflow:brainstorm:artifacts "topic description"` |
-| `📋 /workflow:plan` | Convert to executable implementation plans | `/workflow:plan "description" \| file.md \| ISS-001` |
-| `🔍 /workflow:plan-deep` | Deep technical planning with Gemini analysis | `/workflow:plan-deep "requirements description"` |
-| `✅ /workflow:plan-verify` | Pre-execution validation using dual analysis | `/workflow:plan-verify` |
-| `⚡ /workflow:execute` | Coordinate agents for implementation | `/workflow:execute` |
-| `🔄 /workflow:resume` | Intelligent workflow resumption | `/workflow:resume [--from TASK-ID] [--retry]` |
-| `📊 /workflow:status` | Generate on-demand views from task data | `/workflow:status [task-id] [format] [validation]` |
-| `🧪 /workflow:test-gen` | Generate comprehensive test workflows | `/workflow:test-gen WFS-session-id` |
-| `🔍 /workflow:review` | Execute review phase for quality validation | `/workflow:review` |
-| `📚 /workflow:docs` | Generate hierarchical documentation | `/workflow:docs "architecture" \| "api" \| "all"` |
-
-#### 🏷️ Task Management
-| Command | Function | Usage |
-|---------|----------|-------|
-| `➕ /task:create` | Create implementation task with context | `/task:create "User Authentication System"` |
-| `🔄 /task:breakdown` | Intelligent task decomposition | `/task:breakdown task-id` |
-| `⚡ /task:execute` | Execute tasks with appropriate agents | `/task:execute task-id` |
-| `📋 /task:replan` | Replan tasks with detailed input | `/task:replan task-id ["text" \| file.md \| ISS-001]` |
-
-#### 🏷️ Issue Management
-| Command | Function | Usage |
-|---------|----------|-------|
-| `➕ /workflow:issue:create` | Create new project issue | `/workflow:issue:create "API Rate Limiting" --priority=high` |
-| `📋 /workflow:issue:list` | List and filter issues | `/workflow:issue:list --status=open --assigned=system-architect` |
-| `📝 /workflow:issue:update` | Update existing issue | `/workflow:issue:update ISS-001 --status=in-progress` |
-| `✅ /workflow:issue:close` | Close completed issue | `/workflow:issue:close ISS-001 --reason=resolved` |
-
-#### 🧠 Brainstorming Role Commands
-| Role | Command | Purpose |
-|------|---------|---------|
-| 🏗️ **System Architect** | `/workflow:brainstorm:system-architect` | Technical architecture analysis |
-| 🔒 **Security Expert** | `/workflow:brainstorm:security-expert` | Security and threat analysis |
-| 📊 **Product Manager** | `/workflow:brainstorm:product-manager` | User needs and business value |
-| 🎨 **UI Designer** | `/workflow:brainstorm:ui-designer` | User experience and interface |
-| 📈 **Business Analyst** | `/workflow:brainstorm:business-analyst` | Process optimization analysis |
-| 🔬 **Innovation Lead** | `/workflow:brainstorm:innovation-lead` | Emerging technology opportunities |
-| 📋 **Feature Planner** | `/workflow:brainstorm:feature-planner` | Feature development planning |
-| 🗄️ **Data Architect** | `/workflow:brainstorm:data-architect` | Data modeling and analytics |
-| 👥 **User Researcher** | `/workflow:brainstorm:user-researcher` | User behavior analysis |
-| 🚀 **Auto Selection** | `/workflow:brainstorm:auto` | Dynamic role selection |
-
----
-
-## 🎯 Complete Development Workflows
-
-### 🚀 **Enhanced Workflow Lifecycle**
-
-```mermaid
-graph TD
-    START[🎯 New Feature Request] --> SESSION["/workflow:session:start 'OAuth2 System'"]
-    SESSION --> BRAINSTORM["/workflow:brainstorm:system-architect topic"]
-    BRAINSTORM --> SYNTHESIS["/workflow:brainstorm:synthesis"]
-    SYNTHESIS --> PLAN["/workflow:plan description"]
-    PLAN --> VERIFY["/workflow:plan-verify"]
-    VERIFY --> EXECUTE["/workflow:execute"]
-    EXECUTE --> TEST["/workflow:test-gen WFS-session-id"]
-    TEST --> REVIEW["/workflow:review"]
-    REVIEW --> DOCS["/workflow:docs all"]
-    DOCS --> COMPLETE[✅ Complete]
-```
-
-### ⚡ **Workflow Session Management**
-
-```mermaid
-graph LR
-    START[📋 Session Start] --> MARKER[🏷️ .active-session marker]
-    MARKER --> JSON[📊 workflow-session.json]
-    JSON --> TASKS[🎯 .task/IMPL-*.json]
-    TASKS --> PAUSE[⏸️ Pause: Remove marker]
-    PAUSE --> RESUME[▶️ Resume: Restore marker]
-    RESUME --> SWITCH[🔄 Switch: Change active session]
-```
-
-### 🔥 **Quick Development Examples**
-
-#### **🚀 Complete Feature Development Workflow**
-```bash
-# 1. Initialize focused session
-/workflow:session:start "User Dashboard Feature"
-
-# 2. Multi-perspective brainstorming
-/workflow:brainstorm:system-architect "dashboard analytics system"
-/workflow:brainstorm:ui-designer "dashboard user experience"
-/workflow:brainstorm:data-architect "analytics data flow"
-
-# 3. Synthesize all perspectives
-/workflow:brainstorm:synthesis
-
-# 4. Create executable implementation plan
-/workflow:plan "user dashboard with analytics and real-time data"
-
-# 5. Verify plan before execution
-/workflow:plan-verify
-
-# 6. Execute implementation with agent coordination
-/workflow:execute
-
-# 7. Generate comprehensive test suite
-/workflow:test-gen WFS-user-dashboard-feature
-
-# 8. Quality assurance and review
-/workflow:review
-
-# 9. Generate documentation
-/workflow:docs "all"
-```
-
-#### **⚡ Rapid Bug Resolution**
-```bash
-# Quick bug fix workflow
-/workflow:session:start "Payment Processing Fix"
-/gemini:mode:bug-index "Payment validation fails on concurrent requests"
-/codex:mode:bug-index "Fix race condition in payment validation"
-/workflow:review
-```
-
-#### **📊 Architecture Analysis & Refactoring**
-```bash
-# Deep architecture workflow
-/workflow:session:start "API Refactoring Initiative"
-/gemini:analyze "current API architecture patterns and technical debt"
-/workflow:plan-deep "microservices transition strategy"
-/workflow:plan-verify
-/qwen:mode:auto "Refactor monolith to microservices architecture"
-/workflow:test-gen WFS-api-refactoring-initiative
-/workflow:review
-```
-
----
-
-## 🏗️ Project Structure
-
-```
-📁 .claude/
-├── 🤖 agents/                 # AI agent definitions
-├── 🎯 commands/              # CLI command implementations
-│   ├── 🔍 gemini/           # Gemini CLI commands
-│   ├── 🤖 codex/            # Codex CLI commands
-│   └── 🎯 workflow/         # Workflow management
-├── 🎨 output-styles/         # Output formatting templates
-├── 🎭 planning-templates/    # Role-specific planning
-├── 💬 prompt-templates/      # AI interaction templates
-├── 🔧 scripts/              # Automation utilities
-│   ├── 📊 gemini-wrapper           # Intelligent Gemini wrapper
-│   ├── 🔧 get_modules_by_depth.sh  # Project analysis
-│   └── 📋 read-task-paths.sh       # Task path conversion
-├── 🛠️ workflows/            # Core workflow documentation
-│   ├── 🏛️ workflow-architecture.md      # System architecture
-│   ├── 📊 intelligent-tools-strategy.md # Tool selection guide
-│   ├── 🔧 context-search-strategy.md  # Search and discovery strategy
-│   └── 🔧 tools-implementation-guide.md # Implementation details
-└── ⚙️ settings.local.json   # Local configuration
-
-📁 .workflow/                 # Session workspace (auto-generated)
-├── 🏷️ .active-[session]     # Active session markers
-└── 📋 WFS-[topic-slug]/      # Individual sessions
-    ├── ⚙️ workflow-session.json    # Session metadata
-    ├── 📊 .task/impl-*.json        # Task definitions
-    ├── 📝 IMPL_PLAN.md             # Planning documents
-    ├── ✅ TODO_LIST.md              # Progress tracking
-    ├── 📚 .summaries/              # Completion summaries
-    ├── 🧠 .process/                # NEW: Planning artifacts
-    │   └── 📈 ANALYSIS_RESULTS.md  # Analysis results
-    └── 🧪 WFS-test-[session]/     # NEW: Generated test workflows
-```
-
----
-
-## ⚡ Performance & Technical Specs
-
-### 📊 **Performance Metrics**
-| Metric | Performance | Details |
-|--------|-------------|---------|
-| 🔄 **Session Switching** | <10ms | Atomic marker file operations |
-| 📊 **JSON Queries** | <1ms | Direct JSON access, no parsing overhead |
-| 📝 **Doc Updates** | <30s | Medium projects, intelligent targeting |
-| 🔍 **Context Loading** | <5s | Complex codebases with caching |
-| ⚡ **Task Execution** | 10min timeout | Complex operations with error handling |
-
-### 🛠️ **System Requirements**
-- **🖥️ OS**: Windows 10+, Ubuntu 18.04+, macOS 10.15+
-- **📦 Dependencies**: Git, Node.js (Gemini), Python 3.8+ (Codex)
-- **💾 Storage**: ~50MB core + variable project data
-- **🧠 Memory**: 512MB minimum, 2GB recommended
-
-### 🔗 **Integration Requirements**
-- **🔍 Gemini CLI**: Required for analysis and strategic planning workflows
-- **🤖 Codex CLI**: Required for autonomous development and bug fixing
-- **🔮 Qwen CLI**: Required for architecture analysis and code generation
-- **📂 Git Repository**: Required for change tracking and version control
-- **🎯 Claude Code IDE**: Recommended for optimal experience
-
----
-
-## ⚙️ Installation & Configuration
-
-### 🚀 **Quick Installation**
+**Windows (PowerShell):**
 ```powershell
 Invoke-Expression (Invoke-WebRequest -Uri "https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.ps1" -UseBasicParsing).Content
 ```
 
-### ✅ **Verify Installation**
+**Linux/macOS (Bash/Zsh):**
+```bash
+bash <(curl -fsSL https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.sh)
+```
+
+### **✅ Verify Installation**
+After installation, run the following command to ensure CCW is working:
 ```bash
 /workflow:session:list
 ```
 
-### ⚙️ **Essential Configuration**
+---
+
+## 🚀 Getting Started: A Simple Workflow
+
+1.  **Start a new workflow session:**
+    ```bash
+    /workflow:session:start "Create a new user authentication feature"
+    ```
+
+2.  **Generate an implementation plan:**
+    ```bash
+    /workflow:plan "Implement JWT-based user authentication"
+    ```
+
+3.  **Execute the plan with AI agents:**
+    ```bash
+    /workflow:execute
+    ```
+
+4.  **Check the status:**
+    ```bash
+    /workflow:status
+    ```
+
+---
+
+## 🛠️ Command Reference
+
+### **Unified CLI Commands (`/cli:*)**
+*Use the `--tool <gemini|qwen|codex>` flag to select the desired tool. Defaults to `gemini`.*
+
+| Command | Description |
+|---|---|
+| `/cli:analyze` | Deep codebase analysis. |
+| `/cli:chat` | Direct, interactive chat with a tool. |
+| `/cli:execute` | Execute a task with full permissions. |
+| `/cli:cli-init`| Initialize CLI tool configurations for the workspace. |
+| `/cli:mode:bug-index` | Analyze bugs and suggest fixes. |
+| `/cli:mode:code-analysis` | Perform deep code analysis and debugging. |
+| `/cli:mode:plan` | Project planning and architecture analysis. |
+
+### **Workflow Commands (`/workflow:*)**
+
+| Command | Description |
+|---|---|
+| `/workflow:session:*` | Manage development sessions (`start`, `pause`, `resume`, `list`, `switch`, `complete`). |
+| `/workflow:brainstorm:*` | Use role-based agents for multi-perspective planning. |
+| `/workflow:plan` | Create a detailed, executable plan from a description. |
+| `/workflow:execute` | Execute the current workflow plan autonomously. |
+| `/workflow:status` | Display the current status of the workflow. |
+| `/workflow:test-gen` | Automatically generate a test plan from the implementation. |
+| `/workflow:review` | Initiate a quality assurance review of the completed work. |
+
+### **Task & Memory Commands**
+
+| Command | Description |
+|---|---|
+| `/task:*` | Manage individual tasks (`create`, `breakdown`, `execute`, `replan`). |
+| `/update-memory-full` | Re-index the entire project documentation. |
+| `/update-memory-related` | Update documentation related to recent changes. |
+
+---
+
+## ⚙️ Essential Configuration
+
+For optimal integration, configure your Gemini CLI settings by creating a `settings.json` file in `~/.gemini/`:
 
-#### **Gemini CLI Setup**
 ```json
 // ~/.gemini/settings.json
 {
   "contextFileName": "CLAUDE.md"
 }
 ```
-
-#### **Optimized .geminiignore**
-```bash
-# Performance optimization
-/dist/
-/build/
-/node_modules/
-/.next/
-
-# Temporary files
-*.tmp
-*.log
-/temp/
-
-# Include important docs
-!README.md
-!**/CLAUDE.md
-```
-
-### 🔧 **MCP Tools Configuration** *(Optional Enhancement)*
-
-[![MCP Tools](https://img.shields.io/badge/🔧_MCP_Tools-Optional-blue.svg)](https://github.com/modelcontextprotocol)
-
-**MCP (Model Context Protocol) tools provide enhanced codebase analysis capabilities. They are completely optional - CCW works perfectly without them.**
-
-#### **Quick MCP Setup**
-1. **Install MCP Servers** (choose what you need):
-   ```bash
-   # Option 1: Exa MCP Server (External API patterns)
-   # 📋 Installation Guide: https://github.com/exa-labs/exa-mcp-server
-
-   # Option 2: Code Index MCP (Advanced code search)
-   # 📋 Installation Guide: https://github.com/johnhuang316/code-index-mcp
-   ```
-
-2. **Configure Claude Code IDE**:
-   - Follow the MCP server installation guides above
-   - Restart Claude Code IDE after MCP server installation
-   - CCW will automatically detect and use available MCP tools
-
-#### **Benefits When Enabled**
-- 📊 **Faster Analysis**: Direct codebase indexing vs manual searching
-- 🌐 **External Context**: Real-world API patterns and examples
-- 🔍 **Advanced Search**: Pattern matching and similarity detection
-- ⚡ **Automatic Fallback**: Uses traditional tools when MCP unavailable
-
-#### **Configuration Resources**
-| MCP Server | Installation Guide | Purpose |
-|------------|-------------------|---------|
-| 🌐 **Exa MCP** | [Installation Guide](https://github.com/exa-labs/exa-mcp-server) | External API patterns & best practices |
-| 🔍 **Code Index MCP** | [Installation Guide](https://github.com/johnhuang316/code-index-mcp) | Advanced internal codebase search |
-| 📖 **MCP Protocol** | [Official Documentation](https://github.com/modelcontextprotocol) | Technical specifications |
-
-> **💡 Pro Tip**: Start with basic CCW functionality, then add MCP tools when you want enhanced analysis capabilities.
+This ensures CCW's intelligent documentation system works seamlessly with the Gemini CLI.
 
 ---
 
-## 🤝 Contributing
+## 🤝 Contributing & Support
 
-### 🛠️ **Development Setup**
-1. 🍴 Fork the repository
-2. 🌿 Create feature branch: `git checkout -b feature/enhancement-name`
-3. 📦 Install dependencies
-4. ✅ Test with sample projects
-5. 📤 Submit detailed pull request
-
-### 📏 **Code Standards**
-- ✅ Follow existing command patterns
-- 🔄 Maintain backward compatibility
-- 🧪 Add tests for new functionality
-- 📚 Update documentation
-- 🏷️ Use semantic versioning
-
----
-
-## 📞 Support & Resources
-
-<div align="center">
-
-| Resource | Link | Description |
-|----------|------|-------------|
-| 📚 **Documentation** | [Project Wiki](https://github.com/catlog22/Claude-Code-Workflow/wiki) | Comprehensive guides |
-| 🐛 **Issues** | [GitHub Issues](https://github.com/catlog22/Claude-Code-Workflow/issues) | Bug reports & features |
-| 💬 **Discussions** | [Community Forum](https://github.com/catlog22/Claude-Code-Workflow/discussions) | Community support |
-| 📋 **Changelog** | [Release History](CHANGELOG.md) | Version history |
-
-</div>
-
----
+- **Repository**: [GitHub - Claude-Code-Workflow](https://github.com/catlog22/Claude-Code-Workflow)
+- **Issues**: Report bugs or request features on [GitHub Issues](https://github.com/catlog22/Claude-Code-Workflow/issues).
+- **Discussions**: Join the [Community Forum](https://github.com/catlog22/Claude-Code-Workflow/discussions).
 
 ## 📄 License
 
-This project is licensed under the **MIT License** - see the [LICENSE](LICENSE) file for details.
-
----
-
-<div align="center">
-
-**🚀 Claude Code Workflow (CCW)**
-
-*Professional software development workflow automation through intelligent multi-agent coordination and autonomous execution capabilities.*
-
-[![⭐ Star on GitHub](https://img.shields.io/badge/⭐-Star%20on%20GitHub-yellow.svg)](https://github.com/catlog22/Claude-Code-Workflow)
-
-</div>
+This project is licensed under the **MIT License**. See the [LICENSE](LICENSE) file for details.

README_CN.md

@@ -2,7 +2,7 @@
 
 <div align="center">
 
-[![Version](https://img.shields.io/badge/version-v2.1.0--experimental-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
+[![Version](https://img.shields.io/badge/version-v3.0.1-blue.svg)](https://github.com/catlog22/Claude-Code-Workflow/releases)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20Linux%20%7C%20macOS-lightgrey.svg)]()
 [![MCP工具](https://img.shields.io/badge/🔧_MCP工具-实验性-orange.svg)](https://github.com/modelcontextprotocol)
@@ -13,663 +13,129 @@
 
 ---
 
-## 📋 概述
+**Claude Code Workflow (CCW)** 是一个新一代的多智能体自动化开发框架，通过智能工作流管理和自主执行来协调复杂的软件开发任务。
 
-**Claude Code Workflow (CCW)** 是新一代多智能体自动化开发框架，通过智能工作流管理和自主执行协调复杂的软件开发任务。
-
-> **🧪 最新版本 v2.1.0-experimental**: 引入**实验性 MCP (模型上下文协议) 工具集成**，实现增强的代码库分析和外部上下文获取。包含用于外部 API 模式的 Exa MCP Server 和用于高级内部代码库探索的 Code Index MCP。详见 [CHANGELOG.md](CHANGELOG.md)。
-
-> **⚠️ 实验性功能**: MCP 工具是可选的实验性功能。所有现有功能保持稳定。
-
-### 🌟 核心创新
-
-- **🔄 增强的工作流生命周期**: 完整开发周期：头脑风暴 → 规划 → 验证 → 执行 → 测试 → 审查
-- **🧪 自动测试生成**: 全面的测试工作流生成 (`/workflow:test-gen`) 与完整覆盖规划
-- **✅ 计划验证系统**: 使用 Gemini/Codex 双重分析的执行前验证 (`/workflow:plan-verify`)
-- **🎯 JSON优先架构**: 具有原子会话管理的单一数据源
-- **💡 头脑风暴产物**: 多视角规划与综合和结构化文档生成
-- **🚀 MCP 工具集成**: 通过模型上下文协议实现增强的代码库分析和外部上下文获取
-
-### 🔧 MCP 工具增强 (NEW!)
-
-**通过 MCP (Model Context Protocol) 工具实现的高级代码库分析:**
-
-#### 必需的 MCP 服务器
-1. **Exa MCP Server** - 外部 API 模式和示例
-   - 仓库: https://github.com/exa-labs/exa-mcp-server
-   - 功能: `mcp__exa__get_code_context_exa()` - 获取外部最佳实践
-
-2. **Code Index MCP** - 内部代码库探索
-   - 仓库: https://github.com/johnhuang316/code-index-mcp
-   - 功能:
-     - `mcp__code-index__find_files()` - 文件模式匹配
-     - `mcp__code-index__search_code_advanced()` - 高级代码搜索
-
-#### MCP 集成优势
-- **📊 更快分析**: 直接代码库索引 vs 手动文件搜索
-- **🌐 外部上下文**: 真实世界的 API 模式和实现示例
-- **🔍 模式识别**: 高级代码模式匹配和相似性检测
-- **📈 全面覆盖**: 内部代码探索和外部最佳实践查找
-- **⚡ 自动回退**: 如果 MCP 工具不可用，工作流使用传统 bash/CLI 工具
-
-#### 安装和设置
-请安装这些 MCP 服务器以启用增强的代码库分析。工作流将在可用时自动使用它们。
+> **🎉 最新版本: v3.0.1** - 文档优化和头脑风暴角色更新。详见 [CHANGELOG.md](CHANGELOG.md)。
+>
+> **v3.0.0 版本**: 引入了**统一的 CLI 命令结构**。`/cli:*` 命令通过 `--tool` 标志整合了所有工具（Gemini, Qwen, Codex）的交互。
 
 ---
 
-## 🏗️ 系统架构
+## ✨ 核心特性
 
-### 🏛️ **四层架构**
-
-CCW 通过四个不同的架构层运行，具有明确的职责和数据契约：
-
-| 层级 | 组件 | 数据流 | 集成点 |
-|------|------|--------|--------|
-| **🖥️ 接口层** | CLI 命令、Gemini/Codex/Qwen 包装器 | 用户输入 → 命令 → 智能体 | 外部 CLI 工具、审批模式 |
-| **📋 会话层** | `.active-[session]` 标记、`workflow-session.json` | 会话状态 → 任务发现 | 原子会话切换 |
-| **📊 任务/数据层** | `.task/impl-*.json`、层次管理 | 任务定义 → 智能体执行 | JSON优先模型、生成视图 |
-| **🤖 编排层** | 多智能体协调、依赖解析 | 智能体输出 → 任务更新 | 智能执行流程 |
-
-### **系统架构可视化**
-
-```mermaid
-graph TB
-    subgraph "CLI接口层"
-        CLI[CLI命令]
-        GEM[Gemini CLI]
-        COD[Codex CLI]
-        WRAPPER[Gemini包装器]
-    end
-
-    subgraph "会话管理"
-        MARKER[".active-session 标记"]
-        SESSION["workflow-session.json"]
-        WDIR[".workflow/ 目录"]
-    end
-
-    subgraph "任务系统"
-        TASK_JSON[".task/impl-*.json"]
-        HIERARCHY["任务层次结构（最多2级）"]
-        STATUS["任务状态管理"]
-    end
-
-    subgraph "智能体编排"
-        PLAN_AGENT[概念规划智能体]
-        ACTION_AGENT[行动规划智能体]
-        CODE_AGENT[代码开发智能体]
-        REVIEW_AGENT[代码审查智能体]
-        MEMORY_AGENT[记忆桥接智能体]
-    end
-
-    CLI --> GEM
-    CLI --> COD
-    CLI --> WRAPPER
-    WRAPPER --> GEM
-
-    GEM --> PLAN_AGENT
-    COD --> CODE_AGENT
-
-    PLAN_AGENT --> TASK_JSON
-    ACTION_AGENT --> TASK_JSON
-    CODE_AGENT --> TASK_JSON
-
-    TASK_JSON --> HIERARCHY
-    HIERARCHY --> STATUS
-
-    SESSION --> MARKER
-    MARKER --> WDIR
-```
-
-### **JSON优先数据模型**
-- **单一数据源**: 所有工作流状态和任务定义存储在结构化的 `.task/impl-*.json` 文件中
-- **任务特定路径**: 新增 `paths` 字段实现针对具体项目路径的精准CLI分析
-- **生成视图**: 从JSON数据源按需创建Markdown文档
-- **数据一致性**: 通过集中式数据管理消除同步问题
-- **性能**: 直接JSON操作，亚毫秒级查询响应时间
-
-### **原子化会话管理**
-- **标记文件系统**: 通过原子化的 `.workflow/.active-[session]` 文件管理会话状态
-- **即时上下文切换**: 零开销的会话管理和切换
-- **冲突解决**: 自动检测和解决会话状态冲突
-- **可扩展性**: 支持并发会话而无性能下降
+- **🤖 多智能体系统**: 用于规划、编码、测试和审查的专用智能体。
+- **🔄 端到端工作流自动化**: 从头脑风暴 (`/workflow:brainstorm`) 到部署的完整流程。
+- **🎯 JSON 优先架构**: 使用 JSON 作为任务的唯一真实数据源，确保一致性。
+- **🧪 自动测试生成**: 基于实现分析创建全面的测试套件。
+- **✅ 执行前验证**: 通过战略（Gemini）和技术（Codex）双重分析验证计划。
+- **🔧 统一 CLI**: 一个强大、统一的 `/cli:*` 命令集，用于与各种 AI 工具交互。
+- **🧠 智能上下文管理**: 自动管理和更新项目文档 (`CLAUDE.md`)。
 
 ---
 
-## 📊 复杂度管理系统
+## ⚙️ 安装
 
-CCW 根据项目复杂度自动调整工作流结构：
+### **🚀 一键快速安装**
 
-| **复杂度** | **任务数量** | **结构** | **功能** |
-|---|---|---|---|
-| 🟢 **简单** | <5 任务 | 单级层次结构 | 最小开销，直接执行 |
-| 🟡 **中等** | 5-10 任务 | 两级层次结构 | 进度跟踪，自动文档 |
-| 🔴 **复杂** | >10 任务 | 强制重新划分范围 | 需要多迭代规划 |
-
----
-
-### **命令执行流程**
-
-```mermaid
-sequenceDiagram
-    participant User as 用户
-    participant CLI
-    participant GeminiWrapper as Gemini包装器
-    participant GeminiCLI as Gemini CLI
-    participant CodexCLI as Codex CLI
-    participant Agent as 智能体
-    participant TaskSystem as 任务系统
-    participant FileSystem as 文件系统
-
-    User->>CLI: 命令请求
-    CLI->>CLI: 解析命令类型
-
-    alt 分析任务
-        CLI->>GeminiWrapper: 分析请求
-        GeminiWrapper->>GeminiWrapper: 检查令牌限制
-        GeminiWrapper->>GeminiWrapper: 设置审批模式
-        GeminiWrapper->>GeminiCLI: 执行分析
-        GeminiCLI->>FileSystem: 读取代码库
-        GeminiCLI->>Agent: 路由到规划智能体
-    else 开发任务
-        CLI->>CodexCLI: 开发请求
-        CodexCLI->>Agent: 路由到代码智能体
-    end
-
-    Agent->>TaskSystem: 创建/更新任务
-    TaskSystem->>FileSystem: 保存任务JSON
-    Agent->>Agent: 执行任务逻辑
-    Agent->>FileSystem: 应用变更
-    Agent->>TaskSystem: 更新任务状态
-    TaskSystem->>FileSystem: 重新生成Markdown视图
-    Agent->>CLI: 返回结果
-    CLI->>User: 显示结果
-```
-
-## 完整开发工作流示例
-
-### 🚀 **增强的工作流生命周期**
-
-```mermaid
-graph TD
-    START[🎯 新功能请求] --> SESSION["/workflow:session:start 'OAuth2系统'"]
-    SESSION --> BRAINSTORM["/workflow:brainstorm:system-architect 主题"]
-    BRAINSTORM --> SYNTHESIS["/workflow:brainstorm:synthesis"]
-    SYNTHESIS --> PLAN["/workflow:plan 描述"]
-    PLAN --> VERIFY["/workflow:plan-verify"]
-    VERIFY --> EXECUTE["/workflow:execute"]
-    EXECUTE --> TEST["/workflow:test-gen WFS-session-id"]
-    TEST --> REVIEW["/workflow:review"]
-    REVIEW --> DOCS["/workflow:docs all"]
-    DOCS --> COMPLETE[✅ 完成]
-```
-
-### ⚡ **工作流会话管理**
-
-```mermaid
-graph LR
-    START[📋 会话开始] --> MARKER[🏷️ .active-session 标记]
-    MARKER --> JSON[📊 workflow-session.json]
-    JSON --> TASKS[🎯 .task/impl-*.json]
-    TASKS --> PAUSE[⏸️ 暂停：删除标记]
-    PAUSE --> RESUME[▶️ 恢复：恢复标记]
-    RESUME --> SWITCH[🔄 切换：更改活跃会话]
-```
-
-### 🎯 **规划方法选择指南**
-| 项目类型 | 推荐流程 | 命令序列 |
-|----------|----------|----------|
-| **Bug修复** | 直接规划 | `/workflow:plan` → `/task:execute` |
-| **小功能** | Gemini分析 | `/gemini:mode:plan` → `/workflow:execute` |
-| **中等功能** | 文档+Gemini | 查看文档 → `/gemini:analyze` → `/workflow:plan` |
-| **大型系统** | 完整头脑风暴 | `/workflow:brainstorm` → 综合 → `/workflow:plan-deep` |
-
-### ✨ v2.0 主要增强功能
-
-### 🔄 **增强的工作流生命周期**
-每个阶段都有质量门禁的完整开发生命周期：
-
-1. **💡 头脑风暴阶段** - 基于角色分析的多视角概念规划
-2. **📋 规划阶段** - 结构化实现规划与任务分解
-3. **✅ 验证阶段** - 使用 Gemini（战略）+ Codex（技术）的执行前验证
-4. **⚡ 执行阶段** - 多智能体编排的自主实现
-5. **🧪 测试阶段** - 全面覆盖的自动测试工作流生成
-6. **🔍 审查阶段** - 质量保证和完成验证
-
-### 🧪 **自动测试生成**
-全面的测试工作流创建：
-- **实现分析**: 扫描已完成的 IMPL-* 任务以确定测试需求
-- **多层测试**: 单元、集成、E2E、性能、安全测试
-- **智能体分配**: 不同测试类型的专门测试智能体
-- **依赖映射**: 测试执行遵循实现依赖链
-
-### ✅ **计划验证系统**
-执行前的双引擎验证：
-- **Gemini 战略分析**: 高级可行性和架构合理性
-- **Codex 技术分析**: 实现细节和技术可行性
-- **交叉验证**: 识别战略愿景与技术约束之间的冲突
-- **改进建议**: 实现开始前的可行性建议
-
-## 核心组件
-
-### 多智能体系统
-- **概念规划智能体**: 战略规划和架构设计
-- **行动规划智能体**: 将高层概念转换为可执行的实现计划
-- **代码开发智能体**: 自主代码实现和重构
-- **代码审查智能体**: 质量保证和合规性验证
-- **记忆桥接智能体**: 智能文档管理和更新
-
-### 双CLI集成
-- **Gemini CLI**: 深度代码库分析，模式识别和调查工作流
-- **Codex CLI**: 自主开发，代码生成和实现自动化
-- **任务特定定位**: 精准路径管理实现聚焦分析（替代 `--all-files`）
-- **模板系统**: 统一模板库确保一致的工作流执行
-- **跨平台支持**: Windows和Linux兼容性，统一路径处理
-
-### 工作流会话管理
-- **会话生命周期**: 创建，暂停，恢复，切换和管理开发会话
-- **上下文保持**: 在会话转换过程中维持完整的工作流状态
-- **层次化组织**: 结构化工作流文件系统，自动初始化
-
-### 智能文档系统
-- **活文档**: 四层级分层CLAUDE.md系统，自动更新
-- **Git集成**: 基于仓库变更的上下文感知更新
-- **双更新模式**: 
-  - `related`: 仅更新受近期变更影响的模块
-  - `full`: 完整的项目级文档刷新
-
-## 安装
-
-### 快速安装
+**Windows (PowerShell):**
 ```powershell
 Invoke-Expression (Invoke-WebRequest -Uri "https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.ps1" -UseBasicParsing).Content
 ```
 
-### 验证安装
+**Linux/macOS (Bash/Zsh):**
+```bash
+bash <(curl -fsSL https://raw.githubusercontent.com/catlog22/Claude-Code-Workflow/main/install-remote.sh)
+```
+
+### **✅ 验证安装**
+安装后，运行以下命令以确保 CCW 正常工作：
 ```bash
 /workflow:session:list
 ```
 
-### 必需配置
-对于Gemini CLI集成，配置您的设置：
-```json
-{
-  "contextFileName": "CLAUDE.md"
-}
-```
+---
 
-## 完整命令参考
+## 🚀 快速入门：一个简单的工作流
 
-### 核心系统命令
+1.  **启动一个新的工作流会话：**
+    ```bash
+    /workflow:session:start "创建一个新的用户认证功能"
+    ```
 
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `🎯 /enhance-prompt` | `/enhance-prompt "添加认证系统"` | 技术上下文增强 |
-| `📊 /context` | `/context --analyze --format=tree` | 统一上下文管理 |
-| `📝 /update-memory-full` | `/update-memory-full` | 完整文档更新 |
-| `🔄 /update-memory-related` | `/update-memory-related` | 智能上下文感知更新 |
+2.  **生成一个实现计划：**
+    ```bash
+    /workflow:plan "实现基于JWT的用户认证"
+    ```
 
-### 🔍 Gemini CLI命令（分析与调查）
+3.  **使用 AI 智能体执行计划：**
+    ```bash
+    /workflow:execute
+    ```
 
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `🔍 /gemini:analyze` | `/gemini:analyze "认证模式"` | 深度代码库分析 |
-| `💬 /gemini:chat` | `/gemini:chat "解释这个架构"` | 直接Gemini交互 |
-| `⚡ /gemini:execute` | `/gemini:execute "实现任务-001"` | 智能执行（YOLO权限） |
-| `🎯 /gemini:mode:auto` | `/gemini:mode:auto "分析安全漏洞"` | 自动模板选择 |
-| `🐛 /gemini:mode:bug-index` | `/gemini:mode:bug-index "支付处理失败"` | 错误分析和修复建议 |
-| `📋 /gemini:mode:plan` | `/gemini:mode:plan "微服务架构"` | 项目规划和架构 |
-| `🎯 /gemini:mode:plan-precise` | `/gemini:mode:plan-precise "复杂重构"` | 精确路径规划分析 |
-
-### 🔮 Qwen CLI命令（架构与代码生成）
-
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `🔍 /qwen:analyze` | `/qwen:analyze "系统架构模式"` | 架构分析和代码质量 |
-| `💬 /qwen:chat` | `/qwen:chat "设计认证系统"` | 直接Qwen交互 |
-| `⚡ /qwen:execute` | `/qwen:execute "实现用户认证"` | 智能实现（YOLO权限） |
-| `🚀 /qwen:mode:auto` | `/qwen:mode:auto "构建微服务API"` | 自动模板选择和执行 |
-| `🐛 /qwen:mode:bug-index` | `/qwen:mode:bug-index "服务内存泄漏"` | 错误分析和修复建议 |
-| `📋 /qwen:mode:plan` | `/qwen:mode:plan "设计可扩展数据库"` | 架构规划和分析 |
-| `🎯 /qwen:mode:plan-precise` | `/qwen:mode:plan-precise "复杂系统迁移"` | 精确架构规划 |
-
-### 🤖 Codex CLI命令（开发与实现）
-
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `🔍 /codex:analyze` | `/codex:analyze "优化机会"` | 开发分析 |
-| `💬 /codex:chat` | `/codex:chat "实现JWT认证"` | 直接Codex交互 |
-| `⚡ /codex:execute` | `/codex:execute "重构用户服务"` | 自主实现（YOLO权限） |
-| `🚀 /codex:mode:auto` | `/codex:mode:auto "构建支付系统"` | **主要模式**: 完全自主开发 |
-| `🐛 /codex:mode:bug-index` | `/codex:mode:bug-index "修复竞态条件"` | 自主错误修复和实现 |
-| `📋 /codex:mode:plan` | `/codex:mode:plan "实现API端点"` | 开发规划和实现 |
-
-### 工作流管理命令
-
-#### 会话管理
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `/workflow:session:start` | `/workflow:session:start "<会话名称>"` | 创建并激活新的工作流会话 |
-| `/workflow:session:pause` | `/workflow:session:pause` | 暂停当前活跃会话 |
-| `/workflow:session:resume` | `/workflow:session:resume "<会话名称>"` | 恢复暂停的工作流会话 |
-| `/workflow:session:list` | `/workflow:session:list [--active\|--all]` | 列出工作流会话及状态 |
-| `/workflow:session:switch` | `/workflow:session:switch "<会话名称>"` | 切换到不同的工作流会话 |
-| `/workflow:session:status` | `/workflow:session:status` | 显示当前会话信息 |
-
-#### 工作流操作
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `💭 /workflow:brainstorm:*` | `/workflow:brainstorm:system-architect "微服务"` | 角色专家的多视角规划 |
-| `🤝 /workflow:brainstorm:synthesis` | `/workflow:brainstorm:synthesis` | 综合所有头脑风暴视角 |
-| `🎨 /workflow:brainstorm:artifacts` | `/workflow:brainstorm:artifacts "主题描述"` | 生成结构化规划文档 |
-| `📋 /workflow:plan` | `/workflow:plan "描述" \| file.md \| ISS-001` | 转换为可执行实现计划 |
-| `🔍 /workflow:plan-deep` | `/workflow:plan-deep "需求描述"` | Gemini分析的深度技术规划 |
-| `✅ /workflow:plan-verify` | `/workflow:plan-verify` | 双分析的执行前验证 |
-| `⚡ /workflow:execute` | `/workflow:execute` | 协调智能体进行实现 |
-| `🔄 /workflow:resume` | `/workflow:resume [--from TASK-ID] [--retry]` | 智能工作流恢复 |
-| `📊 /workflow:status` | `/workflow:status [task-id] [format] [validation]` | 从任务数据生成按需视图 |
-| `🧪 /workflow:test-gen` | `/workflow:test-gen WFS-session-id` | 生成全面测试工作流 |
-| `🔍 /workflow:review` | `/workflow:review` | 执行质量验证审查阶段 |
-| `📚 /workflow:docs` | `/workflow:docs "architecture" \| "api" \| "all"` | 生成分层文档 |
-
-#### 🏷️ 问题管理
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `➕ /workflow:issue:create` | `/workflow:issue:create "API 速率限制" --priority=high` | 创建新项目问题 |
-| `📋 /workflow:issue:list` | `/workflow:issue:list --status=open --assigned=system-architect` | 列出和过滤问题 |
-| `📝 /workflow:issue:update` | `/workflow:issue:update ISS-001 --status=in-progress` | 更新现有问题 |
-| `✅ /workflow:issue:close` | `/workflow:issue:close ISS-001 --reason=resolved` | 关闭已完成问题 |
-
-### 任务管理命令
-
-| 命令 | 语法 | 描述 |
-|------|------|------|
-| `➕ /task:create` | `/task:create "用户认证系统"` | 创建带上下文的实现任务 |
-| `🔄 /task:breakdown` | `/task:breakdown task-id` | 智能任务分解 |
-| `⚡ /task:execute` | `/task:execute task-id` | 用适当的智能体执行任务 |
-| `📋 /task:replan` | `/task:replan task-id ["text" \| file.md \| ISS-001]` | 用详细输入重新规划任务 |
-
-#### 🧠 头脑风暴角色命令
-| 角色 | 命令 | 目的 |
-|------|---------|----------|
-| 🏗️ **系统架构师** | `/workflow:brainstorm:system-architect` | 技术架构分析 |
-| 🔒 **安全专家** | `/workflow:brainstorm:security-expert` | 安全和威胁分析 |
-| 📊 **产品经理** | `/workflow:brainstorm:product-manager` | 用户需求和商业价值 |
-| 🎨 **UI设计师** | `/workflow:brainstorm:ui-designer` | 用户体验和界面 |
-| 📈 **业务分析师** | `/workflow:brainstorm:business-analyst` | 流程优化分析 |
-| 🔬 **创新负责人** | `/workflow:brainstorm:innovation-lead` | 新兴技术机会 |
-| 📋 **功能规划师** | `/workflow:brainstorm:feature-planner` | 功能开发规划 |
-| 🗄️ **数据架构师** | `/workflow:brainstorm:data-architect` | 数据建模和分析 |
-| 👥 **用户研究员** | `/workflow:brainstorm:user-researcher` | 用户行为分析 |
-| 🚀 **自动选择** | `/workflow:brainstorm:auto` | 动态角色选择 |
-
-### 头脑风暴角色命令
-
-| 命令 | 描述 |
-|------|------|
-| `/workflow:brainstorm:business-analyst` | 业务需求和市场分析 |
-| `/workflow:brainstorm:data-architect` | 数据建模和架构规划 |
-| `/workflow:brainstorm:feature-planner` | 功能规范和用户故事 |
-| `/workflow:brainstorm:innovation-lead` | 技术创新和新兴解决方案 |
-| `/workflow:brainstorm:product-manager` | 产品策略和路线图规划 |
-| `/workflow:brainstorm:security-expert` | 安全分析和威胁建模 |
-| `/workflow:brainstorm:system-architect` | 系统设计和技术架构 |
-| `/workflow:brainstorm:ui-designer` | 用户界面和体验设计 |
-| `/workflow:brainstorm:user-researcher` | 用户需求分析和研究洞察 |
-| `/workflow:brainstorm:synthesis` | 整合和综合多个视角 |
-
-## 使用工作流
-
-### 完整功能开发工作流
-```bash
-# 1. 初始化专注会话
-/workflow:session:start "用户仪表盘功能"
-
-# 2. 多视角头脑风暴
-/workflow:brainstorm:system-architect "仪表盘分析系统"
-/workflow:brainstorm:ui-designer "仪表盘用户体验"
-/workflow:brainstorm:data-architect "分析数据流"
-
-# 3. 综合所有视角
-/workflow:brainstorm:synthesis
-
-# 4. 创建可执行实现计划
-/workflow:plan "用户仪表盘与分析和实时数据"
-
-# 5. 执行前验证计划
-/workflow:plan-verify
-
-# 6. 智能体协调执行实现
-/workflow:execute
-
-# 7. 生成全面测试套件
-/workflow:test-gen WFS-user-dashboard-feature
-
-# 8. 质量保证和审查
-/workflow:review
-
-# 9. 生成文档
-/workflow:docs "all"
-```
-
-### 快速错误解决
-```bash
-# 快速错误修复工作流
-/workflow:session:start "支付处理修复"
-/gemini:mode:bug-index "并发请求时支付验证失败"
-/codex:mode:bug-index "修复支付验证竞态条件"
-/workflow:review
-```
-
-### 架构分析与重构
-```bash
-# 深度架构工作流
-/workflow:session:start "API重构倡议"
-/gemini:analyze "当前API架构模式和技术债务"
-/workflow:plan-deep "微服务转换策略"
-/workflow:plan-verify
-/qwen:mode:auto "重构单体架构为微服务架构"
-/workflow:test-gen WFS-api-refactoring-initiative
-/workflow:review
-```
-
-### 项目文档管理
-```bash
-# 日常开发工作流
-/update-memory-related
-
-# 重大变更后
-git commit -m "功能实现完成"
-/update-memory-related
-
-# 项目级刷新
-/update-memory-full
-
-# 模块特定更新
-cd src/api && /update-memory-related
-```
-
-## 目录结构
-
-```
-.claude/
-├── agents/                 # AI智能体定义和行为
-├── commands/              # CLI命令实现
-├── output-styles/         # 输出格式模板
-├── planning-templates/    # 角色特定的规划方法
-├── prompt-templates/      # AI交互模板
-├── scripts/              # 自动化和实用脚本
-├── tech-stack-templates/ # 技术栈特定配置
-├── workflows/            # 核心工作流文档
-│   ├── system-architecture.md         # 架构规范
-│   ├── data-model.md                 # JSON数据模型标准
-│   ├── complexity-rules.md           # 复杂度管理规则
-│   ├── session-management-principles.md # 会话系统设计
-│   ├── file-structure-standards.md   # 目录组织
-│   ├── intelligent-tools-strategy.md # 工具选择策略指南
-│   └── tools-implementation-guide.md # 工具实施详细指南
-└── settings.local.json   # 本地环境配置
-
-.workflow/                 # 会话工作空间（自动生成）
-├── .active-[session] # 活跃会话标记文件
-└── WFS-[topic-slug]/      # 个别会话目录
-    ├── workflow-session.json      # 会话元数据
-    ├── .task/impl-*.json          # JSON任务定义
-    ├── IMPL_PLAN.md               # 生成的规划文档
-    └── .summaries/                # 完成摘要
-```
-
-## 技术规范
-
-### 性能指标
-- **会话切换**: 平均<10ms
-- **JSON查询响应**: 平均<1ms
-- **文档更新**: 中型项目<30s
-- **上下文加载**: 复杂代码库<5s
-
-### 系统要求
-- **操作系统**: Windows 10+, Ubuntu 18.04+, macOS 10.15+
-- **依赖项**: Git, Node.js（用于Gemini CLI）, Python 3.8+（用于Codex CLI）
-- **存储**: 核心安装约50MB，项目数据可变
-- **内存**: 最低512MB，复杂工作流推荐2GB
-
-### 集成要求
-- **🔍 Gemini CLI**: 分析和战略规划工作流必需
-- **🤖 Codex CLI**: 自主开发和错误修复必需
-- **🔮 Qwen CLI**: 架构分析和代码生成必需
-- **📂 Git仓库**: 变更跟踪和版本控制必需
-- **🎯 Claude Code IDE**: 推荐用于最佳体验
-- **🔧 MCP 服务器**: 推荐用于增强代码库分析
-  - **Exa MCP Server**: 外部 API 模式和最佳实践获取
-  - **Code Index MCP**: 高级内部代码库搜索和索引
-
-## 配置
-
-### 必需配置
-为了实现最佳的CCW集成效果，请配置Gemini CLI设置：
-
-```json
-// ~/.gemini/settings.json 或 .gemini/settings.json
-{
-  "contextFileName": "CLAUDE.md"
-}
-```
-
-此设置确保CCW的智能文档系统能够与Gemini CLI工作流正确集成。
-
-### .geminiignore 配置
-
-为了优化Gemini CLI性能并减少上下文噪声，请在项目根目录配置 `.geminiignore` 文件。此文件可以排除无关文件的分析，提供更清洁的上下文和更快的处理速度。
-
-#### 创建 .geminiignore
-在项目根目录创建 `.geminiignore` 文件：
-
-```bash
-# 排除构建输出和依赖项
-/dist/
-/build/
-/node_modules/
-/.next/
-
-# 排除临时文件
-*.tmp
-*.log
-/temp/
-
-# 排除敏感文件
-/.env
-/config/secrets.*
-apikeys.txt
-
-# 排除大型数据文件
-*.csv
-*.json
-*.sql
-
-# 包含重要文档（取反模式）
-!README.md
-!CHANGELOG.md
-!**/CLAUDE.md
-```
-
-#### 配置优势
-- **提升性能**: 通过排除无关文件实现更快的分析速度
-- **更好的上下文**: 没有构建产物的更清洁分析结果
-- **减少令牌使用**: 通过过滤不必要内容降低成本
-- **增强专注度**: 通过相关上下文获得更好的AI理解
-
-#### 最佳实践
-- 始终排除 `node_modules/`、`dist/`、`build/` 目录
-- 过滤日志文件、临时文件和构建产物
-- 保留文档文件（使用 `!` 包含特定模式）
-- 项目结构变更时更新 `.geminiignore`
-- 修改 `.geminiignore` 后重启Gemini CLI会话
-
-**注意**: 与 `.gitignore` 不同，`.geminiignore` 仅影响Gemini CLI操作，不会影响Git版本控制。
-
-### 🔧 **MCP 工具配置** *(可选增强)*
-
-[![MCP工具](https://img.shields.io/badge/🔧_MCP工具-可选-blue.svg)](https://github.com/modelcontextprotocol)
-
-**MCP (模型上下文协议) 工具提供增强的代码库分析能力。它们完全是可选的 - CCW 在没有它们的情况下也能完美工作。**
-
-#### **快速 MCP 设置**
-1. **安装 MCP 服务器** (选择您需要的):
-   ```bash
-   # 选项 1: Exa MCP Server (外部 API 模式)
-   # 📋 安装指南: https://github.com/exa-labs/exa-mcp-server
-
-   # 选项 2: Code Index MCP (高级代码搜索)
-   # 📋 安装指南: https://github.com/johnhuang316/code-index-mcp
-   ```
-
-2. **配置 Claude Code IDE**:
-   - 按照上述 MCP 服务器安装指南操作
-   - 安装 MCP 服务器后重启 Claude Code IDE
-   - CCW 将自动检测并使用可用的 MCP 工具
-
-#### **启用后的好处**
-- 📊 **更快分析**: 直接代码库索引 vs 手动搜索
-- 🌐 **外部上下文**: 真实世界的 API 模式和示例
-- 🔍 **高级搜索**: 模式匹配和相似性检测
-- ⚡ **自动回退**: MCP 不可用时使用传统工具
-
-#### **配置资源**
-| MCP 服务器 | 安装指南 | 用途 |
-|------------|---------|------|
-| 🌐 **Exa MCP** | [安装指南](https://github.com/exa-labs/exa-mcp-server) | 外部 API 模式和最佳实践 |
-| 🔍 **Code Index MCP** | [安装指南](https://github.com/johnhuang316/code-index-mcp) | 高级内部代码库搜索 |
-| 📖 **MCP 协议** | [官方文档](https://github.com/modelcontextprotocol) | 技术规范 |
-
-> **💡 专业提示**: 从基本的 CCW 功能开始，然后在需要增强分析能力时添加 MCP 工具。
-
-## 贡献
-
-### 开发设置
-1. Fork仓库
-2. 创建功能分支: `git checkout -b feature/enhancement-name`
-3. 安装依赖: `npm install` 或适合您环境的等效命令
-4. 按照现有模式进行更改
-5. 使用示例项目测试
-6. 提交详细描述的拉取请求
-
-### 代码标准
-- 遵循现有的命令结构模式
-- 维护公共API的向后兼容性
-- 为新功能添加测试
-- 更新面向用户的变更文档
-- 使用语义版本控制进行发布
-
-## 支持和资源
-
-- **文档**: [项目Wiki](https://github.com/catlog22/Claude-Code-Workflow/wiki)
-- **问题**: [GitHub Issues](https://github.com/catlog22/Claude-Code-Workflow/issues)
-- **讨论**: [社区论坛](https://github.com/catlog22/Claude-Code-Workflow/discussions)
-- **变更日志**: [发布历史](CHANGELOG.md)
-
-## 许可证
-
-此项目根据MIT许可证授权 - 详见[LICENSE](LICENSE)文件。
+4.  **检查状态：**
+    ```bash
+    /workflow:status
+    ```
 
 ---
 
-**Claude Code Workflow (CCW)** - 通过智能体协调和自主执行能力实现专业的软件开发工作流自动化。
+## 🛠️ 命令参考
+
+### **统一 CLI 命令 (`/cli:*)**
+*使用 `--tool <gemini|qwen|codex>` 标志选择所需工具。默认为 `gemini`。*
+
+| 命令 | 描述 |
+|---|---|
+| `/cli:analyze` | 深度代码库分析。 |
+| `/cli:chat` | 与工具进行直接的交互式聊天。 |
+| `/cli:execute` | 以完全权限执行任务。 |
+| `/cli:cli-init`| 为工作区初始化CLI工具配置。 |
+| `/cli:mode:bug-index` | 分析错误并提出修复建议。 |
+| `/cli:mode:code-analysis` | 执行深度代码分析和调试。 |
+| `/cli:mode:plan` | 项目规划和架构分析。 |
+
+### **工作流命令 (`/workflow:*)**
+
+| 命令 | 描述 |
+|---|---|
+| `/workflow:session:*` | 管理开发会话（`start`, `pause`, `resume`, `list`, `switch`, `complete`）。 |
+| `/workflow:brainstorm:*` | 使用基于角色的智能体进行多视角规划。 |
+| `/workflow:plan` | 从描述创建详细、可执行的计划。 |
+| `/workflow:execute` | 自主执行当前的工作流计划。 |
+| `/workflow:status` | 显示工作流的当前状态。 |
+| `/workflow:test-gen` | 从实现中自动生成测试计划。 |
+| `/workflow:review` | 对已完成的工作启动质量保证审查。 |
+
+### **任务与内存命令**
+
+| 命令 | 描述 |
+|---|---|
+| `/task:*` | 管理单个任务（`create`, `breakdown`, `execute`, `replan`）。 |
+| `/update-memory-full` | 重新索引整个项目文档。 |
+| `/update-memory-related` | 更新与最近更改相关的文档。 |
+
+---
+
+## ⚙️ 核心配置
+
+为实现最佳集成，请在 `~/.gemini/` 中创建一个 `settings.json` 文件来配置您的 Gemini CLI 设置：
+
+```json
+// ~/.gemini/settings.json
+{
+  "contextFileName": "CLAUDE.md"
+}
+```
+这确保了 CCW 的智能文档系统能与 Gemini CLI 无缝协作。
+
+---
+
+## 🤝 贡献与支持
+
+- **仓库**: [GitHub - Claude-Code-Workflow](https://github.com/catlog22/Claude-Code-Workflow)
+- **问题**: 在 [GitHub Issues](https://github.com/catlog22/Claude-Code-Workflow/issues) 上报告错误或请求功能。
+- **讨论**: 加入 [社区论坛](https://github.com/catlog22/Claude-Code-Workflow/discussions)。
+
+## 📄 许可证
+
+此项目根据 **MIT 许可证** 授权。详见 [LICENSE](LICENSE) 文件。

install-remote.sh

@@ -0,0 +1,394 @@
+#!/usr/bin/env bash
+# Claude Code Workflow (CCW) - Remote Installation Script
+# One-liner remote installation for Claude Code Workflow system
+
+set -e  # Exit on error
+
+# Script metadata
+SCRIPT_NAME="Claude Code Workflow (CCW) Remote Installer"
+VERSION="2.1.1"
+BRANCH="${BRANCH:-main}"
+
+# Colors for output
+COLOR_RESET='\033[0m'
+COLOR_SUCCESS='\033[0;32m'
+COLOR_INFO='\033[0;36m'
+COLOR_WARNING='\033[0;33m'
+COLOR_ERROR='\033[0;31m'
+
+# Variables
+INSTALL_GLOBAL=false
+INSTALL_DIR=""
+FORCE=false
+NO_BACKUP=false
+NON_INTERACTIVE=false
+BACKUP_ALL=false
+
+# Functions
+function write_color() {
+    local message="$1"
+    local color="${2:-$COLOR_RESET}"
+    echo -e "${color}${message}${COLOR_RESET}"
+}
+
+function show_header() {
+    write_color "==== $SCRIPT_NAME v$VERSION ====" "$COLOR_INFO"
+    write_color "========================================================" "$COLOR_INFO"
+    echo ""
+}
+
+function test_prerequisites() {
+    # Test bash version
+    if [ "${BASH_VERSINFO[0]}" -lt 4 ]; then
+        write_color "ERROR: Bash 4.0 or higher is required" "$COLOR_ERROR"
+        write_color "Current version: ${BASH_VERSION}" "$COLOR_ERROR"
+        return 1
+    fi
+
+    # Test required commands
+    for cmd in curl unzip; do
+        if ! command -v "$cmd" &> /dev/null; then
+            write_color "ERROR: Required command '$cmd' not found" "$COLOR_ERROR"
+            write_color "Please install: $cmd" "$COLOR_ERROR"
+            return 1
+        fi
+    done
+
+    # Test internet connectivity
+    if curl -sSf --connect-timeout 10 "https://github.com" &> /dev/null; then
+        write_color "✓ Network connection OK" "$COLOR_SUCCESS"
+    else
+        write_color "ERROR: Cannot connect to GitHub" "$COLOR_ERROR"
+        write_color "Please check your network connection" "$COLOR_ERROR"
+        return 1
+    fi
+
+    return 0
+}
+
+function get_temp_directory() {
+    local temp_dir
+    temp_dir=$(mktemp -d -t claude-code-workflow-install.XXXXXX)
+    echo "$temp_dir"
+}
+
+function download_repository() {
+    local temp_dir="$1"
+    local branch="${2:-main}"
+    local repo_url="https://github.com/catlog22/Claude-Code-Workflow"
+    local zip_url="${repo_url}/archive/refs/heads/${branch}.zip"
+    local zip_path="${temp_dir}/repo.zip"
+
+    write_color "Downloading from GitHub..." "$COLOR_INFO" >&2
+    write_color "Source: $repo_url" "$COLOR_INFO" >&2
+    write_color "Branch: $branch" "$COLOR_INFO" >&2
+    write_color "URL: $zip_url" "$COLOR_INFO" >&2
+
+    # Download with curl
+    if curl -fsSL -o "$zip_path" "$zip_url" 2>&1 >&2; then
+        # Verify the download
+        if [ -f "$zip_path" ]; then
+            local file_size
+            file_size=$(du -h "$zip_path" 2>/dev/null | cut -f1)
+            write_color "✓ Download complete ($file_size)" "$COLOR_SUCCESS" >&2
+
+            # Output path to stdout for capture
+            echo "$zip_path"
+            return 0
+        else
+            write_color "ERROR: Downloaded file does not exist" "$COLOR_ERROR" >&2
+            return 1
+        fi
+    else
+        write_color "ERROR: Download failed" "$COLOR_ERROR" >&2
+        return 1
+    fi
+}
+
+function extract_repository() {
+    local zip_path="$1"
+    local temp_dir="$2"
+
+    write_color "Extracting files..." "$COLOR_INFO" >&2
+
+    # Verify zip file exists
+    if [ ! -f "$zip_path" ]; then
+        write_color "ERROR: ZIP file not found: $zip_path" "$COLOR_ERROR" >&2
+        return 1
+    fi
+
+    # Extract with unzip
+    if unzip -q "$zip_path" -d "$temp_dir" >&2 2>&1; then
+        # Find the extracted directory
+        local repo_dir
+        repo_dir=$(find "$temp_dir" -maxdepth 1 -type d -name "Claude-Code-Workflow-*" 2>/dev/null | head -n 1)
+
+        if [ -n "$repo_dir" ] && [ -d "$repo_dir" ]; then
+            write_color "✓ Extraction complete: $repo_dir" "$COLOR_SUCCESS" >&2
+            # Output path to stdout for capture
+            echo "$repo_dir"
+            return 0
+        else
+            write_color "ERROR: Could not find extracted repository directory" "$COLOR_ERROR" >&2
+            write_color "Temp directory contents:" "$COLOR_INFO" >&2
+            ls -la "$temp_dir" >&2
+            return 1
+        fi
+    else
+        write_color "ERROR: Extraction failed" "$COLOR_ERROR" >&2
+        return 1
+    fi
+}
+
+function invoke_local_installer() {
+    local repo_dir="$1"
+    local installer_path="${repo_dir}/Install-Claude.sh"
+
+    # Make installer executable
+    if [ -f "$installer_path" ]; then
+        chmod +x "$installer_path"
+    else
+        write_color "ERROR: Install-Claude.sh not found" "$COLOR_ERROR"
+        return 1
+    fi
+
+    write_color "Running local installer..." "$COLOR_INFO"
+    echo ""
+
+    # Build parameters for local installer
+    local params=()
+
+    if [ "$INSTALL_GLOBAL" = true ]; then
+        params+=("-InstallMode" "Global")
+    fi
+
+    if [ -n "$INSTALL_DIR" ]; then
+        params+=("-InstallMode" "Path" "-TargetPath" "$INSTALL_DIR")
+    fi
+
+    if [ "$FORCE" = true ]; then
+        params+=("-Force")
+    fi
+
+    if [ "$NO_BACKUP" = true ]; then
+        params+=("-NoBackup")
+    fi
+
+    if [ "$NON_INTERACTIVE" = true ]; then
+        params+=("-NonInteractive")
+    fi
+
+    if [ "$BACKUP_ALL" = true ]; then
+        params+=("-BackupAll")
+    fi
+
+    # Execute installer
+    if (cd "$repo_dir" && "$installer_path" "${params[@]}"); then
+        return 0
+    else
+        write_color "Installation script failed" "$COLOR_ERROR"
+        return 1
+    fi
+}
+
+function cleanup_temp_files() {
+    local temp_dir="$1"
+
+    if [ -d "$temp_dir" ]; then
+        if rm -rf "$temp_dir"; then
+            write_color "✓ Temporary files cleaned up" "$COLOR_INFO"
+        else
+            write_color "WARNING: Failed to clean temporary files" "$COLOR_WARNING"
+        fi
+    fi
+}
+
+function wait_for_user() {
+    local message="${1:-Press Enter to continue...}"
+
+    if [ "$NON_INTERACTIVE" != true ]; then
+        echo ""
+        write_color "$message" "$COLOR_INFO"
+        read -r
+        echo ""
+    fi
+}
+
+function parse_arguments() {
+    while [[ $# -gt 0 ]]; do
+        case "$1" in
+            --global)
+                INSTALL_GLOBAL=true
+                shift
+                ;;
+            --directory)
+                INSTALL_DIR="$2"
+                shift 2
+                ;;
+            --force)
+                FORCE=true
+                shift
+                ;;
+            --no-backup)
+                NO_BACKUP=true
+                shift
+                ;;
+            --non-interactive)
+                NON_INTERACTIVE=true
+                shift
+                ;;
+            --backup-all)
+                BACKUP_ALL=true
+                shift
+                ;;
+            --branch)
+                BRANCH="$2"
+                shift 2
+                ;;
+            --help)
+                show_help
+                exit 0
+                ;;
+            *)
+                write_color "Unknown option: $1" "$COLOR_ERROR"
+                show_help
+                exit 1
+                ;;
+        esac
+    done
+}
+
+function show_help() {
+    cat << EOF
+$SCRIPT_NAME v$VERSION
+
+Usage: $0 [OPTIONS]
+
+Options:
+    --global              Install to global user directory (~/.claude)
+    --directory DIR       Install to custom directory
+    --force               Force installation without prompts
+    --no-backup           Skip backup creation
+    --non-interactive     Non-interactive mode (no prompts)
+    --backup-all          Backup all files before installation
+    --branch BRANCH       Specify GitHub branch (default: main)
+    --help                Show this help message
+
+Examples:
+    # Interactive installation
+    $0
+
+    # Global installation without prompts
+    $0 --global --non-interactive
+
+    # Custom directory installation
+    $0 --directory /opt/claude-code-workflow
+
+EOF
+}
+
+function main() {
+    show_header
+
+    write_color "This will download and install Claude Code Workflow System from GitHub." "$COLOR_INFO"
+    echo ""
+
+    # Test prerequisites
+    write_color "Checking system requirements..." "$COLOR_INFO"
+    if ! test_prerequisites; then
+        wait_for_user "System check failed! Press Enter to exit..."
+        exit 1
+    fi
+
+    # Confirm installation
+    if [ "$NON_INTERACTIVE" != true ] && [ "$FORCE" != true ]; then
+        echo ""
+        write_color "SECURITY NOTE:" "$COLOR_WARNING"
+        echo "- This script will download and execute Claude Code Workflow from GitHub"
+        echo "- Repository: https://github.com/catlog22/Claude-Code-Workflow"
+        echo "- Branch: $BRANCH (latest stable version)"
+        echo "- Features: Intelligent workflow orchestration with multi-agent coordination"
+        echo "- Please ensure you trust this source"
+        echo ""
+
+        read -p "Continue with installation? (y/N) " -r choice
+        if [[ ! $choice =~ ^[Yy]$ ]]; then
+            write_color "Installation cancelled" "$COLOR_WARNING"
+            exit 0
+        fi
+    fi
+
+    # Create temp directory
+    local temp_dir
+    temp_dir=$(get_temp_directory)
+    write_color "Temporary directory: $temp_dir" "$COLOR_INFO"
+
+    local success=false
+
+    # Download repository
+    local zip_path
+    write_color "Starting download process..." "$COLOR_INFO"
+    zip_path=$(download_repository "$temp_dir" "$BRANCH")
+    local download_status=$?
+
+    if [ $download_status -eq 0 ] && [ -n "$zip_path" ] && [ -f "$zip_path" ]; then
+        write_color "Download successful: $zip_path" "$COLOR_SUCCESS"
+
+        # Extract repository
+        local repo_dir
+        write_color "Starting extraction process..." "$COLOR_INFO"
+        repo_dir=$(extract_repository "$zip_path" "$temp_dir")
+        local extract_status=$?
+
+        if [ $extract_status -eq 0 ] && [ -n "$repo_dir" ] && [ -d "$repo_dir" ]; then
+            write_color "Extraction successful: $repo_dir" "$COLOR_SUCCESS"
+
+            # Run local installer
+            if invoke_local_installer "$repo_dir"; then
+                success=true
+                echo ""
+                write_color "✓ Remote installation completed successfully!" "$COLOR_SUCCESS"
+            else
+                write_color "ERROR: Installation script failed" "$COLOR_ERROR"
+            fi
+        else
+            write_color "ERROR: Extraction failed (status: $extract_status)" "$COLOR_ERROR"
+            if [ ! -f "$zip_path" ]; then
+                write_color "ZIP file does not exist: $zip_path" "$COLOR_ERROR"
+            elif [ ! -s "$zip_path" ]; then
+                write_color "ZIP file is empty: $zip_path" "$COLOR_ERROR"
+            fi
+        fi
+    else
+        write_color "ERROR: Download failed (status: $download_status)" "$COLOR_ERROR"
+        if [ -z "$zip_path" ]; then
+            write_color "Download did not return a file path" "$COLOR_ERROR"
+        elif [ ! -f "$zip_path" ]; then
+            write_color "Downloaded file does not exist: $zip_path" "$COLOR_ERROR"
+        fi
+    fi
+
+    # Cleanup
+    cleanup_temp_files "$temp_dir"
+
+    if [ "$success" = true ]; then
+        echo ""
+        write_color "Next steps:" "$COLOR_INFO"
+        echo "1. Review CLAUDE.md for project-specific guidelines"
+        echo "2. Try /workflow commands for Agent coordination"
+        echo "3. Use /update-memory to manage distributed documentation"
+
+        wait_for_user "Remote installation done! Press Enter to exit..."
+        exit 0
+    else
+        echo ""
+        wait_for_user "Installation failed! Press Enter to exit..."
+        exit 1
+    fi
+}
+
+# Parse command line arguments
+parse_arguments "$@"
+
+# Run main function
+main