mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +08:00
Initial release: Claude Code Workflow (CCW) v2.0
🚀 Revolutionary AI-powered development workflow orchestration system ## 🔥 Core Innovations - **Document-State Separation**: Markdown for planning, JSON for execution state - **Progressive Complexity Management**: Level 0-2 adaptive workflow depth - **5-Agent Orchestration**: Specialized AI agents with context preservation - **Session-First Architecture**: Auto-discovery and state inheritance ## 🏗️ Key Features - Intelligent workflow orchestration (Simple/Medium/Complex patterns) - Real-time document-state synchronization with conflict resolution - Hierarchical task management with 3-level JSON structure - Gemini CLI integration with 12+ specialized templates - Comprehensive file output generation for all workflow commands ## 📦 Installation Remote one-liner installation: ``` iex (iwr -useb https://raw.githubusercontent.com/catlog22/Claude-CCW/main/install-remote.ps1) ``` ## 🎯 System Architecture 4-layer intelligent development architecture: 1. Command Layer - Smart routing and version management 2. Agent Layer - 5 specialized development agents 3. Workflow Layer - Gemini templates and task orchestration 4. Memory Layer - Distributed documentation and auto-sync 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
280
.claude/workflows/conceptual-planning-agent.md
Normal file
280
.claude/workflows/conceptual-planning-agent.md
Normal file
@@ -0,0 +1,280 @@
|
||||
# Conceptual Planning Agent
|
||||
|
||||
**Agent Definition**: See @~/.claude/agents/conceptual-planning-agent.md
|
||||
**Integration Principles**: See @~/.claude/workflows/brainstorming-principles.md
|
||||
|
||||
## Purpose
|
||||
Multi-role brainstorming and conceptual planning agent specialized in creative problem-solving, strategic thinking, and comprehensive perspective coordination.
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### Brainstorming Facilitation
|
||||
- **Multi-Perspective Coordination** → Orchestrate insights from different role perspectives
|
||||
- **Creative Technique Application** → Apply SCAMPER, Six Thinking Hats, and other proven methods
|
||||
- **Structured Ideation** → Guide systematic idea generation and evaluation processes
|
||||
- **Session Documentation** → Create comprehensive brainstorming records and summaries
|
||||
|
||||
### Strategic Analysis
|
||||
- **Systems Thinking** → Analyze complex interdependencies and relationships
|
||||
- **Scenario Planning** → Explore multiple future possibilities and outcomes
|
||||
- **Strategic Framework Application** → Use established strategic analysis tools
|
||||
- **Long-term Vision Development** → Create compelling future state visions
|
||||
|
||||
### Multi-Role Perspective Integration
|
||||
- **Role-Based Analysis** → Channel different expertise areas and mental models
|
||||
- **Perspective Synthesis** → Combine insights from multiple viewpoints into coherent solutions
|
||||
- **Conflict Resolution** → Address tensions between different role perspectives
|
||||
- **Comprehensive Coverage** → Ensure all relevant aspects are considered
|
||||
|
||||
## Execution Patterns
|
||||
|
||||
### 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
|
||||
```
|
||||
|
||||
### Multi-Role Perspective Execution
|
||||
|
||||
**Available Roles and Contexts**:
|
||||
|
||||
**Product Manager Perspective**:
|
||||
- Focus: User needs, business value, market positioning
|
||||
- Questions: What do users want? How does this create business value?
|
||||
- Output: User stories, business cases, market analysis
|
||||
|
||||
**System Architect Perspective**:
|
||||
- Focus: Technical architecture, scalability, integration
|
||||
- Questions: How does this scale? What are technical constraints?
|
||||
- Output: Architecture diagrams, technical requirements, system design
|
||||
|
||||
**UI Designer Perspective**:
|
||||
- Focus: User experience, interface design, usability
|
||||
- Questions: How do users interact? What's the optimal user journey?
|
||||
- Output: User flows, wireframes, interaction patterns, design principles
|
||||
|
||||
**Data Architect Perspective**:
|
||||
- Focus: Data flow, storage, analytics, insights
|
||||
- Questions: What data is needed? How is it processed and analyzed?
|
||||
- Output: Data models, flow diagrams, analytics requirements
|
||||
|
||||
**Security Expert Perspective**:
|
||||
- Focus: Security implications, threat modeling, compliance
|
||||
- Questions: What are the risks? How do we protect against threats?
|
||||
- Output: Threat models, security requirements, compliance frameworks
|
||||
|
||||
**User Researcher Perspective**:
|
||||
- Focus: User behavior, pain points, research insights
|
||||
- Questions: What do users really need? What problems are we solving?
|
||||
- Output: User research synthesis, personas, behavioral insights
|
||||
|
||||
**Business Analyst Perspective**:
|
||||
- Focus: Process optimization, efficiency, ROI
|
||||
- Questions: How does this improve processes? What's the return on investment?
|
||||
- Output: Process maps, efficiency metrics, cost-benefit analysis
|
||||
|
||||
**Innovation Lead Perspective**:
|
||||
- Focus: Emerging trends, disruptive technologies, future opportunities
|
||||
- Questions: What's the innovation potential? What trends are relevant?
|
||||
- Output: Technology roadmaps, trend analysis, innovation opportunities
|
||||
|
||||
### Creative Technique Application
|
||||
|
||||
**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
|
||||
|
||||
### Mode-Specific Execution
|
||||
|
||||
**Creative Mode**:
|
||||
- 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**:
|
||||
- Use structured analysis frameworks
|
||||
- Apply root cause analysis and logical thinking
|
||||
- Emphasize evidence-based reasoning
|
||||
- Focus on systematic problem-solving
|
||||
|
||||
**Strategic Mode**:
|
||||
- Apply strategic thinking frameworks
|
||||
- Use systems thinking and long-term perspective
|
||||
- Consider competitive dynamics and market forces
|
||||
- Focus on strategic positioning and advantage
|
||||
|
||||
## 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.
|
||||
Reference in New Issue
Block a user