mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +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
217
.claude/commands/workflow/brainstorm/auto.md
Normal file
217
.claude/commands/workflow/brainstorm/auto.md
Normal file
@@ -0,0 +1,217 @@
|
||||
---
|
||||
name: auto
|
||||
description: Intelligent brainstorming automation with dynamic role selection and guided context gathering
|
||||
usage: /workflow:brainstorm:auto "<topic>"
|
||||
argument-hint: "topic or challenge description"
|
||||
examples:
|
||||
- /workflow:brainstorm:auto "Build real-time collaboration feature"
|
||||
- /workflow:brainstorm:auto "Optimize database performance for millions of users"
|
||||
- /workflow:brainstorm:auto "Implement secure authentication system"
|
||||
allowed-tools: Task(*), TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*)
|
||||
---
|
||||
|
||||
# Workflow Brainstorm Auto Command
|
||||
|
||||
## Usage
|
||||
```bash
|
||||
/workflow:brainstorm:auto "<topic>"
|
||||
```
|
||||
|
||||
## 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
|
||||
- **Business & Process**: `business|process|workflow|cost|innovation|testing` → business-analyst, innovation-lead, test-strategist
|
||||
- **Multi-role**: Complex topics automatically select 2-3 complementary roles
|
||||
- **Default**: `product-manager` if no clear match
|
||||
|
||||
**Template Loading**: `~/.claude/scripts/planning-role-load.sh load <role-name>`
|
||||
**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
|
||||
|
||||
**Example**:
|
||||
```bash
|
||||
~/.claude/scripts/planning-role-load.sh load system-architect
|
||||
~/.claude/scripts/planning-role-load.sh load ui-designer
|
||||
~/.claude/scripts/planning-role-load.sh list # Show all available roles
|
||||
```
|
||||
|
||||
## Core Workflow
|
||||
|
||||
### Analysis & Planning Process
|
||||
The command performs dedicated role analysis through:
|
||||
|
||||
**0. Session Management** ⚠️ FIRST STEP
|
||||
- **Active session detection**: Check `.workflow/.active-*` markers
|
||||
- **Session selection**: Prompt user if multiple active sessions found
|
||||
- **Auto-creation**: Create `WFS-[topic-slug]` only if no active session exists
|
||||
- **Context isolation**: Each session maintains independent brainstorming state
|
||||
|
||||
**1. Role Selection & Template Loading**
|
||||
- **Keyword analysis**: Extract topic keywords and map to planning roles
|
||||
- **Template loading**: Load role templates via `~/.claude/scripts/planning-role-load.sh`
|
||||
- **Role validation**: Verify against `.claude/workflows/cli-templates/planning-roles/`
|
||||
- **Multi-role detection**: Select 1-3 complementary roles based on topic complexity
|
||||
|
||||
**2. Sequential Role Processing** ⚠️ CRITICAL ARCHITECTURE
|
||||
- **One Role = One Agent**: Each role gets dedicated conceptual-planning-agent
|
||||
- **Context gathering**: Role-specific questioning with validation
|
||||
- **Agent submission**: Complete context handoff to single-role agents
|
||||
- **Progress tracking**: Real-time TodoWrite updates per role
|
||||
|
||||
**3. Analysis Artifacts Generated**
|
||||
- **Role contexts**: `.brainstorming/[role]-context.md` - User responses per role
|
||||
- **Agent outputs**: `.brainstorming/[role]/analysis.md` - Dedicated role analysis
|
||||
- **Session metadata**: `.brainstorming/auto-session.json` - Agent assignments and validation
|
||||
- **Synthesis**: `.brainstorming/synthesis/integrated-analysis.md` - Multi-role integration
|
||||
|
||||
## Implementation Standards
|
||||
|
||||
### Dedicated Agent Architecture ⚠️ CRITICAL
|
||||
Agents receive dedicated role assignments with complete context isolation:
|
||||
|
||||
```json
|
||||
"agent_assignment": {
|
||||
"role": "system-architect",
|
||||
"agent_id": "conceptual-planning-agent-system-architect",
|
||||
"context_source": ".brainstorming/system-architect-context.md",
|
||||
"output_location": ".brainstorming/system-architect/",
|
||||
"flow_control": {
|
||||
"pre_analysis": [
|
||||
{
|
||||
"step": "load_role_template",
|
||||
"action": "Load system-architect planning template",
|
||||
"command": "bash(~/.claude/scripts/planning-role-load.sh load system-architect)",
|
||||
"output_to": "role_template"
|
||||
}
|
||||
],
|
||||
"implementation_approach": {
|
||||
"task_description": "Execute dedicated system-architect conceptual analysis for: [topic]",
|
||||
"role_focus": "system-architect",
|
||||
"user_context": "Direct user responses from context gathering phase",
|
||||
"deliverables": "conceptual_analysis, strategic_recommendations, role_perspective"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Context Accumulation & Role Isolation**:
|
||||
1. **Role template loading**: Planning role template with domain expertise via CLI
|
||||
2. **Context validation**: Minimum response requirements with re-prompting
|
||||
3. **Conceptual analysis**: Role-specific perspective on topic without implementation details
|
||||
4. **Agent delegation**: Complete context handoff to dedicated conceptual-planning-agent
|
||||
|
||||
**Content Sources**:
|
||||
- Role templates: `~/.claude/scripts/planning-role-load.sh load <role>` from `.claude/workflows/cli-templates/planning-roles/`
|
||||
- User responses: Direct context gathering during interactive questioning phase
|
||||
- Conceptual focus: Strategic and planning perspective without technical implementation
|
||||
|
||||
**Trigger Conditions**: Topic analysis matches role domains, user provides adequate context responses, role template successfully loaded
|
||||
|
||||
### Role Processing Standards
|
||||
|
||||
**Core Principles**:
|
||||
1. **Sequential Processing** - Complete each role fully before proceeding to next
|
||||
2. **Context Validation** - Ensure adequate detail before agent submission
|
||||
3. **Dedicated Assignment** - One conceptual-planning-agent per role
|
||||
4. **Progress Tracking** - Real-time TodoWrite updates for role processing stages
|
||||
|
||||
**Implementation Rules**:
|
||||
- **Maximum 3 roles**: Auto-selected based on topic complexity and domain overlap
|
||||
- **Context validation**: Minimum response length and completeness checks
|
||||
- **Agent isolation**: Each agent receives only role-specific context
|
||||
- **Error recovery**: Role-specific validation and retry logic
|
||||
|
||||
**Role Question Templates**:
|
||||
- **system-architect**: Scale requirements, integration needs, technology constraints, non-functional requirements
|
||||
- **security-expert**: Sensitive data types, compliance requirements, threat concerns, auth/authz needs
|
||||
- **ui-designer**: User personas, platform support, design guidelines, accessibility requirements
|
||||
- **product-manager**: Business objectives, stakeholders, success metrics, timeline constraints
|
||||
- **data-architect**: Data types, volume projections, compliance needs, analytics requirements
|
||||
|
||||
### Session Management ⚠️ CRITICAL
|
||||
- **⚡ FIRST ACTION**: Check for all `.workflow/.active-*` markers before role processing
|
||||
- **Multiple sessions support**: Different Claude instances can have different active brainstorming sessions
|
||||
- **User selection**: If multiple active sessions found, prompt user to select which one to work with
|
||||
- **Auto-session creation**: `WFS-[topic-slug]` only if no active session exists
|
||||
- **Session continuity**: MUST use selected active session for all role processing
|
||||
- **Context preservation**: Each role's context and agent output stored in session directory
|
||||
- **Session isolation**: Each session maintains independent brainstorming state and role assignments
|
||||
|
||||
## Document Generation
|
||||
|
||||
**Workflow**: Role Selection → Context Gathering → Agent Delegation → Documentation → Synthesis
|
||||
|
||||
**Always Created**:
|
||||
- **auto-session.json**: Agent assignments, context validation, completion tracking
|
||||
- **[role]-context.md**: User responses per role with question-answer pairs
|
||||
|
||||
**Auto-Created (per role)**:
|
||||
- **[role]/analysis.md**: Main role analysis from dedicated agent
|
||||
- **[role]/recommendations.md**: Role-specific recommendations
|
||||
- **[role]-template.md**: Loaded role planning template
|
||||
|
||||
**Auto-Created (multi-role)**:
|
||||
- **synthesis/integrated-analysis.md**: Cross-role integration and consensus analysis
|
||||
- **synthesis/consensus-matrix.md**: Agreement/disagreement analysis
|
||||
- **synthesis/priority-recommendations.md**: Prioritized action items
|
||||
|
||||
**Document Structure**:
|
||||
```
|
||||
.workflow/WFS-[topic]/.brainstorming/
|
||||
├── auto-session.json # Session metadata and agent tracking
|
||||
├── system-architect-context.md # User responses for system-architect
|
||||
├── system-architect-template.md# Loaded role template
|
||||
├── system-architect/ # Dedicated agent outputs
|
||||
│ ├── analysis.md
|
||||
│ ├── recommendations.md
|
||||
│ └── deliverables/
|
||||
├── ui-designer-context.md # User responses for ui-designer
|
||||
├── ui-designer/ # Dedicated agent outputs
|
||||
│ └── analysis.md
|
||||
└── synthesis/ # Multi-role integration
|
||||
├── integrated-analysis.md
|
||||
├── consensus-matrix.md
|
||||
└── priority-recommendations.md
|
||||
```
|
||||
|
||||
## Reference Information
|
||||
|
||||
### Role Processing Schema (Sequential Architecture)
|
||||
Each role processing follows dedicated agent pattern:
|
||||
- **role**: Selected planning role name
|
||||
- **template**: Loaded from cli-templates/planning-roles/
|
||||
- **context**: User responses with validation
|
||||
- **agent**: Dedicated conceptual-planning-agent instance
|
||||
- **output**: Role-specific analysis directory
|
||||
|
||||
### File Structure Reference
|
||||
**Architecture**: @~/.claude/workflows/workflow-architecture.md
|
||||
**Role Templates**: @~/.claude/workflows/cli-templates/planning-roles/
|
||||
|
||||
### Execution Integration
|
||||
Documents created for synthesis and action planning:
|
||||
- **auto-session.json**: Agent tracking and session metadata
|
||||
- **[role]-context.md**: Context loading for role analysis
|
||||
- **[role]/analysis.md**: Role-specific analysis outputs
|
||||
- **synthesis/**: Multi-role integration for comprehensive planning
|
||||
|
||||
## Error Handling
|
||||
- **Role selection failure**: Default to `product-manager` with explanation
|
||||
- **Context validation failure**: Re-prompt with minimum requirements
|
||||
- **Agent execution failure**: Role-specific retry with corrected context
|
||||
- **Template loading issues**: Graceful degradation with fallback questions
|
||||
- **Multi-role conflicts**: Synthesis agent handles disagreement resolution
|
||||
|
||||
## Quality Standards
|
||||
|
||||
### Dedicated Agent Excellence
|
||||
- **Single role focus**: Each agent handles exactly one role - no multi-role assignments
|
||||
- **Complete context**: Each agent receives comprehensive role-specific context
|
||||
- **Sequential processing**: Roles processed one at a time with full validation
|
||||
- **Dedicated output**: Each agent produces role-specific analysis and deliverables
|
||||
|
||||
### Context Collection Excellence
|
||||
- **Role-specific questioning**: Targeted questions for each role's domain expertise
|
||||
- **Context validation**: Verification before agent submission to ensure completeness
|
||||
- **User guidance**: Clear explanations of role perspective and question importance
|
||||
- **Response quality**: Minimum response requirements with re-prompting for insufficient detail
|
||||
@@ -36,7 +36,6 @@ Business process expert responsible for analyzing workflows, identifying require
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
@@ -60,110 +59,103 @@ Business process expert responsible for analyzing workflows, identifying require
|
||||
- What training and adaptation requirements exist?
|
||||
- What success metrics and monitoring mechanisms are needed?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
```bash
|
||||
# Create business analyst analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/business-analyst/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**Business Analyst Perspective Questioning**
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize business analyst perspective analysis tracking:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize business analyst brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze current business processes and workflows", "status": "in_progress", "activeForm": "Analyzing business processes"},
|
||||
{"content": "Identify business requirements and stakeholder needs", "status": "pending", "activeForm": "Identifying requirements"},
|
||||
{"content": "Evaluate cost-benefit and ROI analysis", "status": "pending", "activeForm": "Evaluating cost-benefit"},
|
||||
{"content": "Design process improvements and optimizations", "status": "pending", "activeForm": "Designing improvements"},
|
||||
{"content": "Plan change management and implementation", "status": "pending", "activeForm": "Planning change management"},
|
||||
{"content": "Generate comprehensive business analysis documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
]
|
||||
```
|
||||
Before agent assignment, gather comprehensive business analyst context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
|
||||
**1. Business Process Analysis**
|
||||
- What are the current business processes and workflows that need analysis?
|
||||
- Which departments, teams, or stakeholders are involved in these processes?
|
||||
- What are the key bottlenecks, inefficiencies, or pain points you've observed?
|
||||
- What metrics or KPIs are currently used to measure process performance?
|
||||
|
||||
**2. Cost and Resource Analysis**
|
||||
- What are the current costs associated with these processes (time, money, resources)?
|
||||
- How much time do stakeholders spend on these activities daily/weekly?
|
||||
- What technology, tools, or systems are currently being used?
|
||||
- What budget constraints or financial targets need to be considered?
|
||||
|
||||
**3. Business Requirements and Objectives**
|
||||
- What are the primary business objectives this analysis should achieve?
|
||||
- Who are the key stakeholders and what are their specific needs?
|
||||
- What are the success criteria and how will you measure improvement?
|
||||
- Are there any compliance, regulatory, or governance requirements?
|
||||
|
||||
**4. Change Management and Implementation**
|
||||
- How ready is the organization for process changes?
|
||||
- What training or change management support might be needed?
|
||||
- What timeline or deadlines are we working with?
|
||||
- What potential resistance or challenges do you anticipate?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/business-analyst-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
### Phase 4: Conceptual Planning Agent Coordination
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute dedicated business analyst conceptual analysis for: {topic}
|
||||
|
||||
ASSIGNED_ROLE: business-analyst
|
||||
GEMINI_ANALYSIS_REQUIRED: true
|
||||
ANALYSIS_DIMENSIONS:
|
||||
- process_optimization
|
||||
- cost_analysis
|
||||
- efficiency_metrics
|
||||
- workflow_patterns
|
||||
OUTPUT_LOCATION: .brainstorming/business-analyst/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
Conduct business analyst perspective brainstorming for: {topic}
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load business-analyst planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load business-analyst)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
ROLE CONTEXT: Business Analyst
|
||||
- Focus Areas: Process optimization, requirements analysis, cost-benefit analysis, change management
|
||||
- Analysis Framework: Business-centric approach with emphasis on efficiency and value creation
|
||||
- Success Metrics: Process efficiency, cost reduction, stakeholder satisfaction, ROI achievement
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply business analyst perspective to topic analysis
|
||||
- Focus on process optimization, cost-benefit analysis, and change management
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
Deliverables:
|
||||
- analysis.md: Main business analyst analysis
|
||||
- recommendations.md: Business analyst recommendations
|
||||
- deliverables/: Business analyst-specific outputs as defined in role template
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. Current State Business Analysis
|
||||
- Map existing business processes and workflows
|
||||
- Identify process inefficiencies and bottlenecks
|
||||
- Analyze current costs, resources, and time investments
|
||||
- Assess stakeholder roles and responsibilities
|
||||
- Document pain points and improvement opportunities
|
||||
Embody business analyst role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
2. Requirements Gathering and Analysis
|
||||
- Identify key stakeholders and their needs
|
||||
- Define functional and non-functional business requirements
|
||||
- Prioritize requirements based on business value and urgency
|
||||
- Analyze requirement dependencies and constraints
|
||||
- Create requirements traceability matrix
|
||||
|
||||
3. Process Design and Optimization
|
||||
- Design optimized future state processes
|
||||
- Identify automation opportunities and digital solutions
|
||||
- Plan for process standardization and best practices
|
||||
- Design quality gates and control points
|
||||
- Create process documentation and standard operating procedures
|
||||
|
||||
4. Cost-Benefit and ROI Analysis
|
||||
- Calculate implementation costs (people, technology, time)
|
||||
- Quantify expected benefits (cost savings, efficiency gains, revenue)
|
||||
- Perform ROI analysis and payback period calculation
|
||||
- Assess intangible benefits (customer satisfaction, employee morale)
|
||||
- Create business case with financial justification
|
||||
|
||||
5. Risk Assessment and Mitigation
|
||||
- Identify business, operational, and technical risks
|
||||
- Assess impact and probability of identified risks
|
||||
- Develop risk mitigation strategies and contingency plans
|
||||
- Plan for compliance and regulatory requirements
|
||||
- Design risk monitoring and control measures
|
||||
|
||||
6. Change Management and Implementation Planning
|
||||
- Assess organizational change readiness and impact
|
||||
- Design change management strategy and communication plan
|
||||
- Plan training and knowledge transfer requirements
|
||||
- Create implementation timeline with milestones
|
||||
- Design success metrics and monitoring framework
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/business-analyst/
|
||||
- analysis.md (main business analysis and process assessment)
|
||||
- requirements.md (detailed business requirements and specifications)
|
||||
- business-case.md (cost-benefit analysis and financial justification)
|
||||
- implementation-plan.md (change management and implementation strategy)
|
||||
|
||||
Apply business analysis expertise to optimize processes and maximize business value."
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather business analyst context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to business-analyst-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load business-analyst planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for business-analyst role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **Output Structure**
|
||||
|
||||
@@ -36,7 +36,6 @@ Strategic data professional responsible for designing scalable, efficient data a
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
@@ -60,96 +59,103 @@ Strategic data professional responsible for designing scalable, efficient data a
|
||||
- What balance between real-time dashboards and periodic reports is optimal?
|
||||
- What self-service analytics and data visualization capabilities are needed?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
```bash
|
||||
# Create data architect analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/data-architect/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**Data Architect Perspective Questioning**
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize data architect perspective analysis tracking:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize data architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze data requirements and sources", "status": "in_progress", "activeForm": "Analyzing data requirements"},
|
||||
{"content": "Design optimal data model and schema", "status": "pending", "activeForm": "Designing data model"},
|
||||
{"content": "Plan data pipeline and processing workflows", "status": "pending", "activeForm": "Planning data pipelines"},
|
||||
{"content": "Evaluate data quality and governance", "status": "pending", "activeForm": "Evaluating data governance"},
|
||||
{"content": "Design analytics and reporting solutions", "status": "pending", "activeForm": "Designing analytics"},
|
||||
{"content": "Generate comprehensive data architecture documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
]
|
||||
```
|
||||
Before agent assignment, gather comprehensive data architect context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
|
||||
**1. Data Models and Flow Patterns**
|
||||
- What types of data will you be working with (structured, semi-structured, unstructured)?
|
||||
- What are the expected data volumes and growth projections?
|
||||
- What are the primary data sources and how frequently will data be updated?
|
||||
- Are there existing data models or schemas that need to be considered?
|
||||
|
||||
**2. Storage Strategies and Performance**
|
||||
- What are the query performance requirements and expected response times?
|
||||
- Do you need real-time processing, batch processing, or both?
|
||||
- What are the data retention and archival requirements?
|
||||
- Are there specific compliance or regulatory requirements for data storage?
|
||||
|
||||
**3. Analytics Requirements and Insights**
|
||||
- What types of analytics and reporting capabilities are needed?
|
||||
- Who are the primary users of the data and what are their skill levels?
|
||||
- What business intelligence or machine learning use cases need to be supported?
|
||||
- Are there specific dashboard or visualization requirements?
|
||||
|
||||
**4. Data Governance and Quality**
|
||||
- What data quality standards and validation rules need to be implemented?
|
||||
- Who owns the data and what are the access control requirements?
|
||||
- Are there data privacy or security concerns that need to be addressed?
|
||||
- What data lineage and auditing capabilities are required?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/data-architect-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
### Phase 4: Conceptual Planning Agent Coordination
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
Conduct data architect perspective brainstorming for: {topic}
|
||||
[FLOW_CONTROL]
|
||||
|
||||
ROLE CONTEXT: Data Architect
|
||||
- Focus Areas: Data modeling, data flow, storage optimization, analytics infrastructure
|
||||
- Analysis Framework: Data-driven approach with emphasis on scalability, quality, and insights
|
||||
- Success Metrics: Data quality, processing efficiency, analytics accuracy, scalability
|
||||
Execute dedicated data architect conceptual analysis for: {topic}
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
ASSIGNED_ROLE: data-architect
|
||||
OUTPUT_LOCATION: .brainstorming/data-architect/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. Data Requirements Analysis
|
||||
- Identify all data sources (internal, external, third-party)
|
||||
- Define data collection requirements and constraints
|
||||
- Analyze data volume, velocity, and variety characteristics
|
||||
- Map data lineage and dependencies across systems
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load data-architect planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load data-architect)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
2. Data Model and Schema Design
|
||||
- Design logical and physical data models for optimal performance
|
||||
- Plan database schemas, indexes, and partitioning strategies
|
||||
- Design data relationships and referential integrity constraints
|
||||
- Plan for data archival, retention, and lifecycle management
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply data architect perspective to topic analysis
|
||||
- Focus on data models, flow patterns, storage strategies, and analytics requirements
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
3. Data Pipeline Architecture
|
||||
- Design ETL/ELT processes for data ingestion and transformation
|
||||
- Plan real-time and batch processing workflows
|
||||
- Design error handling, monitoring, and alerting mechanisms
|
||||
- Plan for data pipeline scalability and performance optimization
|
||||
Deliverables:
|
||||
- analysis.md: Main data architect analysis
|
||||
- recommendations.md: Data architect recommendations
|
||||
- deliverables/: Data architect-specific outputs as defined in role template
|
||||
|
||||
4. Data Quality and Governance
|
||||
- Establish data quality metrics and validation rules
|
||||
- Design data governance policies and procedures
|
||||
- Plan data security, privacy, and compliance frameworks
|
||||
- Create data cataloging and metadata management strategies
|
||||
Embody data architect role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
5. Analytics and Business Intelligence
|
||||
- Design data warehouse and data mart architectures
|
||||
- Plan for OLAP cubes, reporting, and dashboard requirements
|
||||
- Design self-service analytics and data exploration capabilities
|
||||
- Plan for machine learning and advanced analytics integration
|
||||
|
||||
6. Performance and Scalability Planning
|
||||
- Analyze current and projected data volumes and growth
|
||||
- Design horizontal and vertical scaling strategies
|
||||
- Plan for high availability and disaster recovery
|
||||
- Optimize query performance and resource utilization
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/data-architect/
|
||||
- analysis.md (main data architecture analysis)
|
||||
- data-model.md (data models, schemas, and relationships)
|
||||
- pipeline-design.md (data processing and ETL/ELT workflows)
|
||||
- governance-plan.md (data quality, security, and governance)
|
||||
|
||||
Apply data architecture expertise to create scalable, reliable, and insightful data solutions."
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather data architect context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to data-architect-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load data-architect planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for data-architect role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **Output Specification**
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: planner
|
||||
name: feature-planner
|
||||
description: Feature planner perspective brainstorming for feature development and planning analysis
|
||||
usage: /workflow:brainstorm:feature-planner <topic>
|
||||
argument-hint: "topic or challenge to analyze from feature planning perspective"
|
||||
@@ -10,142 +10,152 @@ examples:
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
## 🔧 **角色定义: Feature Planner**
|
||||
## 🔧 **Role Overview: Feature Planner**
|
||||
|
||||
### 核心职责
|
||||
- **功能规划**: 设计和规划产品功能的开发路线图
|
||||
- **需求转化**: 将业务需求转化为具体的功能规范
|
||||
- **优先级排序**: 基于价值和资源平衡功能开发优先级
|
||||
- **交付规划**: 制定功能开发和发布时间表
|
||||
### Role Definition
|
||||
Feature development specialist responsible for transforming business requirements into actionable feature specifications, managing development priorities, and ensuring successful feature delivery through strategic planning and execution.
|
||||
|
||||
### 关注领域
|
||||
- **功能设计**: 功能规范、用户故事、验收标准
|
||||
- **开发规划**: 迭代计划、里程碑、依赖关系管理
|
||||
- **质量保证**: 测试策略、质量标准、验收流程
|
||||
- **发布管理**: 发布策略、版本控制、变更管理
|
||||
### Core Responsibilities
|
||||
- **Feature Specification**: Transform business requirements into detailed feature specifications
|
||||
- **Development Planning**: Create development roadmaps and manage feature priorities
|
||||
- **Quality Assurance**: Design testing strategies and acceptance criteria
|
||||
- **Delivery Management**: Plan feature releases and manage implementation timelines
|
||||
|
||||
### Focus Areas
|
||||
- **Feature Design**: User stories, acceptance criteria, feature specifications
|
||||
- **Development Planning**: Sprint planning, milestones, dependency management
|
||||
- **Quality Assurance**: Testing strategies, quality gates, acceptance processes
|
||||
- **Release Management**: Release planning, version control, change management
|
||||
|
||||
### Success Metrics
|
||||
- Feature delivery on time and within scope
|
||||
- Quality standards and acceptance criteria met
|
||||
- User satisfaction with delivered features
|
||||
- Development team productivity and efficiency
|
||||
|
||||
## 🧠 **分析框架**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### 核心分析问题
|
||||
1. **功能需求分析**:
|
||||
- 核心功能需求和用户故事？
|
||||
- 功能的MVP和完整版本规划？
|
||||
- 跨功能依赖和集成需求？
|
||||
### Key Analysis Questions
|
||||
|
||||
2. **技术可行性评估**:
|
||||
- 技术实现的复杂度和挑战？
|
||||
- 现有系统的扩展和改造需求？
|
||||
- 第三方服务和API集成？
|
||||
**1. Feature Requirements and Scope**
|
||||
- What are the core feature requirements and user stories?
|
||||
- How should MVP and full feature versions be planned?
|
||||
- What cross-feature dependencies and integration requirements exist?
|
||||
|
||||
3. **开发资源和时间估算**:
|
||||
- 开发工作量和时间预估？
|
||||
- 所需技能和团队配置？
|
||||
- 开发风险和缓解策略？
|
||||
**2. Implementation Complexity and Feasibility**
|
||||
- What is the technical implementation complexity and what challenges exist?
|
||||
- What extensions or modifications to existing systems are required?
|
||||
- What third-party services and API integrations are needed?
|
||||
|
||||
4. **测试和质量保证**:
|
||||
- 测试策略和测试用例设计？
|
||||
- 质量标准和验收条件？
|
||||
- 用户验收和反馈机制？
|
||||
**3. Development Resources and Timeline**
|
||||
- What are the development effort estimates and time projections?
|
||||
- What skills and team configurations are required?
|
||||
- What development risks exist and how can they be mitigated?
|
||||
|
||||
## ⚙️ **执行协议**
|
||||
**4. Testing and Quality Assurance**
|
||||
- What testing strategies and test case designs are needed?
|
||||
- What quality standards and acceptance criteria should be defined?
|
||||
- What user acceptance and feedback mechanisms are required?
|
||||
|
||||
### Phase 1: 会话检测与初始化
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# 自动检测活动会话
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: 目录结构创建
|
||||
```bash
|
||||
# 创建功能规划师分析目录
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/feature-planner/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**Feature Planner Perspective Questioning**
|
||||
|
||||
### Phase 3: TodoWrite 初始化
|
||||
设置功能规划师视角分析的任务跟踪：
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize feature planner brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze feature requirements and user stories", "status": "in_progress", "activeForm": "Analyzing feature requirements"},
|
||||
{"content": "Design feature architecture and specifications", "status": "pending", "activeForm": "Designing feature architecture"},
|
||||
{"content": "Plan development phases and prioritization", "status": "pending", "activeForm": "Planning development phases"},
|
||||
{"content": "Evaluate testing strategy and quality assurance", "status": "pending", "activeForm": "Evaluating testing strategy"},
|
||||
{"content": "Create implementation timeline and milestones", "status": "pending", "activeForm": "Creating timeline"},
|
||||
{"content": "Generate comprehensive feature planning documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
]
|
||||
```
|
||||
Before agent assignment, gather comprehensive feature planner context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
|
||||
**1. Implementation Complexity and Scope**
|
||||
- What is the scope and complexity of the features you want to plan?
|
||||
- Are there existing features or systems that need to be extended or integrated?
|
||||
- What are the technical constraints or requirements that need to be considered?
|
||||
- How do these features fit into the overall product roadmap?
|
||||
|
||||
**2. Dependency Mapping and Integration**
|
||||
- What other features, systems, or teams does this depend on?
|
||||
- Are there any external APIs, services, or third-party integrations required?
|
||||
- What are the data dependencies and how will data flow between components?
|
||||
- What are the potential blockers or risks that could impact development?
|
||||
|
||||
**3. Risk Assessment and Mitigation**
|
||||
- What are the main technical, business, or timeline risks?
|
||||
- Are there any unknowns or areas that need research or prototyping?
|
||||
- What fallback plans or alternative approaches should be considered?
|
||||
- How will quality and testing be ensured throughout development?
|
||||
|
||||
**4. Technical Feasibility and Resource Planning**
|
||||
- What is the estimated development effort and timeline?
|
||||
- What skills, expertise, or team composition is needed?
|
||||
- Are there any specific technologies, tools, or frameworks required?
|
||||
- What are the performance, scalability, or maintenance considerations?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/feature-planner-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
### Phase 4: 概念规划代理协调
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
Conduct feature planner perspective brainstorming for: {topic}
|
||||
[FLOW_CONTROL]
|
||||
|
||||
ROLE CONTEXT: Feature Planner
|
||||
- Focus Areas: Feature specification, development planning, quality assurance, delivery management
|
||||
- Analysis Framework: Feature-centric approach with emphasis on deliverability and user value
|
||||
- Success Metrics: Feature completion, quality standards, user satisfaction, delivery timeline
|
||||
Execute dedicated feature planner conceptual analysis for: {topic}
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
ASSIGNED_ROLE: feature-planner
|
||||
OUTPUT_LOCATION: .brainstorming/feature-planner/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. Feature Requirements Analysis
|
||||
- Break down high-level requirements into specific feature specifications
|
||||
- Create detailed user stories with acceptance criteria
|
||||
- Identify feature dependencies and integration requirements
|
||||
- Map features to user personas and use cases
|
||||
- Define feature scope and boundaries (MVP vs full feature)
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load feature-planner planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load feature-planner)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
2. Feature Architecture and Design
|
||||
- Design feature workflows and user interaction patterns
|
||||
- Plan feature integration with existing system components
|
||||
- Define APIs and data interfaces required
|
||||
- Plan for feature configuration and customization options
|
||||
- Design feature monitoring and analytics capabilities
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply feature planner perspective to topic analysis
|
||||
- Focus on implementation complexity, dependency mapping, risk assessment, and technical feasibility
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
3. Development Planning and Estimation
|
||||
- Estimate development effort and complexity for each feature
|
||||
- Identify technical risks and implementation challenges
|
||||
- Plan feature development phases and incremental delivery
|
||||
- Define development milestones and checkpoints
|
||||
- Assess resource requirements and team capacity
|
||||
Deliverables:
|
||||
- analysis.md: Main feature planner analysis
|
||||
- recommendations.md: Feature planner recommendations
|
||||
- deliverables/: Feature planner-specific outputs as defined in role template
|
||||
|
||||
4. Quality Assurance and Testing Strategy
|
||||
- Design comprehensive testing strategy (unit, integration, E2E)
|
||||
- Create test scenarios and edge case coverage
|
||||
- Plan performance testing and scalability validation
|
||||
- Design user acceptance testing procedures
|
||||
- Plan for accessibility and usability testing
|
||||
Embody feature planner role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
5. Feature Prioritization and Roadmap
|
||||
- Apply prioritization frameworks (MoSCoW, Kano, RICE)
|
||||
- Balance business value with development complexity
|
||||
- Create feature release planning and versioning strategy
|
||||
- Plan for feature flags and gradual rollout
|
||||
- Design feature deprecation and sunset strategies
|
||||
|
||||
6. Delivery and Release Management
|
||||
- Plan feature delivery timeline and release schedule
|
||||
- Design change management and deployment strategies
|
||||
- Plan for feature documentation and user training
|
||||
- Create feature success metrics and KPIs
|
||||
- Design post-release monitoring and support plans
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/feature-planner/
|
||||
- analysis.md (main feature analysis and specifications)
|
||||
- user-stories.md (detailed user stories and acceptance criteria)
|
||||
- development-plan.md (development timeline and resource planning)
|
||||
- testing-strategy.md (quality assurance and testing approach)
|
||||
|
||||
Apply feature planning expertise to create deliverable, high-quality feature implementations."
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather feature planner context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to feature-planner-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load feature-planner planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for feature-planner role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **输出结构**
|
||||
|
||||
@@ -10,150 +10,152 @@ examples:
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
## 🚀 **角色定义: Innovation Lead**
|
||||
## 🚀 **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.
|
||||
|
||||
### 关注领域
|
||||
- **新兴技术**: AI、区块链、IoT、AR/VR、量子计算等前沿技术
|
||||
- **市场趋势**: 行业变革、用户行为演进、商业模式创新
|
||||
- **创新机会**: 破坏性创新、蓝海市场、技术融合机会
|
||||
- **未来愿景**: 长期技术路线图、概念验证、原型开发
|
||||
### 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
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### 核心分析问题
|
||||
1. **技术趋势和机会**:
|
||||
- 哪些新兴技术对我们的行业最有影响？
|
||||
- 技术成熟度和采用时间轴？
|
||||
- 技术融合创造的新机会？
|
||||
### Key Analysis Questions
|
||||
|
||||
2. **创新潜力评估**:
|
||||
- 破坏性创新的可能性和影响？
|
||||
- 现有解决方案的创新空间？
|
||||
- 未被满足的市场需求？
|
||||
**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?
|
||||
|
||||
3. **竞争和市场分析**:
|
||||
- 竞争对手的创新动向？
|
||||
- 市场空白和蓝海机会？
|
||||
- 技术壁垒和先发优势？
|
||||
**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?
|
||||
|
||||
4. **实施和风险评估**:
|
||||
- 技术实施的可行性和风险？
|
||||
- 投资需求和预期回报？
|
||||
- 组织创新能力和适应性？
|
||||
**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?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
**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?
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
```bash
|
||||
# Create innovation lead analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/innovation-lead/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**Innovation Lead Perspective Questioning**
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize innovation lead perspective analysis tracking:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize innovation lead brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Research emerging technology trends and opportunities", "status": "in_progress", "activeForm": "Researching technology trends"},
|
||||
{"content": "Analyze innovation potential and market disruption", "status": "pending", "activeForm": "Analyzing innovation potential"},
|
||||
{"content": "Evaluate competitive landscape and positioning", "status": "pending", "activeForm": "Evaluating competitive landscape"},
|
||||
{"content": "Design future-oriented solutions and concepts", "status": "pending", "activeForm": "Designing future solutions"},
|
||||
{"content": "Assess implementation feasibility and roadmap", "status": "pending", "activeForm": "Assessing implementation"},
|
||||
{"content": "Generate comprehensive innovation strategy documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
]
|
||||
```
|
||||
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**
|
||||
|
||||
### Phase 4: Conceptual Planning Agent Coordination
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute dedicated innovation lead conceptual analysis for: {topic}
|
||||
|
||||
ASSIGNED_ROLE: innovation-lead
|
||||
GEMINI_ANALYSIS_REQUIRED: true
|
||||
ANALYSIS_DIMENSIONS:
|
||||
- emerging_patterns
|
||||
- technology_trends
|
||||
- disruption_potential
|
||||
- innovation_opportunities
|
||||
OUTPUT_LOCATION: .brainstorming/innovation-lead/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
Conduct innovation lead perspective brainstorming for: {topic}
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load innovation-lead planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load innovation-lead)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
ROLE CONTEXT: Innovation Lead
|
||||
- Focus Areas: Emerging technologies, market disruption, future opportunities, innovation strategy
|
||||
- Analysis Framework: Forward-thinking approach with emphasis on breakthrough innovation and competitive advantage
|
||||
- Success Metrics: Innovation impact, market differentiation, technology adoption, future readiness
|
||||
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
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
Deliverables:
|
||||
- analysis.md: Main innovation lead analysis
|
||||
- recommendations.md: Innovation lead recommendations
|
||||
- deliverables/: Innovation lead-specific outputs as defined in role template
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. Emerging Technology Landscape Analysis
|
||||
- Research current and emerging technology trends relevant to the topic
|
||||
- Analyze technology maturity levels and adoption curves
|
||||
- Identify breakthrough technologies with disruptive potential
|
||||
- Assess technology convergence opportunities and synergies
|
||||
- Map technology evolution timelines and critical milestones
|
||||
Embody innovation lead role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
2. Innovation Opportunity Assessment
|
||||
- Identify unmet market needs and whitespace opportunities
|
||||
- Analyze potential for disruptive innovation vs incremental improvement
|
||||
- Assess blue ocean market opportunities and new value propositions
|
||||
- Evaluate cross-industry innovation transfer possibilities
|
||||
- Identify platform and ecosystem innovation opportunities
|
||||
|
||||
3. Competitive Intelligence and Market Analysis
|
||||
- Analyze competitor innovation strategies and technology investments
|
||||
- Identify market leaders and emerging disruptors
|
||||
- Assess patent landscapes and intellectual property opportunities
|
||||
- Evaluate startup ecosystem and potential acquisition targets
|
||||
- Analyze venture capital and funding trends in related areas
|
||||
|
||||
4. Future Scenario Planning
|
||||
- Design multiple future scenarios based on technology trends
|
||||
- Create technology roadmaps with short, medium, and long-term horizons
|
||||
- Identify potential black swan events and wild card scenarios
|
||||
- Plan for technology convergence and platform shifts
|
||||
- Design adaptive strategies for uncertain futures
|
||||
|
||||
5. Innovation Concept Development
|
||||
- Generate breakthrough product and service concepts
|
||||
- Design minimum viable innovation experiments
|
||||
- Create proof-of-concept prototyping strategies
|
||||
- Plan innovation pilot programs and validation approaches
|
||||
- Design scalable innovation frameworks and processes
|
||||
|
||||
6. Implementation Strategy and Risk Assessment
|
||||
- Assess organizational innovation readiness and capabilities
|
||||
- Identify required technology investments and partnerships
|
||||
- Evaluate risks including technology, market, and execution risks
|
||||
- Design innovation governance and decision-making frameworks
|
||||
- Plan talent acquisition and capability building strategies
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/innovation-lead/
|
||||
- analysis.md (main innovation analysis and opportunity assessment)
|
||||
- technology-roadmap.md (technology trends and future scenarios)
|
||||
- innovation-concepts.md (breakthrough ideas and concept development)
|
||||
- strategy-implementation.md (innovation strategy and execution plan)
|
||||
|
||||
Apply innovation leadership expertise to identify breakthrough opportunities and design future-ready strategies."
|
||||
### 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"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **输出结构**
|
||||
|
||||
@@ -36,7 +36,6 @@ Strategic product leader focused on maximizing user value and business impact th
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
@@ -60,84 +59,98 @@ Strategic product leader focused on maximizing user value and business impact th
|
||||
- What are the technical and market risks?
|
||||
- Do we have the right team capabilities?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
```bash
|
||||
# Create product manager analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/product-manager/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**Product Manager Perspective Questioning**
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize product manager perspective analysis tracking:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize product manager brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze user needs and pain points", "status": "in_progress", "activeForm": "Analyzing user needs"},
|
||||
{"content": "Evaluate business value and impact", "status": "pending", "activeForm": "Evaluating business impact"},
|
||||
{"content": "Assess market opportunities", "status": "pending", "activeForm": "Assessing market opportunities"},
|
||||
{"content": "Develop product strategy recommendations", "status": "pending", "activeForm": "Developing strategy"},
|
||||
{"content": "Create prioritized action plan", "status": "pending", "activeForm": "Creating action plan"},
|
||||
{"content": "Generate comprehensive product analysis", "status": "pending", "activeForm": "Generating analysis"}
|
||||
]
|
||||
```
|
||||
Before agent assignment, gather comprehensive product management context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
1. **Business Objectives & Metrics**
|
||||
- Primary business goals and success metrics?
|
||||
- Revenue impact expectations and timeline?
|
||||
- Key stakeholders and decision makers?
|
||||
|
||||
2. **Target Users & Market**
|
||||
- Primary user segments and personas?
|
||||
- User pain points and current solutions?
|
||||
- Competitive landscape and differentiation needs?
|
||||
|
||||
3. **Product Strategy & Scope**
|
||||
- Feature priorities and user value propositions?
|
||||
- Resource constraints and timeline expectations?
|
||||
- Integration with existing product ecosystem?
|
||||
|
||||
4. **Success Criteria & Risk Assessment**
|
||||
- How will success be measured and validated?
|
||||
- Market and technical risks to consider?
|
||||
- Go-to-market strategy requirements?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/product-manager-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
### Phase 4: Conceptual Planning Agent Coordination
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
Conduct product management perspective brainstorming for: {topic}
|
||||
[FLOW_CONTROL]
|
||||
|
||||
ROLE CONTEXT: Product Manager
|
||||
- Focus Areas: User needs, business value, market positioning, product strategy
|
||||
- Analysis Framework: User-centric approach with business impact assessment
|
||||
- Success Metrics: User satisfaction, business growth, market differentiation
|
||||
Execute dedicated product-manager conceptual analysis for: {topic}
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
ASSIGNED_ROLE: product-manager
|
||||
OUTPUT_LOCATION: .brainstorming/product-manager/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. User Needs Analysis
|
||||
- Identify core user problems and pain points
|
||||
- Define target user segments and personas
|
||||
- Map user journey and experience gaps
|
||||
- Prioritize user requirements by impact and frequency
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load product-manager planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load product-manager)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
2. Business Value Assessment
|
||||
- Quantify potential business impact (revenue, growth, efficiency)
|
||||
- Analyze cost-benefit ratio and ROI projections
|
||||
- Identify key success metrics and KPIs
|
||||
- Assess risk factors and mitigation strategies
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply product-manager perspective to topic analysis
|
||||
- Focus on user value, business impact, and market positioning
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
3. Market Opportunity Analysis
|
||||
- Competitive landscape and gap analysis
|
||||
- Market trends and emerging opportunities
|
||||
- Differentiation strategies and unique value propositions
|
||||
- Go-to-market considerations
|
||||
Deliverables:
|
||||
- analysis.md: Main product management analysis
|
||||
- recommendations.md: Product strategy recommendations
|
||||
- deliverables/: Product-specific outputs as defined in role template
|
||||
|
||||
4. Product Strategy Development
|
||||
- Feature prioritization matrix
|
||||
- Product roadmap recommendations
|
||||
- Resource allocation strategies
|
||||
- Implementation timeline and milestones
|
||||
Embody product-manager role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/product-manager/
|
||||
- analysis.md (main product management analysis)
|
||||
- business-case.md (business justification and metrics)
|
||||
- user-research.md (user needs and market insights)
|
||||
- roadmap.md (strategic recommendations and timeline)
|
||||
|
||||
Apply product management expertise to generate actionable insights addressing business goals and user needs."
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather product manager context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to product-manager-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load product-manager planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for product-manager role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **Output Specification**
|
||||
|
||||
@@ -36,7 +36,6 @@ Cybersecurity specialist focused on identifying threats, designing security cont
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
@@ -60,36 +59,97 @@ Cybersecurity specialist focused on identifying threats, designing security cont
|
||||
- What monitoring and detection capabilities are required?
|
||||
- How should we plan for incident response and recovery?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
### Step 1: Context Gathering Phase
|
||||
**Security Expert Perspective Questioning**
|
||||
|
||||
Before agent assignment, gather comprehensive security context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
1. **Threat Assessment & Attack Vectors**
|
||||
- Sensitive data types and classification levels?
|
||||
- Known threat actors and attack scenarios?
|
||||
- Current security vulnerabilities and concerns?
|
||||
|
||||
2. **Compliance & Regulatory Requirements**
|
||||
- Applicable compliance standards (GDPR, SOX, HIPAA)?
|
||||
- Industry-specific security requirements?
|
||||
- Audit and reporting obligations?
|
||||
|
||||
3. **Security Architecture & Controls**
|
||||
- Authentication and authorization needs?
|
||||
- Data encryption and protection requirements?
|
||||
- Network security and access control strategy?
|
||||
|
||||
4. **Incident Response & Monitoring**
|
||||
- Security monitoring and detection capabilities?
|
||||
- Incident response procedures and team readiness?
|
||||
- Business continuity and disaster recovery plans?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/security-expert-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
```bash
|
||||
# Create security expert analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/security-expert/
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute dedicated security-expert conceptual analysis for: {topic}
|
||||
|
||||
ASSIGNED_ROLE: security-expert
|
||||
OUTPUT_LOCATION: .brainstorming/security-expert/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load security-expert planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load security-expert)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply security-expert perspective to topic analysis
|
||||
- Focus on threat modeling, security architecture, and risk assessment
|
||||
- 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 security analysis
|
||||
- recommendations.md: Security recommendations
|
||||
- deliverables/: Security-specific outputs as defined in role template
|
||||
|
||||
Embody security-expert role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize security expert perspective analysis tracking:
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize security expert brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Conduct threat modeling and risk assessment", "status": "in_progress", "activeForm": "Conducting threat modeling"},
|
||||
{"content": "Design security architecture and controls", "status": "pending", "activeForm": "Designing security architecture"},
|
||||
{"content": "Evaluate compliance and regulatory requirements", "status": "pending", "activeForm": "Evaluating compliance"},
|
||||
{"content": "Plan security implementation and integration", "status": "pending", "activeForm": "Planning implementation"},
|
||||
{"content": "Design monitoring and incident response", "status": "pending", "activeForm": "Designing monitoring"},
|
||||
{"content": "Generate comprehensive security documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
{"content": "Gather security expert context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to security-expert-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load security-expert planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for security-expert role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
|
||||
@@ -36,7 +36,6 @@ Technical leader responsible for designing scalable, maintainable, and high-perf
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
@@ -60,90 +59,98 @@ Technical leader responsible for designing scalable, maintainable, and high-perf
|
||||
- How should we handle traffic growth and scaling demands?
|
||||
- What database scaling and optimization strategies are needed?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
```bash
|
||||
# Create system architect analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**System Architect Perspective Questioning**
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize system architect perspective analysis tracking:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize system architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze current system architecture", "status": "in_progress", "activeForm": "Analyzing architecture"},
|
||||
{"content": "Evaluate technical requirements and constraints", "status": "pending", "activeForm": "Evaluating requirements"},
|
||||
{"content": "Design optimal system architecture", "status": "pending", "activeForm": "Designing architecture"},
|
||||
{"content": "Assess scalability and performance", "status": "pending", "activeForm": "Assessing scalability"},
|
||||
{"content": "Plan technology stack and integration", "status": "pending", "activeForm": "Planning technology"},
|
||||
{"content": "Generate comprehensive architecture documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
]
|
||||
```
|
||||
Before agent assignment, gather comprehensive system architecture context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
1. **Scale & Performance Requirements**
|
||||
- Expected user load and traffic patterns?
|
||||
- Performance requirements (latency, throughput)?
|
||||
- Data volume and growth projections?
|
||||
|
||||
2. **Technical Constraints & Environment**
|
||||
- Existing technology stack and constraints?
|
||||
- Integration requirements with external systems?
|
||||
- Infrastructure and deployment environment?
|
||||
|
||||
3. **Architecture Complexity & Patterns**
|
||||
- Microservices vs monolithic considerations?
|
||||
- Data consistency and transaction requirements?
|
||||
- Event-driven vs request-response patterns?
|
||||
|
||||
4. **Non-Functional Requirements**
|
||||
- High availability and disaster recovery needs?
|
||||
- Security and compliance requirements?
|
||||
- Monitoring and observability expectations?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/system-architect-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
### Phase 4: Conceptual Planning Agent Coordination
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
Conduct system architecture perspective brainstorming for: {topic}
|
||||
[FLOW_CONTROL]
|
||||
|
||||
ROLE CONTEXT: System Architect
|
||||
- Focus Areas: Technical architecture, scalability, system integration, performance
|
||||
- Analysis Framework: Architecture-first approach with scalability and maintainability focus
|
||||
- Success Metrics: System performance, availability, maintainability, technical debt reduction
|
||||
Execute dedicated system-architect conceptual analysis for: {topic}
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
ASSIGNED_ROLE: system-architect
|
||||
OUTPUT_LOCATION: .brainstorming/system-architect/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. Current Architecture Assessment
|
||||
- Analyze existing system architecture and identify pain points
|
||||
- Evaluate current technology stack effectiveness
|
||||
- Assess technical debt and maintenance overhead
|
||||
- Identify architectural bottlenecks and limitations
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load system-architect planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load system-architect)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
2. Requirements and Constraints Analysis
|
||||
- Define functional and non-functional requirements
|
||||
- Identify performance, scalability, and availability requirements
|
||||
- Analyze security and compliance constraints
|
||||
- Assess resource and budget limitations
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply system-architect perspective to topic analysis
|
||||
- Focus on architectural patterns, scalability, and integration points
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
3. Architecture Design and Strategy
|
||||
- Design optimal system architecture for the given requirements
|
||||
- Recommend technology stack and architectural patterns
|
||||
- Plan for microservices vs monolithic architecture decisions
|
||||
- Design data architecture and storage strategies
|
||||
Deliverables:
|
||||
- analysis.md: Main system architecture analysis
|
||||
- recommendations.md: Architecture recommendations
|
||||
- deliverables/: Architecture-specific outputs as defined in role template
|
||||
|
||||
4. Integration and Scalability Planning
|
||||
- Design system integration patterns and APIs
|
||||
- Plan for horizontal and vertical scaling strategies
|
||||
- Design monitoring, logging, and observability systems
|
||||
- Plan deployment and DevOps strategies
|
||||
Embody system-architect role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
5. Risk Assessment and Mitigation
|
||||
- Identify technical risks and failure points
|
||||
- Design fault tolerance and disaster recovery strategies
|
||||
- Plan for security vulnerabilities and mitigations
|
||||
- Assess migration risks and strategies
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/system-architect/
|
||||
- analysis.md (main architecture analysis)
|
||||
- architecture-design.md (detailed system design and diagrams)
|
||||
- technology-stack.md (technology recommendations and justifications)
|
||||
- integration-plan.md (system integration and API strategies)
|
||||
|
||||
Apply system architecture expertise to generate scalable, maintainable, and performant solutions."
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather system architect context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to system-architect-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load system-architect planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for system-architect role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **Output Specification**
|
||||
|
||||
@@ -36,7 +36,6 @@ Creative professional responsible for designing intuitive, accessible, and visua
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
@@ -60,36 +59,97 @@ Creative professional responsible for designing intuitive, accessible, and visua
|
||||
- What responsive design requirements must be addressed?
|
||||
- How do performance considerations impact user experience?
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### Phase 1: Session Detection & Initialization
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Detect active workflow session
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: Directory Structure Creation
|
||||
### Step 1: Context Gathering Phase
|
||||
**UI Designer Perspective Questioning**
|
||||
|
||||
Before agent assignment, gather comprehensive UI/UX design context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
1. **User Experience & Personas**
|
||||
- Primary user personas and their key characteristics?
|
||||
- Current user pain points and usability issues?
|
||||
- Platform requirements (web, mobile, desktop)?
|
||||
|
||||
2. **Design System & Branding**
|
||||
- Existing design system and brand guidelines?
|
||||
- Visual design preferences and constraints?
|
||||
- Accessibility and compliance requirements?
|
||||
|
||||
3. **User Journey & Interactions**
|
||||
- Key user workflows and task flows?
|
||||
- Critical interaction points and user goals?
|
||||
- Performance and responsive design requirements?
|
||||
|
||||
4. **Implementation & Integration**
|
||||
- Technical constraints and development capabilities?
|
||||
- Integration with existing UI components?
|
||||
- Testing and validation approach?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/ui-designer-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
```bash
|
||||
# Create UI designer analysis directory
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute dedicated ui-designer conceptual analysis for: {topic}
|
||||
|
||||
ASSIGNED_ROLE: ui-designer
|
||||
OUTPUT_LOCATION: .brainstorming/ui-designer/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load ui-designer planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load ui-designer)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply ui-designer perspective to topic analysis
|
||||
- Focus on user experience, interface design, and interaction patterns
|
||||
- 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 UI/UX design analysis
|
||||
- recommendations.md: Design recommendations
|
||||
- deliverables/: UI-specific outputs as defined in role template
|
||||
|
||||
Embody ui-designer role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
### Phase 3: Task Tracking Initialization
|
||||
Initialize UI designer perspective analysis tracking:
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize UI designer brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze current user experience and pain points", "status": "in_progress", "activeForm": "Analyzing user experience"},
|
||||
{"content": "Design user journey and interaction flows", "status": "pending", "activeForm": "Designing user flows"},
|
||||
{"content": "Create visual design concepts and mockups", "status": "pending", "activeForm": "Creating visual concepts"},
|
||||
{"content": "Evaluate accessibility and usability", "status": "pending", "activeForm": "Evaluating accessibility"},
|
||||
{"content": "Plan responsive design strategy", "status": "pending", "activeForm": "Planning responsive design"},
|
||||
{"content": "Generate comprehensive UI/UX documentation", "status": "pending", "activeForm": "Generating documentation"}
|
||||
{"content": "Gather ui-designer context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to ui-designer-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load ui-designer planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for ui-designer role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
|
||||
@@ -10,142 +10,152 @@ examples:
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
## 🔍 **角色定义: User Researcher**
|
||||
## 🔍 **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
|
||||
@~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
### 核心分析问题
|
||||
1. **用户理解和洞察**:
|
||||
- 目标用户的真实需求和痛点是什么？
|
||||
- 用户的行为模式和使用场景？
|
||||
- 不同用户群体的差异化需求？
|
||||
### Key Analysis Questions
|
||||
|
||||
2. **用户体验分析**:
|
||||
- 当前用户体验的主要问题？
|
||||
- 用户任务完成的障碍和摩擦点？
|
||||
- 用户满意度和期望差距？
|
||||
**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?
|
||||
|
||||
3. **研究方法和验证**:
|
||||
- 哪些研究方法最适合当前问题？
|
||||
- 如何验证假设和设计决策？
|
||||
- 如何持续收集用户反馈？
|
||||
**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?
|
||||
|
||||
4. **洞察转化和应用**:
|
||||
- 研究发现如何转化为产品改进？
|
||||
- 如何影响产品决策和设计？
|
||||
- 如何建立以用户为中心的文化？
|
||||
**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?
|
||||
|
||||
### Phase 1: 会话检测与初始化
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# 自动检测活动会话
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
load_context_from(session_id)
|
||||
ELSE:
|
||||
request_user_for_session_creation()
|
||||
# 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
|
||||
```
|
||||
|
||||
### Phase 2: 目录结构创建
|
||||
```bash
|
||||
# 创建用户研究员分析目录
|
||||
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
|
||||
```
|
||||
### Step 1: Context Gathering Phase
|
||||
**User Researcher Perspective Questioning**
|
||||
|
||||
### Phase 3: TodoWrite 初始化
|
||||
设置用户研究员视角分析的任务跟踪：
|
||||
```json
|
||||
[
|
||||
{"content": "Initialize user researcher brainstorming session", "status": "completed", "activeForm": "Initializing session"},
|
||||
{"content": "Analyze user behavior patterns and motivations", "status": "in_progress", "activeForm": "Analyzing user behavior"},
|
||||
{"content": "Identify user needs and pain points", "status": "pending", "activeForm": "Identifying user needs"},
|
||||
{"content": "Evaluate current user experience", "status": "pending", "activeForm": "Evaluating user experience"},
|
||||
{"content": "Design user research methodology", "status": "pending", "activeForm": "Designing research methodology"},
|
||||
{"content": "Generate user insights and recommendations", "status": "pending", "activeForm": "Generating insights"},
|
||||
{"content": "Create comprehensive user research documentation", "status": "pending", "activeForm": "Creating documentation"}
|
||||
]
|
||||
```
|
||||
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**
|
||||
|
||||
### Phase 4: 概念规划代理协调
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
Conduct user researcher perspective brainstorming for: {topic}
|
||||
[FLOW_CONTROL]
|
||||
|
||||
ROLE CONTEXT: User Researcher
|
||||
- Focus Areas: User behavior analysis, needs discovery, usability assessment, research methodology
|
||||
- Analysis Framework: Human-centered research approach with emphasis on behavioral insights
|
||||
- Success Metrics: User satisfaction, task success rates, insight quality, research impact
|
||||
Execute dedicated user researcher conceptual analysis for: {topic}
|
||||
|
||||
USER CONTEXT: {captured_user_requirements_from_session}
|
||||
ASSIGNED_ROLE: user-researcher
|
||||
OUTPUT_LOCATION: .brainstorming/user-researcher/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
ANALYSIS REQUIREMENTS:
|
||||
1. User Behavior Analysis
|
||||
- Analyze current user behavior patterns and usage data
|
||||
- Identify user decision-making processes and mental models
|
||||
- Map user journeys and touchpoint interactions
|
||||
- Assess user motivations and goals across different scenarios
|
||||
- Identify behavioral segments and usage patterns
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load user-researcher planning template\",
|
||||
\"command\": \"bash(~/.claude/scripts/planning-role-load.sh load user-researcher)\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
2. User Needs and Pain Points Discovery
|
||||
- Conduct gap analysis between user needs and current solutions
|
||||
- Identify unmet needs and latent requirements
|
||||
- Analyze user feedback and support data for pain points
|
||||
- Map emotional user journey and frustration points
|
||||
- Prioritize needs based on user impact and frequency
|
||||
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
|
||||
|
||||
3. Usability and Experience Assessment
|
||||
- Evaluate current user experience against best practices
|
||||
- Identify usability heuristics violations and UX issues
|
||||
- Assess cognitive load and task completion efficiency
|
||||
- Analyze accessibility barriers and inclusive design gaps
|
||||
- Evaluate user satisfaction and Net Promoter Score trends
|
||||
Deliverables:
|
||||
- analysis.md: Main user researcher analysis
|
||||
- recommendations.md: User researcher recommendations
|
||||
- deliverables/: User researcher-specific outputs as defined in role template
|
||||
|
||||
4. User Segmentation and Personas
|
||||
- Define user segments based on behavior and needs
|
||||
- Create detailed user personas with goals and contexts
|
||||
- Map user scenarios and use case variations
|
||||
- Analyze demographic and psychographic factors
|
||||
- Identify key user archetypes and edge cases
|
||||
Embody user researcher role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
5. Research Methodology Design
|
||||
- Recommend appropriate research methods (qualitative/quantitative)
|
||||
- Design user interview guides and survey instruments
|
||||
- Plan usability testing scenarios and success metrics
|
||||
- Design A/B testing strategies for key hypotheses
|
||||
- Plan longitudinal research and continuous feedback loops
|
||||
|
||||
6. Insights Generation and Validation
|
||||
- Synthesize research findings into actionable insights
|
||||
- Identify opportunity areas and innovation potential
|
||||
- Validate assumptions and hypotheses with evidence
|
||||
- Prioritize insights based on business and user impact
|
||||
- Create research-backed design principles and guidelines
|
||||
|
||||
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
|
||||
- analysis.md (main user research analysis)
|
||||
- user-personas.md (detailed user personas and segments)
|
||||
- research-plan.md (methodology and research approach)
|
||||
- insights-recommendations.md (key findings and actionable recommendations)
|
||||
|
||||
Apply user research expertise to generate deep user understanding and actionable insights."
|
||||
### 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"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **输出结构**
|
||||
|
||||
Reference in New Issue
Block a user