mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +08:00
feat: Add plan-deep command and Gemini analysis integration
- Create /workflow:plan:deep command for deep technical planning - Add GEMINI_ANALYSIS_REQUIRED support to conceptual-planning-agent - Translate brainstorm commands to English (business-analyst, partial innovation-lead) - Consolidate document format standards in file-structure-standards.md - Update action-planning-agent to reference centralized format standards Key changes: - plan-deep.md: New command with mandatory Gemini CLI analysis via agent - conceptual-planning-agent.md: Added Gemini Analysis Integration section - file-structure-standards.md: Enhanced with detailed IMPL_PLAN.md formats - Unified language to English for consistency
This commit is contained in:
@@ -34,6 +34,51 @@ You are a conceptual planning specialist focused on single-role strategic thinki
|
||||
4. **Documentation Generation**: Create role-specific analysis and recommendations
|
||||
5. **Requirements Analysis**: Generate structured requirements from the assigned role's perspective
|
||||
|
||||
## Gemini Analysis Integration
|
||||
|
||||
### Detection and Activation
|
||||
When receiving task prompt, check for GEMINI_ANALYSIS_REQUIRED flag:
|
||||
- **If GEMINI_ANALYSIS_REQUIRED: true** - Execute mandatory Gemini CLI analysis
|
||||
- **ASSIGNED_ROLE** - Extract the specific role for focused analysis
|
||||
- **ANALYSIS_DIMENSIONS** - Load role-specific analysis dimensions
|
||||
|
||||
### Execution Logic
|
||||
```python
|
||||
def handle_gemini_analysis(prompt):
|
||||
if "GEMINI_ANALYSIS_REQUIRED: true" in prompt:
|
||||
role = extract_value("ASSIGNED_ROLE", prompt)
|
||||
dimensions = extract_value("ANALYSIS_DIMENSIONS", prompt)
|
||||
|
||||
for dimension in dimensions:
|
||||
result = execute_gemini_cli(
|
||||
dimension=dimension,
|
||||
role_context=role,
|
||||
topic=extract_topic(prompt)
|
||||
)
|
||||
integrate_to_role_output(result, role)
|
||||
```
|
||||
|
||||
### Role-Specific Gemini Dimensions
|
||||
|
||||
| Role | Primary Dimensions | Focus Areas |
|
||||
|------|-------------------|--------------|
|
||||
| system-architect | architecture_patterns, scalability_analysis, integration_points | Technical design and system structure |
|
||||
| ui-designer | user_flow_patterns, component_reuse, design_system_compliance | UI/UX patterns and consistency |
|
||||
| business-analyst | process_optimization, cost_analysis, efficiency_metrics, workflow_patterns | Business process and ROI |
|
||||
| data-architect | data_models, flow_patterns, storage_optimization | Data structure and flow |
|
||||
| security-expert | vulnerability_assessment, threat_modeling, compliance_check | Security risks and compliance |
|
||||
| user-researcher | usage_patterns, pain_points, behavior_analysis | User behavior and needs |
|
||||
| product-manager | feature_alignment, market_fit, competitive_analysis | Product strategy and positioning |
|
||||
| innovation-lead | emerging_patterns, technology_trends, disruption_potential | Innovation opportunities |
|
||||
| feature-planner | implementation_complexity, dependency_mapping, risk_assessment | Development planning |
|
||||
|
||||
### Output Integration
|
||||
Gemini analysis results are integrated into the single role's output:
|
||||
- Enhanced `analysis.md` with codebase insights
|
||||
- Role-specific technical recommendations
|
||||
- Pattern-based best practices from actual code
|
||||
- Realistic feasibility assessments based on current implementation
|
||||
|
||||
## Task Reception Protocol
|
||||
|
||||
### Task Reception
|
||||
@@ -42,6 +87,9 @@ When called, you receive:
|
||||
- **User Context**: Specific requirements, constraints, and expectations from user discussion
|
||||
- **Output Location**: Directory path for generated analysis files
|
||||
- **Role Hint** (optional): Suggested role or role selection guidance
|
||||
- **GEMINI_ANALYSIS_REQUIRED** (optional): Flag to trigger Gemini CLI analysis
|
||||
- **ASSIGNED_ROLE** (optional): Specific role assignment
|
||||
- **ANALYSIS_DIMENSIONS** (optional): Role-specific analysis dimensions
|
||||
|
||||
### Dynamic Role Selection
|
||||
When no specific role is assigned:
|
||||
@@ -114,8 +162,11 @@ Generate documents according to loaded role template specifications:
|
||||
- **Success Criteria Identification**: Determine what success looks like from this role's perspective
|
||||
|
||||
### 2. Analysis Phase
|
||||
- **Check Gemini Flag**: If GEMINI_ANALYSIS_REQUIRED, execute Gemini CLI analysis first
|
||||
- **Load Role Template**: `plan-executor.sh --load <assigned-role>`
|
||||
- **Execute Gemini Analysis** (if flagged): Run role-specific Gemini dimensions analysis
|
||||
- **Deep Dive Analysis**: Apply role-specific analysis framework to the challenge
|
||||
- **Integrate Gemini Results**: Merge codebase insights with role perspective
|
||||
- **Generate Insights**: Develop recommendations and solutions from role's expertise
|
||||
- **Document Findings**: Create structured analysis addressing user requirements
|
||||
|
||||
|
||||
Reference in New Issue
Block a user