mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-12 02:37:45 +08:00
refactor: Update brainstorming workflow roles and documentation
Major role restructuring to improve workflow efficiency and clarity: ## New Roles Added (4) - product-owner: Backlog management and user story definition - scrum-master: Sprint planning and agile process facilitation - ux-expert: User experience optimization and usability testing - subject-matter-expert: Domain expertise and industry standards ## Roles Removed (5) - business-analyst → functionality split to product-owner and scrum-master - feature-planner → merged into product-owner responsibilities - innovation-lead → integrated into subject-matter-expert - security-expert → integrated into subject-matter-expert - user-researcher → merged into ux-expert ## Files Updated ### Command Files (.claude/commands/workflow/brainstorm/) - Created: product-owner.md, scrum-master.md, ux-expert.md, subject-matter-expert.md - Deleted: business-analyst.md, feature-planner.md, innovation-lead.md, security-expert.md, user-researcher.md - Updated: artifacts.md, auto-parallel.md, auto-squeeze.md, synthesis.md ### Planning Templates (.claude/workflows/cli-templates/planning-roles/) - Created: product-owner.md, scrum-master.md, ux-expert.md, subject-matter-expert.md - Archived: Moved 5 deprecated roles to _deprecated/ with migration guide - Added: _deprecated/README.md with deprecation details and migration paths ### Agent Configurations - Updated conceptual-planning-agent.md with new role mappings - Updated action-planning-agent.md with new role references ### Documentation - Updated README.md brainstorming role tables and descriptions - Updated README_CN.md with Chinese translations for new roles - Updated workflow documentation files with new role references ## Breaking Changes Commands for removed roles are no longer available. Use replacement roles: - /workflow:brainstorm:business-analyst → use product-owner or scrum-master - /workflow:brainstorm:feature-planner → use product-owner - /workflow:brainstorm:innovation-lead → use subject-matter-expert - /workflow:brainstorm:security-expert → use subject-matter-expert - /workflow:brainstorm:user-researcher → use ux-expert 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
@@ -5,8 +5,8 @@ usage: /workflow:brainstorm:artifacts "<topic>" [--roles "role1,role2,role3"]
|
||||
argument-hint: "topic or challenge description for framework generation"
|
||||
examples:
|
||||
- /workflow:brainstorm:artifacts "Build real-time collaboration feature"
|
||||
- /workflow:brainstorm:artifacts "Optimize database performance" --roles "system-architect,data-architect,security-expert"
|
||||
- /workflow:brainstorm:artifacts "Implement secure authentication system" --roles "ui-designer,security-expert,user-researcher"
|
||||
- /workflow:brainstorm:artifacts "Optimize database performance" --roles "system-architect,data-architect,subject-matter-expert"
|
||||
- /workflow:brainstorm:artifacts "Implement secure authentication system" --roles "ui-designer,ux-expert,subject-matter-expert"
|
||||
allowed-tools: TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*)
|
||||
---
|
||||
|
||||
@@ -109,7 +109,7 @@ Framework content adapts based on `--roles` parameter:
|
||||
- **Scope**: [Topic boundaries relevant to selected roles]
|
||||
- **Objectives**: [Goals from perspective of selected roles]
|
||||
- **Context**: [Background focusing on role-specific concerns]
|
||||
- **Target Roles**: ui-designer, system-architect, security-expert
|
||||
- **Target Roles**: ui-designer, system-architect, subject-matter-expert
|
||||
|
||||
## Role-Specific Discussion Points
|
||||
|
||||
@@ -135,21 +135,21 @@ Framework content adapts based on `--roles` parameter:
|
||||
- What are the performance requirements?
|
||||
- What dependencies must be managed?
|
||||
|
||||
### For Security Expert
|
||||
1. **Security Requirements**
|
||||
- What are the key security concerns?
|
||||
- What threat vectors must be addressed?
|
||||
- What compliance requirements apply?
|
||||
### For Subject Matter Expert
|
||||
1. **Domain Expertise & Standards**
|
||||
- What industry standards and best practices apply?
|
||||
- What regulatory compliance requirements exist?
|
||||
- What domain-specific patterns should be followed?
|
||||
|
||||
2. **Security Implementation**
|
||||
- What authentication/authorization is needed?
|
||||
- What data protection mechanisms are required?
|
||||
- How to handle security incidents?
|
||||
2. **Technical Quality & Risk**
|
||||
- What technical debt considerations exist?
|
||||
- What scalability and maintenance implications apply?
|
||||
- What knowledge transfer and documentation is needed?
|
||||
|
||||
## Cross-Role Integration Points
|
||||
- How do UI decisions impact architecture?
|
||||
- How does architecture constrain UI possibilities?
|
||||
- What security requirements affect both UI and architecture?
|
||||
- What domain standards affect both UI and architecture?
|
||||
|
||||
## Framework Usage
|
||||
**For Role Agents**: Address your specific section + integration points
|
||||
@@ -157,7 +157,7 @@ Framework content adapts based on `--roles` parameter:
|
||||
**Update Process**: Use /workflow:brainstorm:artifacts to update
|
||||
|
||||
---
|
||||
*Generated for roles: ui-designer, system-architect, security-expert*
|
||||
*Generated for roles: ui-designer, system-architect, subject-matter-expert*
|
||||
*Last updated: [timestamp]*
|
||||
```
|
||||
|
||||
@@ -200,9 +200,9 @@ Framework content adapts based on `--roles` parameter:
|
||||
|
||||
## Available Role Perspectives
|
||||
Framework supports analysis from any of these roles:
|
||||
- system-architect, ui-designer, security-expert
|
||||
- user-researcher, product-manager, business-analyst
|
||||
- data-architect, innovation-lead, feature-planner
|
||||
- **Technical**: system-architect, data-architect, subject-matter-expert
|
||||
- **Product & Design**: ui-designer, ux-expert, product-manager, product-owner
|
||||
- **Agile & Quality**: scrum-master, test-strategist
|
||||
|
||||
---
|
||||
*Comprehensive framework - adaptable to any role*
|
||||
@@ -216,17 +216,17 @@ Framework supports analysis from any of these roles:
|
||||
**Technical Roles**:
|
||||
- `system-architect`: Architecture patterns, scalability, technology stack, integration
|
||||
- `data-architect`: Data modeling, processing workflows, analytics, storage
|
||||
- `security-expert`: Security requirements, threat modeling, compliance, protection
|
||||
- `subject-matter-expert`: Domain expertise, industry standards, compliance, best practices
|
||||
|
||||
**Product & Design Roles**:
|
||||
- `ui-designer`: User interface, visual design, interaction patterns, accessibility
|
||||
- `user-researcher`: User needs, behavior analysis, usability testing, personas
|
||||
- `ux-expert`: User experience optimization, usability testing, interaction design, design systems
|
||||
- `product-manager`: Business value, feature prioritization, market positioning, roadmap
|
||||
- `product-owner`: Backlog management, user stories, acceptance criteria, stakeholder alignment
|
||||
|
||||
**Business Roles**:
|
||||
- `business-analyst`: Process optimization, requirements analysis, cost-benefit, ROI
|
||||
- `innovation-lead`: Emerging technologies, competitive advantage, transformation, trends
|
||||
- `feature-planner`: Feature specification, user stories, acceptance criteria, dependencies
|
||||
**Agile & Quality Roles**:
|
||||
- `scrum-master`: Sprint planning, team dynamics, process optimization, delivery management
|
||||
- `test-strategist`: Testing strategies, quality assurance, test automation, validation approaches
|
||||
|
||||
### Dynamic Discussion Point Generation
|
||||
|
||||
@@ -248,23 +248,32 @@ Generate:
|
||||
|
||||
#### Example 1: Architecture-Heavy Topic
|
||||
```bash
|
||||
/workflow:brainstorm:artifacts "Design scalable microservices platform" --roles "system-architect,data-architect,security-expert"
|
||||
/workflow:brainstorm:artifacts "Design scalable microservices platform" --roles "system-architect,data-architect,subject-matter-expert"
|
||||
```
|
||||
**Generated framework focuses on**:
|
||||
- Service architecture and communication patterns
|
||||
- Data flow and storage strategies
|
||||
- Security boundaries and authentication
|
||||
- Domain standards and best practices
|
||||
|
||||
#### Example 2: User-Focused Topic
|
||||
```bash
|
||||
/workflow:brainstorm:artifacts "Improve user onboarding experience" --roles "ui-designer,user-researcher,product-manager"
|
||||
/workflow:brainstorm:artifacts "Improve user onboarding experience" --roles "ui-designer,ux-expert,product-manager"
|
||||
```
|
||||
**Generated framework focuses on**:
|
||||
- Onboarding flow and UI components
|
||||
- User behavior and pain points
|
||||
- User experience optimization and usability
|
||||
- Business value and success metrics
|
||||
|
||||
#### Example 3: Comprehensive Analysis
|
||||
#### Example 3: Agile Delivery Topic
|
||||
```bash
|
||||
/workflow:brainstorm:artifacts "Optimize sprint delivery process" --roles "scrum-master,product-owner,test-strategist"
|
||||
```
|
||||
**Generated framework focuses on**:
|
||||
- Sprint planning and team collaboration
|
||||
- Backlog management and prioritization
|
||||
- Quality assurance and testing strategies
|
||||
|
||||
#### Example 4: Comprehensive Analysis
|
||||
```bash
|
||||
/workflow:brainstorm:artifacts "Build real-time collaboration feature"
|
||||
```
|
||||
|
||||
@@ -18,15 +18,17 @@ allowed-tools: SlashCommand(*), Task(*), TodoWrite(*), Read(*), Write(*), Bash(*
|
||||
```
|
||||
|
||||
## Role Selection Logic
|
||||
- **Technical & Architecture**: `architecture|system|performance|database|security` → system-architect, data-architect, security-expert
|
||||
- **Product & UX**: `user|ui|ux|interface|design|product|feature` → ui-designer, user-researcher, product-manager
|
||||
- **Technical & Architecture**: `architecture|system|performance|database|security` → system-architect, data-architect, security-expert, subject-matter-expert
|
||||
- **Product & UX**: `user|ui|ux|interface|design|product|feature|experience` → ui-designer, user-researcher, product-manager, ux-expert, product-owner
|
||||
- **Business & Process**: `business|process|workflow|cost|innovation|testing` → business-analyst, innovation-lead, test-strategist
|
||||
- **Agile & Delivery**: `agile|sprint|scrum|team|collaboration|delivery` → scrum-master, product-owner
|
||||
- **Domain Expertise**: `domain|standard|compliance|expertise|regulation` → subject-matter-expert
|
||||
- **Multi-role**: Complex topics automatically select 2-3 complementary roles
|
||||
- **Default**: `product-manager` if no clear match
|
||||
|
||||
**Template Loading**: `bash($(cat "~/.claude/workflows/cli-templates/planning-roles/<role-name>.md"))`
|
||||
**Template Source**: `.claude/workflows/cli-templates/planning-roles/`
|
||||
**Available Roles**: business-analyst, data-architect, feature-planner, innovation-lead, product-manager, security-expert, system-architect, test-strategist, ui-designer, user-researcher
|
||||
**Available Roles**: data-architect, product-manager, product-owner, scrum-master, subject-matter-expert, system-architect, test-strategist, ui-designer, ux-expert
|
||||
|
||||
**Example**:
|
||||
```bash
|
||||
@@ -72,9 +74,10 @@ Auto command coordinates independent specialized commands:
|
||||
4. **Command coordination**: SlashCommand handles execution and validation
|
||||
|
||||
**Role Selection Logic**:
|
||||
- **Technical**: `architecture|system|performance|database|security` → system-architect, data-architect, security-expert
|
||||
- **Product & UX**: `user|ui|ux|interface|design|product|feature` → ui-designer, user-researcher, product-manager
|
||||
- **Business**: `business|process|workflow|cost|innovation` → business-analyst, innovation-lead
|
||||
- **Technical**: `architecture|system|performance|database` → system-architect, data-architect, subject-matter-expert
|
||||
- **Product & UX**: `user|ui|ux|interface|design|product|feature|experience` → ui-designer, ux-expert, product-manager, product-owner
|
||||
- **Agile & Delivery**: `agile|sprint|scrum|team|collaboration|delivery` → scrum-master, product-owner
|
||||
- **Domain Expertise**: `domain|standard|compliance|expertise|regulation` → subject-matter-expert
|
||||
- **Auto-select**: 2-3 most relevant roles based on topic analysis
|
||||
|
||||
### Simplified Processing Standards
|
||||
|
||||
@@ -61,16 +61,16 @@ Use keyword analysis to auto-select 2-3 roles:
|
||||
|
||||
**Role Selection Logic**:
|
||||
- **Technical/Architecture keywords**: `architecture|system|performance|database|api|backend|scalability`
|
||||
→ system-architect, data-architect, security-expert
|
||||
→ system-architect, data-architect, subject-matter-expert
|
||||
- **UI/UX keywords**: `user|ui|ux|interface|design|frontend|experience`
|
||||
→ ui-designer, user-researcher
|
||||
→ ui-designer, ux-expert
|
||||
- **Product/Business keywords**: `product|feature|business|workflow|process|customer`
|
||||
→ product-manager, business-analyst
|
||||
- **Security keywords**: `security|auth|permission|encryption|compliance`
|
||||
→ security-expert
|
||||
- **Innovation keywords**: `innovation|new|disrupt|transform|emerging`
|
||||
→ innovation-lead
|
||||
- **Default**: ui-designer (if no clear match)
|
||||
→ product-manager, product-owner
|
||||
- **Agile/Delivery keywords**: `agile|sprint|scrum|team|collaboration|delivery`
|
||||
→ scrum-master, product-owner
|
||||
- **Domain Expertise keywords**: `domain|standard|compliance|expertise|regulation`
|
||||
→ subject-matter-expert
|
||||
- **Default**: product-manager (if no clear match)
|
||||
|
||||
**Selection Rules**:
|
||||
- Maximum 3 roles
|
||||
@@ -91,14 +91,14 @@ Execute each selected role command one by one:
|
||||
|
||||
**Commands**:
|
||||
- `SlashCommand(command="/workflow:brainstorm:ui-designer")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:ux-expert")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:system-architect")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:security-expert")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:user-researcher")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:product-manager")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:business-analyst")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:data-architect")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:innovation-lead")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:feature-planner")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:product-manager")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:product-owner")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:scrum-master")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:subject-matter-expert")`
|
||||
- `SlashCommand(command="/workflow:brainstorm:test-strategist")`
|
||||
|
||||
**Validation** (after each role):
|
||||
- File `.workflow/[session]/.brainstorming/[role]/analysis.md` exists
|
||||
@@ -202,8 +202,8 @@ Return summary to user
|
||||
**Keywords detected**: user, interface, design
|
||||
**Selected roles**:
|
||||
- ui-designer (primary: UI/UX match)
|
||||
- user-researcher (secondary: user experience)
|
||||
- security-expert (complementary: auth security)
|
||||
- ux-expert (secondary: user experience)
|
||||
- subject-matter-expert (complementary: auth standards)
|
||||
|
||||
### Example 2: Architecture Topic
|
||||
**Topic**: "Design scalable microservices architecture"
|
||||
@@ -211,15 +211,15 @@ Return summary to user
|
||||
**Selected roles**:
|
||||
- system-architect (primary: architecture match)
|
||||
- data-architect (secondary: scalability/data)
|
||||
- security-expert (complementary: system security)
|
||||
- subject-matter-expert (complementary: domain expertise)
|
||||
|
||||
### Example 3: Business Process Topic
|
||||
**Topic**: "Optimize customer onboarding workflow"
|
||||
**Keywords detected**: workflow, process, customer
|
||||
### Example 3: Agile Delivery Topic
|
||||
**Topic**: "Optimize team sprint planning and delivery process"
|
||||
**Keywords detected**: sprint, team, delivery, process
|
||||
**Selected roles**:
|
||||
- business-analyst (primary: process match)
|
||||
- product-manager (secondary: customer focus)
|
||||
- ui-designer (complementary: user experience)
|
||||
- scrum-master (primary: agile process match)
|
||||
- product-owner (secondary: backlog/delivery focus)
|
||||
- product-manager (complementary: product strategy)
|
||||
|
||||
## Error Handling
|
||||
|
||||
|
||||
@@ -1,254 +0,0 @@
|
||||
---
|
||||
name: innovation-lead
|
||||
description: Generate or update innovation-lead/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:innovation-lead [topic]
|
||||
argument-hint: "optional topic - uses existing framework if available"
|
||||
examples:
|
||||
- /workflow:brainstorm:innovation-lead
|
||||
- /workflow:brainstorm:innovation-lead "AI integration opportunities"
|
||||
- /workflow:brainstorm:innovation-lead "future technology trends"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
|
||||
---
|
||||
|
||||
## 🚀 **Role Overview: Innovation Lead**
|
||||
|
||||
### Role Definition
|
||||
Visionary technology strategist responsible for identifying emerging technology trends, evaluating disruptive innovation opportunities, and designing future-ready solutions that create competitive advantage and drive market transformation.
|
||||
|
||||
### Core Responsibilities
|
||||
- **Trend Identification**: Identify and analyze emerging technology trends and market opportunities
|
||||
- **Innovation Strategy**: Develop innovation roadmaps and technology development strategies
|
||||
- **Technology Assessment**: Evaluate new technology application potential and feasibility
|
||||
- **Future Planning**: Design forward-looking product and service concepts
|
||||
|
||||
### Focus Areas
|
||||
- **Emerging Technologies**: AI, blockchain, IoT, AR/VR, quantum computing, and other frontier technologies
|
||||
- **Market Trends**: Industry transformation, user behavior evolution, business model innovation
|
||||
- **Innovation Opportunities**: Disruptive innovation, blue ocean markets, technology convergence opportunities
|
||||
- **Future Vision**: Long-term technology roadmaps, proof of concepts, prototype development
|
||||
|
||||
### Success Metrics
|
||||
- Innovation impact and market differentiation
|
||||
- Technology adoption rates and competitive advantage
|
||||
- Future readiness and strategic positioning
|
||||
- Breakthrough opportunity identification and validation
|
||||
|
||||
## 🧠 **Analysis Framework**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
**1. Emerging Trends and Technology Opportunities**
|
||||
- Which emerging technologies will have the greatest impact on our industry?
|
||||
- What is the technology maturity level and adoption timeline?
|
||||
- What new opportunities does technology convergence create?
|
||||
|
||||
**2. Disruption Potential and Innovation Assessment**
|
||||
- What is the potential for disruptive innovation and its impact?
|
||||
- What innovation opportunities exist within current solutions?
|
||||
- What unmet market needs and demands exist?
|
||||
|
||||
**3. Competitive Advantage and Market Analysis**
|
||||
- What are competitors' innovation strategies and directions?
|
||||
- What market gaps and blue ocean opportunities exist?
|
||||
- What technological barriers and first-mover advantages are available?
|
||||
|
||||
**4. Implementation and Risk Assessment**
|
||||
- What is the feasibility and risk of technology implementation?
|
||||
- What are the investment requirements and expected returns?
|
||||
- What organizational innovation capabilities and adaptability are needed?
|
||||
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Check for active sessions
|
||||
active_sessions=$(find .workflow -name ".active-*" 2>/dev/null)
|
||||
if [ multiple_sessions ]; then
|
||||
prompt_user_to_select_session()
|
||||
else
|
||||
use_existing_or_create_new()
|
||||
fi
|
||||
```
|
||||
|
||||
### Step 1: Context Gathering Phase
|
||||
**Innovation Lead Perspective Questioning**
|
||||
|
||||
Before agent assignment, gather comprehensive innovation lead context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
|
||||
**1. Emerging Trends and Future Technologies**
|
||||
- What emerging technologies or trends do you think will be most relevant to this topic?
|
||||
- Are there any specific industries or markets you want to explore for innovation opportunities?
|
||||
- What time horizon are you considering (near-term, medium-term, long-term disruption)?
|
||||
- Are there any particular technology domains you want to focus on (AI, IoT, blockchain, etc.)?
|
||||
|
||||
**2. Innovation Opportunities and Market Potential**
|
||||
- What current limitations or pain points could be addressed through innovation?
|
||||
- Are there any unmet market needs or underserved segments you're aware of?
|
||||
- What would disruptive success look like in this context?
|
||||
- Are there cross-industry innovations that could be applied to this domain?
|
||||
|
||||
**3. Disruption Potential and Competitive Landscape**
|
||||
- Who are the current market leaders and what are their innovation strategies?
|
||||
- What startup activity or venture capital investment trends are you seeing?
|
||||
- Are there any potential platform shifts or ecosystem changes on the horizon?
|
||||
- What would make a solution truly differentiated in the marketplace?
|
||||
|
||||
**4. Implementation and Strategic Considerations**
|
||||
- What organizational capabilities or partnerships would be needed for innovation?
|
||||
- Are there regulatory, technical, or market barriers to consider?
|
||||
- What level of risk tolerance exists for breakthrough vs. incremental innovation?
|
||||
- How important is first-mover advantage versus fast-follower strategies?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/innovation-lead-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute dedicated innovation lead conceptual analysis for: {topic}
|
||||
|
||||
ASSIGNED_ROLE: innovation-lead
|
||||
OUTPUT_LOCATION: .brainstorming/innovation-lead/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load innovation-lead planning template\",
|
||||
\"command\": \"bash($(cat ~/.claude/workflows/cli-templates/planning-roles/innovation-lead.md))\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply innovation lead perspective to topic analysis
|
||||
- Focus on emerging trends, disruption potential, competitive advantage, and future opportunities
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
Deliverables:
|
||||
- analysis.md: Main innovation lead analysis
|
||||
- recommendations.md: Innovation lead recommendations
|
||||
- deliverables/: Innovation lead-specific outputs as defined in role template
|
||||
|
||||
Embody innovation lead role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather innovation lead context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to innovation-lead-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load innovation-lead planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for innovation-lead role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📋 **TodoWrite Integration**
|
||||
|
||||
### Workflow Progress Tracking
|
||||
```javascript
|
||||
TodoWrite({
|
||||
todos: [
|
||||
{
|
||||
content: "Detect active session and locate topic framework",
|
||||
status: "in_progress",
|
||||
activeForm: "Detecting session and framework"
|
||||
},
|
||||
{
|
||||
content: "Load topic-framework.md and session metadata for context",
|
||||
status: "pending",
|
||||
activeForm: "Loading framework and session context"
|
||||
},
|
||||
{
|
||||
content: "Execute innovation-lead analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
status: "pending",
|
||||
activeForm: "Executing innovation-lead framework analysis"
|
||||
},
|
||||
{
|
||||
content: "Generate analysis.md addressing all framework discussion points",
|
||||
status: "pending",
|
||||
activeForm: "Generating structured innovation-lead analysis"
|
||||
},
|
||||
{
|
||||
content: "Update session.json with innovation-lead completion status",
|
||||
status: "pending",
|
||||
activeForm: "Updating session metadata"
|
||||
}
|
||||
]
|
||||
});
|
||||
```
|
||||
|
||||
## 📊 **Output Structure**
|
||||
|
||||
### Framework-Based Analysis
|
||||
```
|
||||
.workflow/WFS-{session}/.brainstorming/innovation-lead/
|
||||
└── analysis.md # Structured analysis addressing topic-framework.md discussion points
|
||||
```
|
||||
|
||||
### Analysis Document Structure
|
||||
```markdown
|
||||
# Innovation Lead Analysis: [Topic from Framework]
|
||||
|
||||
## Framework Reference
|
||||
**Topic Framework**: @../topic-framework.md
|
||||
**Role Focus**: Innovation and Emerging Technology perspective
|
||||
|
||||
## Discussion Points Analysis
|
||||
[Address each point from topic-framework.md with innovation expertise]
|
||||
|
||||
### Core Requirements (from framework)
|
||||
[Innovation perspective on emerging technology requirements]
|
||||
|
||||
### Technical Considerations (from framework)
|
||||
[Future technology and breakthrough considerations]
|
||||
|
||||
### User Experience Factors (from framework)
|
||||
[Future user behavior and interaction trends]
|
||||
|
||||
### Implementation Challenges (from framework)
|
||||
[Innovation implementation and market adoption considerations]
|
||||
|
||||
### Success Metrics (from framework)
|
||||
[Innovation success metrics and breakthrough criteria]
|
||||
|
||||
## Innovation Specific Recommendations
|
||||
[Role-specific innovation opportunities and breakthrough concepts]
|
||||
|
||||
---
|
||||
*Generated by innovation-lead analysis addressing structured framework*
|
||||
```
|
||||
|
||||
## 🔄 **Session Integration**
|
||||
|
||||
### Completion Status Update
|
||||
```json
|
||||
{
|
||||
"innovation_lead": {
|
||||
"status": "completed",
|
||||
"framework_addressed": true,
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/innovation-lead/analysis.md",
|
||||
"framework_reference": "@../topic-framework.md"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Integration Points
|
||||
- **Framework Reference**: @../topic-framework.md for structured discussion points
|
||||
- **Cross-Role Synthesis**: Innovation insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
@@ -1,31 +1,31 @@
|
||||
---
|
||||
name: business-analyst
|
||||
description: Generate or update business-analyst/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:business-analyst [topic]
|
||||
name: product-owner
|
||||
description: Generate or update product-owner/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:product-owner [topic]
|
||||
argument-hint: "optional topic - uses existing framework if available"
|
||||
examples:
|
||||
- /workflow:brainstorm:business-analyst
|
||||
- /workflow:brainstorm:business-analyst "workflow automation opportunities"
|
||||
- /workflow:brainstorm:business-analyst "business process optimization"
|
||||
- /workflow:brainstorm:product-owner
|
||||
- /workflow:brainstorm:product-owner "user authentication redesign"
|
||||
- /workflow:brainstorm:product-owner "mobile app performance optimization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
|
||||
---
|
||||
|
||||
## 📊 **Business Analyst Analysis Generator**
|
||||
## 🎯 **Product Owner Analysis Generator**
|
||||
|
||||
### Purpose
|
||||
**Specialized command for generating business-analyst/analysis.md** that addresses topic-framework.md discussion points from business analysis perspective. Creates or updates role-specific analysis with framework references.
|
||||
**Specialized command for generating product-owner/analysis.md** that addresses topic-framework.md discussion points from product backlog and feature prioritization perspective. Creates or updates role-specific analysis with framework references.
|
||||
|
||||
### Core Function
|
||||
- **Framework-based Analysis**: Address each discussion point in topic-framework.md
|
||||
- **Business Analysis Focus**: Process optimization, requirements analysis, and business efficiency perspective
|
||||
- **Product Backlog Focus**: Feature prioritization, user stories, and acceptance criteria
|
||||
- **Update Mechanism**: Create new or update existing analysis.md
|
||||
- **Agent Delegation**: Use conceptual-planning-agent for analysis generation
|
||||
|
||||
### Analysis Scope
|
||||
- **Process Analysis**: Analyze existing business processes for efficiency and improvement opportunities
|
||||
- **Requirements Analysis**: Identify and define business requirements and functional specifications
|
||||
- **Value Analysis**: Assess cost-benefit and ROI of business initiatives
|
||||
- **Change Management**: Plan organizational change and process transformation
|
||||
- **Backlog Management**: User story creation, refinement, and prioritization
|
||||
- **Stakeholder Alignment**: Requirements gathering, value definition, and expectation management
|
||||
- **Feature Prioritization**: ROI analysis, MoSCoW method, and value-driven delivery
|
||||
- **Acceptance Criteria**: Definition of Done, acceptance testing, and quality standards
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
|
||||
@@ -68,11 +68,11 @@ ELSE:
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute business-analyst analysis for existing topic framework
|
||||
Execute product-owner analysis for existing topic framework
|
||||
|
||||
## Context Loading
|
||||
ASSIGNED_ROLE: business-analyst
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/business-analyst/
|
||||
ASSIGNED_ROLE: product-owner
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/product-owner/
|
||||
ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
|
||||
## Flow Control Steps
|
||||
@@ -82,8 +82,8 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
- Output: topic_framework_content
|
||||
|
||||
2. **load_role_template**
|
||||
- Action: Load business-analyst planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/business-analyst.md))
|
||||
- Action: Load product-owner planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/product-owner.md))
|
||||
- Output: role_template_guidelines
|
||||
|
||||
3. **load_session_metadata**
|
||||
@@ -92,19 +92,19 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
- Output: session_context
|
||||
|
||||
## Analysis Requirements
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from business analysis perspective
|
||||
**Role Focus**: Process optimization, requirements analysis, business efficiency
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from product backlog and feature prioritization perspective
|
||||
**Role Focus**: Backlog management, stakeholder alignment, feature prioritization, acceptance criteria
|
||||
**Structured Approach**: Create analysis.md addressing framework discussion points
|
||||
**Template Integration**: Apply role template guidelines within framework structure
|
||||
|
||||
## Expected Deliverables
|
||||
1. **analysis.md**: Comprehensive business analysis addressing all framework discussion points
|
||||
1. **analysis.md**: Comprehensive product ownership analysis addressing all framework discussion points
|
||||
2. **Framework Reference**: Include @../topic-framework.md reference in analysis
|
||||
|
||||
## Completion Criteria
|
||||
- Address each discussion point from topic-framework.md with business analysis expertise
|
||||
- Provide process optimization recommendations and requirements specifications
|
||||
- Include cost-benefit analysis and change management considerations
|
||||
- Address each discussion point from topic-framework.md with product ownership expertise
|
||||
- Provide actionable user stories and acceptance criteria definitions
|
||||
- Include feature prioritization and stakeholder alignment strategies
|
||||
- Reference framework document using @ notation for integration
|
||||
"
|
||||
```
|
||||
@@ -126,17 +126,17 @@ TodoWrite({
|
||||
activeForm: "Loading framework and session context"
|
||||
},
|
||||
{
|
||||
content: "Execute business-analyst analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
content: "Execute product-owner analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
status: "pending",
|
||||
activeForm: "Executing business-analyst framework analysis"
|
||||
activeForm: "Executing product-owner framework analysis"
|
||||
},
|
||||
{
|
||||
content: "Generate analysis.md addressing all framework discussion points",
|
||||
status: "pending",
|
||||
activeForm: "Generating structured business-analyst analysis"
|
||||
activeForm: "Generating structured product-owner analysis"
|
||||
},
|
||||
{
|
||||
content: "Update session.json with business-analyst completion status",
|
||||
content: "Update session.json with product-owner completion status",
|
||||
status: "pending",
|
||||
activeForm: "Updating session metadata"
|
||||
}
|
||||
@@ -148,41 +148,41 @@ TodoWrite({
|
||||
|
||||
### Framework-Based Analysis
|
||||
```
|
||||
.workflow/WFS-{session}/.brainstorming/business-analyst/
|
||||
.workflow/WFS-{session}/.brainstorming/product-owner/
|
||||
└── analysis.md # Structured analysis addressing topic-framework.md discussion points
|
||||
```
|
||||
|
||||
### Analysis Document Structure
|
||||
```markdown
|
||||
# Business Analyst Analysis: [Topic from Framework]
|
||||
# Product Owner Analysis: [Topic from Framework]
|
||||
|
||||
## Framework Reference
|
||||
**Topic Framework**: @../topic-framework.md
|
||||
**Role Focus**: Business Analysis perspective
|
||||
**Role Focus**: Product Backlog & Feature Prioritization perspective
|
||||
|
||||
## Discussion Points Analysis
|
||||
[Address each point from topic-framework.md with business analysis expertise]
|
||||
[Address each point from topic-framework.md with product ownership expertise]
|
||||
|
||||
### Core Requirements (from framework)
|
||||
[Business analysis perspective on requirements]
|
||||
[User story formulation and backlog refinement perspective]
|
||||
|
||||
### Technical Considerations (from framework)
|
||||
[Business process and workflow considerations]
|
||||
[Technical feasibility and implementation sequencing considerations]
|
||||
|
||||
### User Experience Factors (from framework)
|
||||
[Business user experience and stakeholder considerations]
|
||||
[User value definition and acceptance criteria analysis]
|
||||
|
||||
### Implementation Challenges (from framework)
|
||||
[Change management and process transformation challenges]
|
||||
[Sprint planning, dependency management, and delivery strategies]
|
||||
|
||||
### Success Metrics (from framework)
|
||||
[Business success metrics and performance indicators]
|
||||
[Feature adoption, value delivery metrics, and stakeholder satisfaction indicators]
|
||||
|
||||
## Business Analysis Specific Recommendations
|
||||
[Role-specific business process recommendations and solutions]
|
||||
## Product Owner Specific Recommendations
|
||||
[Role-specific backlog management and feature prioritization strategies]
|
||||
|
||||
---
|
||||
*Generated by business-analyst analysis addressing structured framework*
|
||||
*Generated by product-owner analysis addressing structured framework*
|
||||
```
|
||||
|
||||
## 🔄 **Session Integration**
|
||||
@@ -190,10 +190,10 @@ TodoWrite({
|
||||
### Completion Status Update
|
||||
```json
|
||||
{
|
||||
"business_analyst": {
|
||||
"product_owner": {
|
||||
"status": "completed",
|
||||
"framework_addressed": true,
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/business-analyst/analysis.md",
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/product-owner/analysis.md",
|
||||
"framework_reference": "@../topic-framework.md"
|
||||
}
|
||||
}
|
||||
@@ -201,5 +201,5 @@ TodoWrite({
|
||||
|
||||
### Integration Points
|
||||
- **Framework Reference**: @../topic-framework.md for structured discussion points
|
||||
- **Cross-Role Synthesis**: Business analysis insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
- **Cross-Role Synthesis**: Product ownership insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
@@ -1,31 +1,31 @@
|
||||
---
|
||||
name: security-expert
|
||||
description: Generate or update security-expert/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:security-expert [topic]
|
||||
name: scrum-master
|
||||
description: Generate or update scrum-master/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:scrum-master [topic]
|
||||
argument-hint: "optional topic - uses existing framework if available"
|
||||
examples:
|
||||
- /workflow:brainstorm:security-expert
|
||||
- /workflow:brainstorm:security-expert "user authentication security review"
|
||||
- /workflow:brainstorm:security-expert "API security architecture"
|
||||
- /workflow:brainstorm:scrum-master
|
||||
- /workflow:brainstorm:scrum-master "user authentication redesign"
|
||||
- /workflow:brainstorm:scrum-master "mobile app performance optimization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
|
||||
---
|
||||
|
||||
## 🔒 **Security Expert Analysis Generator**
|
||||
## 🎯 **Scrum Master Analysis Generator**
|
||||
|
||||
### Purpose
|
||||
**Specialized command for generating security-expert/analysis.md** that addresses topic-framework.md discussion points from cybersecurity perspective. Creates or updates role-specific analysis with framework references.
|
||||
**Specialized command for generating scrum-master/analysis.md** that addresses topic-framework.md discussion points from agile process and team collaboration perspective. Creates or updates role-specific analysis with framework references.
|
||||
|
||||
### Core Function
|
||||
- **Framework-based Analysis**: Address each discussion point in topic-framework.md
|
||||
- **Cybersecurity Focus**: Threat modeling, security architecture, and risk management
|
||||
- **Agile Process Focus**: Sprint planning, team dynamics, and delivery optimization
|
||||
- **Update Mechanism**: Create new or update existing analysis.md
|
||||
- **Agent Delegation**: Use conceptual-planning-agent for analysis generation
|
||||
|
||||
### Analysis Scope
|
||||
- **Threat Modeling**: Attack vectors, threat actors, and vulnerability assessment
|
||||
- **Security Architecture**: Controls, defensive measures, and compliance
|
||||
- **Risk Management**: Risk assessment, mitigation, and security policies
|
||||
- **Implementation Security**: Integration, monitoring, and incident response
|
||||
- **Sprint Planning**: Task breakdown, estimation, and iteration planning
|
||||
- **Team Collaboration**: Communication patterns, impediment removal, and facilitation
|
||||
- **Process Optimization**: Agile ceremonies, retrospectives, and continuous improvement
|
||||
- **Delivery Management**: Velocity tracking, burndown analysis, and release planning
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
|
||||
@@ -68,11 +68,11 @@ ELSE:
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute security-expert analysis for existing topic framework
|
||||
Execute scrum-master analysis for existing topic framework
|
||||
|
||||
## Context Loading
|
||||
ASSIGNED_ROLE: security-expert
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/security-expert/
|
||||
ASSIGNED_ROLE: scrum-master
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/scrum-master/
|
||||
ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
|
||||
## Flow Control Steps
|
||||
@@ -82,8 +82,8 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
- Output: topic_framework_content
|
||||
|
||||
2. **load_role_template**
|
||||
- Action: Load security-expert planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/security-expert.md))
|
||||
- Action: Load scrum-master planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/scrum-master.md))
|
||||
- Output: role_template_guidelines
|
||||
|
||||
3. **load_session_metadata**
|
||||
@@ -92,19 +92,19 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
- Output: session_context
|
||||
|
||||
## Analysis Requirements
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from cybersecurity perspective
|
||||
**Role Focus**: Threat modeling, security architecture, risk management, compliance
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from agile process and team collaboration perspective
|
||||
**Role Focus**: Sprint planning, team dynamics, process optimization, delivery management
|
||||
**Structured Approach**: Create analysis.md addressing framework discussion points
|
||||
**Template Integration**: Apply role template guidelines within framework structure
|
||||
|
||||
## Expected Deliverables
|
||||
1. **analysis.md**: Comprehensive security analysis addressing all framework discussion points
|
||||
1. **analysis.md**: Comprehensive agile process analysis addressing all framework discussion points
|
||||
2. **Framework Reference**: Include @../topic-framework.md reference in analysis
|
||||
|
||||
## Completion Criteria
|
||||
- Address each discussion point from topic-framework.md with cybersecurity expertise
|
||||
- Provide actionable security controls and threat mitigation strategies
|
||||
- Include compliance requirements and risk assessment insights
|
||||
- Address each discussion point from topic-framework.md with scrum mastery expertise
|
||||
- Provide actionable sprint planning and team facilitation strategies
|
||||
- Include process optimization and impediment removal insights
|
||||
- Reference framework document using @ notation for integration
|
||||
"
|
||||
```
|
||||
@@ -126,17 +126,17 @@ TodoWrite({
|
||||
activeForm: "Loading framework and session context"
|
||||
},
|
||||
{
|
||||
content: "Execute security-expert analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
content: "Execute scrum-master analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
status: "pending",
|
||||
activeForm: "Executing security-expert framework analysis"
|
||||
activeForm: "Executing scrum-master framework analysis"
|
||||
},
|
||||
{
|
||||
content: "Generate analysis.md addressing all framework discussion points",
|
||||
status: "pending",
|
||||
activeForm: "Generating structured security-expert analysis"
|
||||
activeForm: "Generating structured scrum-master analysis"
|
||||
},
|
||||
{
|
||||
content: "Update session.json with security-expert completion status",
|
||||
content: "Update session.json with scrum-master completion status",
|
||||
status: "pending",
|
||||
activeForm: "Updating session metadata"
|
||||
}
|
||||
@@ -148,41 +148,41 @@ TodoWrite({
|
||||
|
||||
### Framework-Based Analysis
|
||||
```
|
||||
.workflow/WFS-{session}/.brainstorming/security-expert/
|
||||
.workflow/WFS-{session}/.brainstorming/scrum-master/
|
||||
└── analysis.md # Structured analysis addressing topic-framework.md discussion points
|
||||
```
|
||||
|
||||
### Analysis Document Structure
|
||||
```markdown
|
||||
# Security Expert Analysis: [Topic from Framework]
|
||||
# Scrum Master Analysis: [Topic from Framework]
|
||||
|
||||
## Framework Reference
|
||||
**Topic Framework**: @../topic-framework.md
|
||||
**Role Focus**: Cybersecurity perspective
|
||||
**Role Focus**: Agile Process & Team Collaboration perspective
|
||||
|
||||
## Discussion Points Analysis
|
||||
[Address each point from topic-framework.md with cybersecurity expertise]
|
||||
[Address each point from topic-framework.md with scrum mastery expertise]
|
||||
|
||||
### Core Requirements (from framework)
|
||||
[Security perspective on threat modeling and protection requirements]
|
||||
[Sprint planning and iteration breakdown perspective]
|
||||
|
||||
### Technical Considerations (from framework)
|
||||
[Security architecture and technical control considerations]
|
||||
[Technical debt management and process considerations]
|
||||
|
||||
### User Experience Factors (from framework)
|
||||
[Security usability and user protection considerations]
|
||||
[User story refinement and acceptance criteria analysis]
|
||||
|
||||
### Implementation Challenges (from framework)
|
||||
[Security implementation and compliance considerations]
|
||||
[Impediment identification and removal strategies]
|
||||
|
||||
### Success Metrics (from framework)
|
||||
[Security success metrics and risk management criteria]
|
||||
[Velocity tracking, burndown metrics, and team performance indicators]
|
||||
|
||||
## Cybersecurity Specific Recommendations
|
||||
[Role-specific security controls and threat mitigation strategies]
|
||||
## Scrum Master Specific Recommendations
|
||||
[Role-specific agile process optimization and team facilitation strategies]
|
||||
|
||||
---
|
||||
*Generated by security-expert analysis addressing structured framework*
|
||||
*Generated by scrum-master analysis addressing structured framework*
|
||||
```
|
||||
|
||||
## 🔄 **Session Integration**
|
||||
@@ -190,10 +190,10 @@ TodoWrite({
|
||||
### Completion Status Update
|
||||
```json
|
||||
{
|
||||
"security_expert": {
|
||||
"scrum_master": {
|
||||
"status": "completed",
|
||||
"framework_addressed": true,
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/security-expert/analysis.md",
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/scrum-master/analysis.md",
|
||||
"framework_reference": "@../topic-framework.md"
|
||||
}
|
||||
}
|
||||
@@ -201,5 +201,5 @@ TodoWrite({
|
||||
|
||||
### Integration Points
|
||||
- **Framework Reference**: @../topic-framework.md for structured discussion points
|
||||
- **Cross-Role Synthesis**: Security insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
- **Cross-Role Synthesis**: Agile process insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
205
.claude/commands/workflow/brainstorm/subject-matter-expert.md
Normal file
205
.claude/commands/workflow/brainstorm/subject-matter-expert.md
Normal file
@@ -0,0 +1,205 @@
|
||||
---
|
||||
name: subject-matter-expert
|
||||
description: Generate or update subject-matter-expert/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:subject-matter-expert [topic]
|
||||
argument-hint: "optional topic - uses existing framework if available"
|
||||
examples:
|
||||
- /workflow:brainstorm:subject-matter-expert
|
||||
- /workflow:brainstorm:subject-matter-expert "user authentication redesign"
|
||||
- /workflow:brainstorm:subject-matter-expert "mobile app performance optimization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
|
||||
---
|
||||
|
||||
## 🎯 **Subject Matter Expert Analysis Generator**
|
||||
|
||||
### Purpose
|
||||
**Specialized command for generating subject-matter-expert/analysis.md** that addresses topic-framework.md discussion points from domain knowledge and technical expertise perspective. Creates or updates role-specific analysis with framework references.
|
||||
|
||||
### Core Function
|
||||
- **Framework-based Analysis**: Address each discussion point in topic-framework.md
|
||||
- **Domain Expertise Focus**: Deep technical knowledge, industry standards, and best practices
|
||||
- **Update Mechanism**: Create new or update existing analysis.md
|
||||
- **Agent Delegation**: Use conceptual-planning-agent for analysis generation
|
||||
|
||||
### Analysis Scope
|
||||
- **Domain Knowledge**: Industry-specific expertise, regulatory requirements, and compliance
|
||||
- **Technical Standards**: Best practices, design patterns, and architectural guidelines
|
||||
- **Risk Assessment**: Technical debt, scalability concerns, and maintenance implications
|
||||
- **Knowledge Transfer**: Documentation strategies, training requirements, and expertise sharing
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
|
||||
### Phase 1: Session & Framework Detection
|
||||
```bash
|
||||
# Check active session and framework
|
||||
CHECK: .workflow/.active-* marker files
|
||||
IF active_session EXISTS:
|
||||
session_id = get_active_session()
|
||||
brainstorm_dir = .workflow/WFS-{session}/.brainstorming/
|
||||
|
||||
CHECK: brainstorm_dir/topic-framework.md
|
||||
IF EXISTS:
|
||||
framework_mode = true
|
||||
load_framework = true
|
||||
ELSE:
|
||||
IF topic_provided:
|
||||
framework_mode = false # Create analysis without framework
|
||||
ELSE:
|
||||
ERROR: "No framework found and no topic provided"
|
||||
```
|
||||
|
||||
### Phase 2: Analysis Mode Detection
|
||||
```bash
|
||||
# Determine execution mode
|
||||
IF framework_mode == true:
|
||||
mode = "framework_based_analysis"
|
||||
topic_ref = load_framework_topic()
|
||||
discussion_points = extract_framework_points()
|
||||
ELSE:
|
||||
mode = "standalone_analysis"
|
||||
topic_ref = provided_topic
|
||||
discussion_points = generate_basic_structure()
|
||||
```
|
||||
|
||||
### Phase 3: Agent Execution with Flow Control
|
||||
**Framework-Based Analysis Generation**
|
||||
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute subject-matter-expert analysis for existing topic framework
|
||||
|
||||
## Context Loading
|
||||
ASSIGNED_ROLE: subject-matter-expert
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/subject-matter-expert/
|
||||
ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
|
||||
## Flow Control Steps
|
||||
1. **load_topic_framework**
|
||||
- Action: Load structured topic discussion framework
|
||||
- Command: Read(.workflow/WFS-{session}/.brainstorming/topic-framework.md)
|
||||
- Output: topic_framework_content
|
||||
|
||||
2. **load_role_template**
|
||||
- Action: Load subject-matter-expert planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/subject-matter-expert.md))
|
||||
- Output: role_template_guidelines
|
||||
|
||||
3. **load_session_metadata**
|
||||
- Action: Load session metadata and existing context
|
||||
- Command: Read(.workflow/WFS-{session}/.brainstorming/session.json)
|
||||
- Output: session_context
|
||||
|
||||
## Analysis Requirements
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from domain expertise and technical standards perspective
|
||||
**Role Focus**: Domain knowledge, technical standards, risk assessment, knowledge transfer
|
||||
**Structured Approach**: Create analysis.md addressing framework discussion points
|
||||
**Template Integration**: Apply role template guidelines within framework structure
|
||||
|
||||
## Expected Deliverables
|
||||
1. **analysis.md**: Comprehensive domain expertise analysis addressing all framework discussion points
|
||||
2. **Framework Reference**: Include @../topic-framework.md reference in analysis
|
||||
|
||||
## Completion Criteria
|
||||
- Address each discussion point from topic-framework.md with subject matter expertise
|
||||
- Provide actionable technical standards and best practices recommendations
|
||||
- Include risk assessment and compliance considerations
|
||||
- Reference framework document using @ notation for integration
|
||||
"
|
||||
```
|
||||
|
||||
## 📋 **TodoWrite Integration**
|
||||
|
||||
### Workflow Progress Tracking
|
||||
```javascript
|
||||
TodoWrite({
|
||||
todos: [
|
||||
{
|
||||
content: "Detect active session and locate topic framework",
|
||||
status: "in_progress",
|
||||
activeForm: "Detecting session and framework"
|
||||
},
|
||||
{
|
||||
content: "Load topic-framework.md and session metadata for context",
|
||||
status: "pending",
|
||||
activeForm: "Loading framework and session context"
|
||||
},
|
||||
{
|
||||
content: "Execute subject-matter-expert analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
status: "pending",
|
||||
activeForm: "Executing subject-matter-expert framework analysis"
|
||||
},
|
||||
{
|
||||
content: "Generate analysis.md addressing all framework discussion points",
|
||||
status: "pending",
|
||||
activeForm: "Generating structured subject-matter-expert analysis"
|
||||
},
|
||||
{
|
||||
content: "Update session.json with subject-matter-expert completion status",
|
||||
status: "pending",
|
||||
activeForm: "Updating session metadata"
|
||||
}
|
||||
]
|
||||
});
|
||||
```
|
||||
|
||||
## 📊 **Output Structure**
|
||||
|
||||
### Framework-Based Analysis
|
||||
```
|
||||
.workflow/WFS-{session}/.brainstorming/subject-matter-expert/
|
||||
└── analysis.md # Structured analysis addressing topic-framework.md discussion points
|
||||
```
|
||||
|
||||
### Analysis Document Structure
|
||||
```markdown
|
||||
# Subject Matter Expert Analysis: [Topic from Framework]
|
||||
|
||||
## Framework Reference
|
||||
**Topic Framework**: @../topic-framework.md
|
||||
**Role Focus**: Domain Expertise & Technical Standards perspective
|
||||
|
||||
## Discussion Points Analysis
|
||||
[Address each point from topic-framework.md with subject matter expertise]
|
||||
|
||||
### Core Requirements (from framework)
|
||||
[Domain-specific requirements and industry standards perspective]
|
||||
|
||||
### Technical Considerations (from framework)
|
||||
[Deep technical analysis, architectural patterns, and best practices]
|
||||
|
||||
### User Experience Factors (from framework)
|
||||
[Domain-specific usability standards and industry conventions]
|
||||
|
||||
### Implementation Challenges (from framework)
|
||||
[Technical risks, scalability concerns, and maintenance implications]
|
||||
|
||||
### Success Metrics (from framework)
|
||||
[Domain-specific KPIs, compliance metrics, and quality standards]
|
||||
|
||||
## Subject Matter Expert Specific Recommendations
|
||||
[Role-specific technical expertise and industry best practices]
|
||||
|
||||
---
|
||||
*Generated by subject-matter-expert analysis addressing structured framework*
|
||||
```
|
||||
|
||||
## 🔄 **Session Integration**
|
||||
|
||||
### Completion Status Update
|
||||
```json
|
||||
{
|
||||
"subject_matter_expert": {
|
||||
"status": "completed",
|
||||
"framework_addressed": true,
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/subject-matter-expert/analysis.md",
|
||||
"framework_reference": "@../topic-framework.md"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Integration Points
|
||||
- **Framework Reference**: @../topic-framework.md for structured discussion points
|
||||
- **Cross-Role Synthesis**: Domain expertise insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
@@ -184,7 +184,7 @@ Strategic overview with key insights, breakthrough opportunities, and implementa
|
||||
|
||||
## Design Specifications
|
||||
### UI/UX Guidelines
|
||||
**Consolidated from**: @ui-designer/analysis.md, @user-researcher/analysis.md
|
||||
**Consolidated from**: @ui-designer/analysis.md, @ux-expert/analysis.md
|
||||
- Component specifications and interaction patterns
|
||||
- Visual design system and accessibility requirements
|
||||
- User flow and interface specifications
|
||||
@@ -195,11 +195,11 @@ Strategic overview with key insights, breakthrough opportunities, and implementa
|
||||
- Data flow and storage strategy
|
||||
- Technology stack decisions
|
||||
|
||||
### Security Framework
|
||||
**Consolidated from**: @security-expert/analysis.md
|
||||
- Authentication and authorization patterns
|
||||
- Data protection and compliance requirements
|
||||
- Security monitoring and audit strategy
|
||||
### Domain Expertise & Standards
|
||||
**Consolidated from**: @subject-matter-expert/analysis.md
|
||||
- Industry standards and best practices
|
||||
- Compliance requirements and regulations
|
||||
- Technical quality and domain-specific patterns
|
||||
|
||||
## Implementation Roadmap
|
||||
### Development Phases
|
||||
@@ -242,7 +242,7 @@ Upon completion, update `workflow-session.json`:
|
||||
"status": "completed",
|
||||
"synthesis_completed": true,
|
||||
"completed_at": "timestamp",
|
||||
"participating_roles": ["product-manager", "system-architect", "ui-designer", "security-expert", "data-architect", ...],
|
||||
"participating_roles": ["product-manager", "product-owner", "scrum-master", "system-architect", "ui-designer", "ux-expert", "data-architect", "subject-matter-expert", "test-strategist"],
|
||||
"consolidated_output": {
|
||||
"synthesis_specification": ".workflow/WFS-{topic}/.brainstorming/synthesis-specification.md"
|
||||
},
|
||||
|
||||
@@ -1,267 +0,0 @@
|
||||
---
|
||||
name: user-researcher
|
||||
description: User researcher perspective brainstorming for user behavior analysis and research insights
|
||||
usage: /workflow:brainstorm:user-researcher <topic>
|
||||
argument-hint: "topic or challenge to analyze from user research perspective"
|
||||
examples:
|
||||
- /workflow:brainstorm:user-researcher "user onboarding experience"
|
||||
- /workflow:brainstorm:user-researcher "mobile app usability issues"
|
||||
- /workflow:brainstorm:user-researcher "feature adoption analysis"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
||||
---
|
||||
|
||||
## 🔍 **Role Overview: User Researcher**
|
||||
|
||||
### Role Definition
|
||||
User experience research specialist responsible for understanding user behavior, identifying needs and pain points, and transforming research insights into actionable product improvements that enhance user satisfaction and engagement.
|
||||
|
||||
### Core Responsibilities
|
||||
- **User Behavior Research**: Deep analysis of user behavior patterns and motivations
|
||||
- **User Needs Discovery**: Research to discover unmet user needs and requirements
|
||||
- **Usability Assessment**: Evaluate product usability and user experience issues
|
||||
- **User Insights Generation**: Transform research findings into actionable product insights
|
||||
|
||||
### Focus Areas
|
||||
- **User Behavior**: Usage patterns, decision paths, task completion methods
|
||||
- **User Needs**: Explicit needs, implicit needs, emotional requirements
|
||||
- **User Experience**: Pain points, satisfaction levels, emotional responses, expectations
|
||||
- **Market Segmentation**: User personas, demographic segments, usage scenarios
|
||||
|
||||
### Success Metrics
|
||||
- User satisfaction and engagement scores
|
||||
- Task success rates and completion times
|
||||
- Quality and actionability of research insights
|
||||
- Impact of research on product decisions
|
||||
|
||||
## 🧠 **分析框架**
|
||||
|
||||
@~/.claude/workflows/brainstorming-principles.md
|
||||
|
||||
### Key Analysis Questions
|
||||
|
||||
**1. User Understanding and Insights**
|
||||
- What are the real needs and pain points of target users?
|
||||
- What are the user behavior patterns and usage scenarios?
|
||||
- What are the differentiated needs of various user groups?
|
||||
|
||||
**2. User Experience Analysis**
|
||||
- What are the main issues with the current user experience?
|
||||
- What obstacles and friction points exist in user task completion?
|
||||
- What gaps exist between user satisfaction and expectations?
|
||||
|
||||
**3. Research Methods and Validation**
|
||||
- Which research methods are most suitable for the current problem?
|
||||
- How can hypotheses and design decisions be validated?
|
||||
- How can continuous user feedback be collected?
|
||||
|
||||
**4. Insights Translation and Application**
|
||||
- How can research findings be translated into product improvements?
|
||||
- How can product decisions and design be influenced?
|
||||
- How can a user-centered culture be established?
|
||||
|
||||
## ⚡ **Two-Step Execution Flow**
|
||||
|
||||
### ⚠️ Session Management - FIRST STEP
|
||||
Session detection and selection:
|
||||
```bash
|
||||
# Check for active sessions
|
||||
active_sessions=$(find .workflow -name ".active-*" 2>/dev/null)
|
||||
if [ multiple_sessions ]; then
|
||||
prompt_user_to_select_session()
|
||||
else
|
||||
use_existing_or_create_new()
|
||||
fi
|
||||
```
|
||||
|
||||
### Step 1: Context Gathering Phase
|
||||
**User Researcher Perspective Questioning**
|
||||
|
||||
Before agent assignment, gather comprehensive user researcher context:
|
||||
|
||||
#### 📋 Role-Specific Questions
|
||||
|
||||
**1. User Behavior Patterns and Insights**
|
||||
- Who are the primary users and what are their key characteristics?
|
||||
- What user behaviors, patterns, or pain points have you observed?
|
||||
- Are there specific user segments or personas you're particularly interested in?
|
||||
- What user feedback or data do you already have available?
|
||||
|
||||
**2. Research Focus and Pain Points**
|
||||
- What specific user experience problems or questions need to be addressed?
|
||||
- Are there particular user tasks, workflows, or touchpoints to focus on?
|
||||
- What assumptions about users need to be validated or challenged?
|
||||
- What gaps exist in your current understanding of user needs?
|
||||
|
||||
**3. Research Context and Constraints**
|
||||
- What research has been done previously and what were the key findings?
|
||||
- Are there specific research methods you prefer or want to avoid?
|
||||
- What timeline and resources are available for user research?
|
||||
- Who are the key stakeholders that need to understand user insights?
|
||||
|
||||
**4. User Testing Strategy and Goals**
|
||||
- What specific user experience improvements are you hoping to achieve?
|
||||
- How do you currently measure user satisfaction or success?
|
||||
- Are there competitive products or experiences you want to benchmark against?
|
||||
- What would successful user research outcomes look like for this project?
|
||||
|
||||
#### Context Validation
|
||||
- **Minimum Response**: Each answer must be ≥50 characters
|
||||
- **Re-prompting**: Insufficient detail triggers follow-up questions
|
||||
- **Context Storage**: Save responses to `.brainstorming/user-researcher-context.md`
|
||||
|
||||
### Step 2: Agent Assignment with Flow Control
|
||||
**Dedicated Agent Execution**
|
||||
|
||||
```bash
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute dedicated user researcher conceptual analysis for: {topic}
|
||||
|
||||
ASSIGNED_ROLE: user-researcher
|
||||
OUTPUT_LOCATION: .brainstorming/user-researcher/
|
||||
USER_CONTEXT: {validated_responses_from_context_gathering}
|
||||
|
||||
Flow Control Steps:
|
||||
[
|
||||
{
|
||||
\"step\": \"load_role_template\",
|
||||
\"action\": \"Load user-researcher planning template\",
|
||||
\"command\": \"bash($(cat ~/.claude/workflows/cli-templates/planning-roles/user-researcher.md))\",
|
||||
\"output_to\": \"role_template\"
|
||||
}
|
||||
]
|
||||
|
||||
Conceptual Analysis Requirements:
|
||||
- Apply user researcher perspective to topic analysis
|
||||
- Focus on user behavior patterns, pain points, research insights, and user testing strategy
|
||||
- Use loaded role template framework for analysis structure
|
||||
- Generate role-specific deliverables in designated output location
|
||||
- Address all user context from questioning phase
|
||||
|
||||
Deliverables:
|
||||
- analysis.md: Main user researcher analysis
|
||||
- recommendations.md: User researcher recommendations
|
||||
- deliverables/: User researcher-specific outputs as defined in role template
|
||||
|
||||
Embody user researcher role expertise for comprehensive conceptual planning."
|
||||
```
|
||||
|
||||
### Progress Tracking
|
||||
TodoWrite tracking for two-step process:
|
||||
```json
|
||||
[
|
||||
{"content": "Gather user researcher context through role-specific questioning", "status": "in_progress", "activeForm": "Gathering context"},
|
||||
{"content": "Validate context responses and save to user-researcher-context.md", "status": "pending", "activeForm": "Validating context"},
|
||||
{"content": "Load user-researcher planning template via flow control", "status": "pending", "activeForm": "Loading template"},
|
||||
{"content": "Execute dedicated conceptual-planning-agent for user-researcher role", "status": "pending", "activeForm": "Executing agent"}
|
||||
]
|
||||
```
|
||||
|
||||
## 📊 **输出结构**
|
||||
|
||||
### 保存位置
|
||||
```
|
||||
.workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
|
||||
├── analysis.md # 主要用户研究分析
|
||||
├── user-personas.md # 详细用户画像和细分
|
||||
├── research-plan.md # 方法论和研究方法
|
||||
└── insights-recommendations.md # 关键发现和可执行建议
|
||||
```
|
||||
|
||||
### 文档模板
|
||||
|
||||
#### analysis.md 结构
|
||||
```markdown
|
||||
# User Researcher Analysis: {Topic}
|
||||
*Generated: {timestamp}*
|
||||
|
||||
## Executive Summary
|
||||
[核心用户研究发现和建议概述]
|
||||
|
||||
## Current User Landscape
|
||||
### User Base Overview
|
||||
### Behavioral Patterns
|
||||
### Usage Statistics and Trends
|
||||
### Satisfaction Metrics
|
||||
|
||||
## User Needs Analysis
|
||||
### Primary User Needs
|
||||
### Unmet Needs and Gaps
|
||||
### Need Prioritization Matrix
|
||||
### Emotional and Functional Needs
|
||||
|
||||
## User Experience Assessment
|
||||
### Current UX Strengths
|
||||
### Major Pain Points and Friction
|
||||
### Usability Issues Identified
|
||||
### Accessibility Gaps
|
||||
|
||||
## User Behavior Insights
|
||||
### User Journey Mapping
|
||||
### Decision-Making Patterns
|
||||
### Task Completion Analysis
|
||||
### Behavioral Segments
|
||||
|
||||
## Research Recommendations
|
||||
### Recommended Research Methods
|
||||
### Key Research Questions
|
||||
### Success Metrics and KPIs
|
||||
### Research Timeline and Resources
|
||||
|
||||
## Actionable Insights
|
||||
### Immediate UX Improvements
|
||||
### Product Feature Recommendations
|
||||
### Long-term User Strategy
|
||||
### Success Measurement Plan
|
||||
```
|
||||
|
||||
## 🔄 **会话集成**
|
||||
|
||||
### 状态同步
|
||||
分析完成后，更新 `workflow-session.json`:
|
||||
```json
|
||||
{
|
||||
"phases": {
|
||||
"BRAINSTORM": {
|
||||
"user_researcher": {
|
||||
"status": "completed",
|
||||
"completed_at": "timestamp",
|
||||
"output_directory": ".workflow/WFS-{topic}/.brainstorming/user-researcher/",
|
||||
"key_insights": ["user_behavior_pattern", "unmet_need", "usability_issue"]
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 与其他角色的协作
|
||||
用户研究员视角为其他角色提供：
|
||||
- **用户需求和洞察** → Product Manager
|
||||
- **用户行为数据** → Data Architect
|
||||
- **用户体验要求** → UI Designer
|
||||
- **用户安全需求** → Security Expert
|
||||
- **功能使用场景** → Feature Planner
|
||||
|
||||
## ✅ **质量标准**
|
||||
|
||||
### 必须包含的研究元素
|
||||
- [ ] 详细的用户行为分析
|
||||
- [ ] 明确的用户需求识别
|
||||
- [ ] 全面的用户体验评估
|
||||
- [ ] 科学的研究方法设计
|
||||
- [ ] 可执行的改进建议
|
||||
|
||||
### 用户研究原则检查
|
||||
- [ ] 以人为本：所有分析以用户为中心
|
||||
- [ ] 基于证据：结论有数据和研究支撑
|
||||
- [ ] 行为导向：关注实际行为而非声明意图
|
||||
- [ ] 情境考虑：分析使用场景和环境因素
|
||||
- [ ] 持续迭代：建立持续研究和改进机制
|
||||
|
||||
### 洞察质量评估
|
||||
- [ ] 洞察的新颖性和深度
|
||||
- [ ] 建议的可操作性和具体性
|
||||
- [ ] 影响评估的准确性
|
||||
- [ ] 研究方法的科学性
|
||||
- [ ] 用户代表性的覆盖度
|
||||
@@ -1,31 +1,31 @@
|
||||
---
|
||||
name: feature-planner
|
||||
description: Generate or update feature-planner/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:feature-planner [topic]
|
||||
name: ux-expert
|
||||
description: Generate or update ux-expert/analysis.md addressing topic-framework discussion points
|
||||
usage: /workflow:brainstorm:ux-expert [topic]
|
||||
argument-hint: "optional topic - uses existing framework if available"
|
||||
examples:
|
||||
- /workflow:brainstorm:feature-planner
|
||||
- /workflow:brainstorm:feature-planner "user dashboard enhancement"
|
||||
- /workflow:brainstorm:feature-planner "mobile app feature roadmap"
|
||||
- /workflow:brainstorm:ux-expert
|
||||
- /workflow:brainstorm:ux-expert "user authentication redesign"
|
||||
- /workflow:brainstorm:ux-expert "mobile app performance optimization"
|
||||
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
|
||||
---
|
||||
|
||||
## 🔧 **Feature Planner Analysis Generator**
|
||||
## 🎯 **UX Expert Analysis Generator**
|
||||
|
||||
### Purpose
|
||||
**Specialized command for generating feature-planner/analysis.md** that addresses topic-framework.md discussion points from feature development perspective. Creates or updates role-specific analysis with framework references.
|
||||
**Specialized command for generating ux-expert/analysis.md** that addresses topic-framework.md discussion points from user experience and interface design perspective. Creates or updates role-specific analysis with framework references.
|
||||
|
||||
### Core Function
|
||||
- **Framework-based Analysis**: Address each discussion point in topic-framework.md
|
||||
- **Feature Development Focus**: Feature specification, development planning, and delivery management
|
||||
- **UX Design Focus**: User interface, interaction patterns, and usability optimization
|
||||
- **Update Mechanism**: Create new or update existing analysis.md
|
||||
- **Agent Delegation**: Use conceptual-planning-agent for analysis generation
|
||||
|
||||
### Analysis Scope
|
||||
- **Feature Specification**: Transform requirements into detailed specifications
|
||||
- **Development Planning**: Sprint planning, milestones, and dependency management
|
||||
- **Quality Assurance**: Testing strategies and acceptance criteria
|
||||
- **Delivery Management**: Release planning and implementation timelines
|
||||
- **User Interface Design**: Visual hierarchy, layout patterns, and component design
|
||||
- **Interaction Patterns**: User flows, navigation, and microinteractions
|
||||
- **Usability Optimization**: Accessibility, cognitive load, and user testing strategies
|
||||
- **Design Systems**: Component libraries, design tokens, and consistency frameworks
|
||||
|
||||
## ⚙️ **Execution Protocol**
|
||||
|
||||
@@ -68,11 +68,11 @@ ELSE:
|
||||
Task(conceptual-planning-agent): "
|
||||
[FLOW_CONTROL]
|
||||
|
||||
Execute feature-planner analysis for existing topic framework
|
||||
Execute ux-expert analysis for existing topic framework
|
||||
|
||||
## Context Loading
|
||||
ASSIGNED_ROLE: feature-planner
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/feature-planner/
|
||||
ASSIGNED_ROLE: ux-expert
|
||||
OUTPUT_LOCATION: .workflow/WFS-{session}/.brainstorming/ux-expert/
|
||||
ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
|
||||
## Flow Control Steps
|
||||
@@ -82,8 +82,8 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
- Output: topic_framework_content
|
||||
|
||||
2. **load_role_template**
|
||||
- Action: Load feature-planner planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/feature-planner.md))
|
||||
- Action: Load ux-expert planning template
|
||||
- Command: bash($(cat ~/.claude/workflows/cli-templates/planning-roles/ux-expert.md))
|
||||
- Output: role_template_guidelines
|
||||
|
||||
3. **load_session_metadata**
|
||||
@@ -92,19 +92,19 @@ ANALYSIS_MODE: {framework_mode ? "framework_based" : "standalone"}
|
||||
- Output: session_context
|
||||
|
||||
## Analysis Requirements
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from feature development perspective
|
||||
**Role Focus**: Feature specification, development planning, quality assurance, delivery management
|
||||
**Framework Reference**: Address all discussion points in topic-framework.md from user experience and interface design perspective
|
||||
**Role Focus**: UI design, interaction patterns, usability optimization, design systems
|
||||
**Structured Approach**: Create analysis.md addressing framework discussion points
|
||||
**Template Integration**: Apply role template guidelines within framework structure
|
||||
|
||||
## Expected Deliverables
|
||||
1. **analysis.md**: Comprehensive feature planning analysis addressing all framework discussion points
|
||||
1. **analysis.md**: Comprehensive UX design analysis addressing all framework discussion points
|
||||
2. **Framework Reference**: Include @../topic-framework.md reference in analysis
|
||||
|
||||
## Completion Criteria
|
||||
- Address each discussion point from topic-framework.md with feature development expertise
|
||||
- Provide actionable development plans and implementation strategies
|
||||
- Include quality assurance and testing considerations
|
||||
- Address each discussion point from topic-framework.md with UX design expertise
|
||||
- Provide actionable interface design and usability optimization strategies
|
||||
- Include accessibility considerations and interaction pattern recommendations
|
||||
- Reference framework document using @ notation for integration
|
||||
"
|
||||
```
|
||||
@@ -126,17 +126,17 @@ TodoWrite({
|
||||
activeForm: "Loading framework and session context"
|
||||
},
|
||||
{
|
||||
content: "Execute feature-planner analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
content: "Execute ux-expert analysis using conceptual-planning-agent with FLOW_CONTROL",
|
||||
status: "pending",
|
||||
activeForm: "Executing feature-planner framework analysis"
|
||||
activeForm: "Executing ux-expert framework analysis"
|
||||
},
|
||||
{
|
||||
content: "Generate analysis.md addressing all framework discussion points",
|
||||
status: "pending",
|
||||
activeForm: "Generating structured feature-planner analysis"
|
||||
activeForm: "Generating structured ux-expert analysis"
|
||||
},
|
||||
{
|
||||
content: "Update session.json with feature-planner completion status",
|
||||
content: "Update session.json with ux-expert completion status",
|
||||
status: "pending",
|
||||
activeForm: "Updating session metadata"
|
||||
}
|
||||
@@ -148,41 +148,41 @@ TodoWrite({
|
||||
|
||||
### Framework-Based Analysis
|
||||
```
|
||||
.workflow/WFS-{session}/.brainstorming/feature-planner/
|
||||
.workflow/WFS-{session}/.brainstorming/ux-expert/
|
||||
└── analysis.md # Structured analysis addressing topic-framework.md discussion points
|
||||
```
|
||||
|
||||
### Analysis Document Structure
|
||||
```markdown
|
||||
# Feature Planner Analysis: [Topic from Framework]
|
||||
# UX Expert Analysis: [Topic from Framework]
|
||||
|
||||
## Framework Reference
|
||||
**Topic Framework**: @../topic-framework.md
|
||||
**Role Focus**: Feature Development perspective
|
||||
**Role Focus**: User Experience & Interface Design perspective
|
||||
|
||||
## Discussion Points Analysis
|
||||
[Address each point from topic-framework.md with feature development expertise]
|
||||
[Address each point from topic-framework.md with UX design expertise]
|
||||
|
||||
### Core Requirements (from framework)
|
||||
[Feature development perspective on requirements]
|
||||
[User interface and interaction design requirements perspective]
|
||||
|
||||
### Technical Considerations (from framework)
|
||||
[Feature architecture and development considerations]
|
||||
[Design system implementation and technical feasibility considerations]
|
||||
|
||||
### User Experience Factors (from framework)
|
||||
[Feature usability and user story considerations]
|
||||
[Usability optimization, accessibility, and user-centered design analysis]
|
||||
|
||||
### Implementation Challenges (from framework)
|
||||
[Development complexity and delivery considerations]
|
||||
[Design implementation challenges and progressive enhancement strategies]
|
||||
|
||||
### Success Metrics (from framework)
|
||||
[Feature success metrics and acceptance criteria]
|
||||
[UX metrics including usability testing, user satisfaction, and design KPIs]
|
||||
|
||||
## Feature Development Specific Recommendations
|
||||
[Role-specific feature planning recommendations and strategies]
|
||||
## UX Expert Specific Recommendations
|
||||
[Role-specific interface design patterns and usability optimization strategies]
|
||||
|
||||
---
|
||||
*Generated by feature-planner analysis addressing structured framework*
|
||||
*Generated by ux-expert analysis addressing structured framework*
|
||||
```
|
||||
|
||||
## 🔄 **Session Integration**
|
||||
@@ -190,10 +190,10 @@ TodoWrite({
|
||||
### Completion Status Update
|
||||
```json
|
||||
{
|
||||
"feature_planner": {
|
||||
"ux_expert": {
|
||||
"status": "completed",
|
||||
"framework_addressed": true,
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/feature-planner/analysis.md",
|
||||
"output_location": ".workflow/WFS-{session}/.brainstorming/ux-expert/analysis.md",
|
||||
"framework_reference": "@../topic-framework.md"
|
||||
}
|
||||
}
|
||||
@@ -201,5 +201,5 @@ TodoWrite({
|
||||
|
||||
### Integration Points
|
||||
- **Framework Reference**: @../topic-framework.md for structured discussion points
|
||||
- **Cross-Role Synthesis**: Feature development insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
- **Cross-Role Synthesis**: UX design insights available for synthesis-report.md integration
|
||||
- **Agent Autonomy**: Independent execution with framework guidance
|
||||
Reference in New Issue
Block a user