mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-09 02:24:11 +08:00
fix: Correct TodoWrite Template in workflow execute command
- Replace markdown template with Claude Code TodoWrite tool usage - Update documentation to use built-in TodoWrite API instead of manual TODO_LIST.md updates - Align with JSON-only data model and real-time progress tracking principles - Add proper TodoWrite integration rules and examples 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
@@ -1,169 +0,0 @@
|
||||
# Brainstorming Framework
|
||||
|
||||
## Overview
|
||||
Common creative techniques, execution modes, and quality standards for all brainstorming sessions.
|
||||
|
||||
## Creative Techniques
|
||||
|
||||
### 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
|
||||
- **Brainstorming**: Free-flowing idea generation
|
||||
- **Brainwriting**: Silent idea generation and building
|
||||
- **Random Word**: Stimulus-based creative thinking
|
||||
- **What If**: Scenario-based exploration
|
||||
- **Assumption Challenging**: Question fundamental assumptions
|
||||
|
||||
## Execution Modes
|
||||
|
||||
### Creative Mode (Default)
|
||||
- **Techniques**: SCAMPER, Six Thinking Hats, wild ideas
|
||||
- **Focus**: Innovation and unconventional solutions
|
||||
- **Approach**:
|
||||
- Emphasize divergent thinking and wild ideas
|
||||
- Apply creative techniques extensively
|
||||
- Encourage "what if" thinking and assumption challenging
|
||||
- Focus on novel and unconventional solutions
|
||||
|
||||
### Analytical Mode
|
||||
- **Techniques**: Root cause analysis, data-driven insights
|
||||
- **Focus**: Evidence-based systematic problem-solving
|
||||
- **Approach**:
|
||||
- Use structured analysis frameworks
|
||||
- Apply root cause analysis and logical thinking
|
||||
- Emphasize evidence-based reasoning
|
||||
- Focus on systematic problem-solving
|
||||
|
||||
### Strategic Mode
|
||||
- **Techniques**: Systems thinking, scenario planning
|
||||
- **Focus**: Long-term strategic positioning
|
||||
- **Approach**:
|
||||
- Apply strategic thinking frameworks
|
||||
- Use systems thinking and long-term perspective
|
||||
- Consider competitive dynamics and market forces
|
||||
- Focus on strategic positioning and advantage
|
||||
|
||||
## Brainstorming Session Protocol
|
||||
|
||||
### Input Processing
|
||||
```
|
||||
Topic: [Challenge or opportunity description]
|
||||
Mode: [creative|analytical|strategic]
|
||||
Perspectives: [Selected role perspectives]
|
||||
Context: [Current situation and constraints]
|
||||
```
|
||||
|
||||
### Execution Flow
|
||||
```
|
||||
1. Challenge Analysis → Define scope, constraints, success criteria
|
||||
2. Perspective Setup → Establish role contexts and viewpoints
|
||||
3. Ideation Phase → Generate ideas using appropriate techniques
|
||||
4. Convergence Phase → Evaluate, synthesize, prioritize solutions
|
||||
5. Documentation → Create structured session records
|
||||
```
|
||||
|
||||
## 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
|
||||
|
||||
## 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
|
||||
|
||||
## Integration Guidelines
|
||||
|
||||
### With Brainstorming Principles
|
||||
This framework works in conjunction with @~/.claude/workflows/brainstorming-principles.md which defines:
|
||||
- Project structure establishment
|
||||
- Session initialization requirements
|
||||
- Directory creation protocols
|
||||
- Agent coordination standards
|
||||
|
||||
### With Role Commands
|
||||
Each role-specific brainstorm command implements this framework within their domain context:
|
||||
- Applies appropriate techniques for their perspective
|
||||
- Uses mode selection based on problem type
|
||||
- Follows documentation standards
|
||||
- Maintains quality criteria
|
||||
|
||||
---
|
||||
|
||||
This framework provides the common foundation for all brainstorming activities while allowing role-specific customization and focus.
|
||||
@@ -3,177 +3,80 @@
|
||||
## Core Philosophy
|
||||
**"Diverge first, then converge"** - Generate multiple solutions from diverse perspectives, then synthesize and prioritize.
|
||||
|
||||
## Project Structure Establishment (MANDATORY FIRST STEP)
|
||||
## Creative Techniques Reference
|
||||
|
||||
### Automatic Directory Creation
|
||||
Before ANY agent coordination begins, the brainstorming command MUST establish the complete project structure:
|
||||
### 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?
|
||||
|
||||
1. **Create Session Directory**:
|
||||
```bash
|
||||
mkdir -p .workflow/WFS-[topic-slug]/.brainstorming/
|
||||
```
|
||||
### 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
|
||||
|
||||
2. **Create Agent Output Directories**:
|
||||
```bash
|
||||
# Create directories ONLY for selected participating agent roles
|
||||
mkdir -p .workflow/WFS-[topic-slug]/.brainstorming/{selected-agent1,selected-agent2,selected-agent3}
|
||||
# Example: mkdir -p .workflow/WFS-user-auth/.brainstorming/{system-architect,ui-designer,product-manager}
|
||||
```
|
||||
### 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
|
||||
|
||||
3. **Initialize Session State**:
|
||||
- Create workflow-session.json with brainstorming phase tracking
|
||||
- Set up document reference structure
|
||||
- Establish agent coordination metadata
|
||||
|
||||
### Pre-Agent Verification
|
||||
Before delegating to @conceptual-planning-agent, VERIFY:
|
||||
- [ ] Topic slug generated correctly
|
||||
- [ ] All required directories exist
|
||||
- [ ] workflow-session.json initialized
|
||||
- [ ] Agent roles selected and corresponding directories created
|
||||
|
||||
## Brainstorming Modes
|
||||
## Analysis Modes
|
||||
|
||||
### Creative Mode (Default)
|
||||
- **Techniques**: SCAMPER, Six Thinking Hats, wild ideas
|
||||
- **Focus**: Innovation and unconventional solutions
|
||||
- **Approach**: Emphasize divergent thinking, "what if" scenarios, assumption challenging
|
||||
|
||||
### Analytical Mode
|
||||
- **Techniques**: Root cause analysis, data-driven insights
|
||||
### Analytical Mode
|
||||
- **Focus**: Evidence-based systematic problem-solving
|
||||
- **Approach**: Structured analysis, root cause analysis, logical reasoning
|
||||
|
||||
### Strategic Mode
|
||||
- **Techniques**: Systems thinking, scenario planning
|
||||
- **Focus**: Long-term strategic positioning
|
||||
- **Approach**: Systems thinking, competitive dynamics, market forces
|
||||
|
||||
## Documentation Structure
|
||||
|
||||
### Workflow Integration
|
||||
Brainstorming sessions are integrated with the unified workflow system under `.workflow/WFS-[topic-slug]/.brainstorming/`.
|
||||
|
||||
**Directory Creation**: If `.workflow/WFS-[topic-slug]/` doesn't exist, create it automatically before starting brainstorming.
|
||||
|
||||
**Topic Slug Format**: Convert topic to lowercase with hyphens (e.g., "User Authentication System" → `WFS-user-authentication-system`)
|
||||
## Documentation Standards
|
||||
|
||||
### Session Output Format
|
||||
```
|
||||
.workflow/WFS-[topic-slug]/
|
||||
└── .brainstorming/
|
||||
├── session-summary.md # Main session documentation
|
||||
├── synthesis-analysis.md # Cross-role integration
|
||||
├── recommendations.md # Prioritized solutions
|
||||
├── system-architect/ # Architecture perspective
|
||||
│ ├── analysis.md
|
||||
│ └── technical-specifications.md
|
||||
├── ui-designer/ # Design perspective
|
||||
│ ├── analysis.md
|
||||
│ └── user-experience-plan.md
|
||||
├── product-manager/ # Product perspective
|
||||
│ ├── analysis.md
|
||||
│ └── business-requirements.md
|
||||
├── data-architect/ # Data perspective
|
||||
│ ├── analysis.md
|
||||
│ └── data-model-design.md
|
||||
├── test-strategist/ # Testing perspective
|
||||
│ ├── analysis.md
|
||||
│ └── test-strategy-plan.md
|
||||
├── security-expert/ # Security perspective
|
||||
│ ├── analysis.md
|
||||
│ └── security-assessment.md
|
||||
├── user-researcher/ # User research perspective
|
||||
│ ├── analysis.md
|
||||
│ └── user-insights.md
|
||||
├── business-analyst/ # Business analysis perspective
|
||||
│ ├── analysis.md
|
||||
│ └── process-optimization.md
|
||||
├── innovation-lead/ # Innovation perspective
|
||||
│ ├── analysis.md
|
||||
│ └── future-roadmap.md
|
||||
└── feature-planner/ # Feature planning perspective
|
||||
├── analysis.md
|
||||
└── feature-specifications.md
|
||||
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
|
||||
```
|
||||
|
||||
## Session Metadata
|
||||
Each brainstorming session maintains metadata in `session-summary.md` header:
|
||||
|
||||
```markdown
|
||||
# Brainstorming Session: [Topic]
|
||||
|
||||
**Session ID**: WFS-[topic-slug]
|
||||
**Topic**: [Challenge description]
|
||||
**Mode**: creative|analytical|strategic
|
||||
**Perspectives**: [role1, role2, role3...]
|
||||
**Facilitator**: @conceptual-planning-agent
|
||||
**Date**: YYYY-MM-DD
|
||||
|
||||
## Session Overview
|
||||
[Brief session description and objectives]
|
||||
```
|
||||
### 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
|
||||
- **Diverse Perspectives**: Include multiple role viewpoints
|
||||
- **Actionable Outputs**: Generate concrete next steps
|
||||
- **Comprehensive Documentation**: Capture all insights and recommendations
|
||||
- **Inclusive Participation**: Ensure all perspectives are valued
|
||||
- **Creative Environment**: Maintain judgment-free ideation atmosphere
|
||||
- **Actionable Outcomes**: Generate concrete next steps
|
||||
|
||||
## Unified Workflow Integration
|
||||
### 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
|
||||
|
||||
### Document-State Separation
|
||||
Following unified workflow system principles:
|
||||
- **Markdown Files** → Brainstorming insights, role analyses, synthesis results
|
||||
- **JSON Files** → Session state, role completion tracking, workflow coordination
|
||||
- **Auto-sync** → Integration with `workflow-session.json` for seamless workflow transition
|
||||
---
|
||||
|
||||
### Session Coordination
|
||||
Brainstorming sessions integrate with the unified workflow system:
|
||||
|
||||
```json
|
||||
// workflow-session.json integration
|
||||
{
|
||||
"session_id": "WFS-[topic-slug]",
|
||||
"type": "complex", // brainstorming typically creates complex workflows
|
||||
"current_phase": "PLAN", // conceptual phase
|
||||
"brainstorming": {
|
||||
"status": "active|completed",
|
||||
"mode": "creative|analytical|strategic",
|
||||
"roles_completed": ["system-architect", "ui-designer"],
|
||||
"current_role": "data-architect",
|
||||
"output_directory": ".workflow/WFS-[topic-slug]/.brainstorming/",
|
||||
"agent_document_paths": {
|
||||
"system-architect": ".workflow/WFS-[topic-slug]/.brainstorming/system-architect/",
|
||||
"ui-designer": ".workflow/WFS-[topic-slug]/.brainstorming/ui-designer/",
|
||||
"product-manager": ".workflow/WFS-[topic-slug]/.brainstorming/product-manager/",
|
||||
"data-architect": ".workflow/WFS-[topic-slug]/.brainstorming/data-architect/"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Directory Auto-Creation
|
||||
Before starting brainstorming session:
|
||||
```bash
|
||||
# Create workflow structure and ONLY selected agent directories
|
||||
mkdir -p .workflow/WFS-[topic-slug]/.brainstorming/
|
||||
# Create directories for selected agents only
|
||||
for agent in selected_agents; do
|
||||
mkdir -p .workflow/WFS-[topic-slug]/.brainstorming/$agent
|
||||
done
|
||||
```
|
||||
|
||||
### Agent Document Assignment Protocol
|
||||
When coordinating with @conceptual-planning-agent, ALWAYS specify exact output location:
|
||||
|
||||
**Correct Agent Delegation:**
|
||||
```
|
||||
Task(conceptual-planning-agent): "Conduct brainstorming analysis for: [topic]. Use [mode] approach. Required perspective: [role].
|
||||
|
||||
Load role definition using: ~/.claude/scripts/plan-executor.sh [role]
|
||||
|
||||
OUTPUT REQUIREMENT: Save all generated documents to: .workflow/WFS-[topic-slug]/.brainstorming/[role]/
|
||||
- analysis.md (main perspective analysis)
|
||||
- [role-specific-output].md (specialized deliverable)
|
||||
"
|
||||
```
|
||||
|
||||
### Brainstorming Output
|
||||
The brainstorming phase produces comprehensive role-based analysis documents that serve as input for subsequent workflow phases.
|
||||
This framework provides the conceptual foundation for brainstorming activities. Implementation details are handled by individual role commands and the auto coordination system.
|
||||
Reference in New Issue
Block a user