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:
catlog22
2025-09-09 10:52:51 +08:00
parent 6f85340ab8
commit b6dda499e4
6 changed files with 638 additions and 260 deletions

View File

@@ -125,11 +125,17 @@ impl-2 # Another main task
### Document Template Standards
#### IMPL_PLAN.md Structure
Two formats available based on task complexity:
##### Stage-Based Format (Simple Tasks)
Use for tasks with clear, linear progression:
```markdown
# Implementation Plan: [Session Topic]
# Implementation Plan: [Task Name]
## Overview
[High-level description]
[Brief description of the overall goal and approach]
## Requirements
[Functional and non-functional requirements]
@@ -137,17 +143,95 @@ impl-2 # Another main task
## [Brainstorming Integration]
[If .brainstorming/ exists - reference analysis results]
## Implementation Strategy
[Technical approach and phases]
## Stage 1: [Name]
**Goal**: [Specific deliverable]
**Success Criteria**:
- [Testable outcome 1]
- [Testable outcome 2]
**Tests**:
- [Specific test case 1]
- [Specific test case 2]
**Dependencies**: [Previous stages or external requirements]
**Estimated Effort**: [Small/Medium/Large]
**Review Status**: [Not Started]
**Status**: [Not Started]
## Success Criteria
[Acceptance criteria and validation]
## Stage 2: [Name]
[Repeat stage structure]
## Stage 3: [Name]
[Repeat stage structure]
## Risk Mitigation
[Identified risks and mitigation strategies]
## Rollback Strategy
[How to revert if issues arise]
```
##### Hierarchical Format (Complex Tasks)
Use for tasks requiring >5 subtasks or spanning >3 modules:
```markdown
# Implementation Plan: [Project Name]
## Overview
[Brief description and strategic approach]
## Requirements
[Functional and non-functional requirements]
## Task Hierarchy
### Main Task: [IMPL-001] [Primary Goal]
**Description**: [Detailed description]
**Complexity**: [High/Medium/Low]
**Estimated Effort**: [Time estimate]
**Dependencies**: [External dependencies]
**Status**: [Not Started]
#### Subtask: [IMPL-001.1] [Subtask Name]
**Description**: [Specific deliverable]
**Assigned Agent**: [code-developer/code-review-agent/general-purpose]
**Dependencies**: [Parent/peer task dependencies]
**Acceptance Criteria**:
- [Testable criteria 1]
- [Testable criteria 2]
**Estimated Effort**: [Time estimate]
**Assigned Module**: [Component/file location]
**Status**: [Not Started]
**Links**: [Related documentation/requirements]
##### Action Item: [IMPL-001.1.1] [Specific Action]
**Type**: [Code/Test/Documentation/Review]
**Recommended Agent**: [code-developer/code-review-agent/general-purpose]
**Description**: [Concrete action]
**Files Affected**: [List of files]
**Verification**: [How to verify completion]
**Status**: [Not Started]
[Repeat structure for all tasks/subtasks/actions]
### Main Task: [IMPL-002] [Secondary Goal]
[Repeat task structure]
## Dependency Graph
[Visual or text representation of task dependencies]
## Resource Requirements
[Tools, libraries, external dependencies needed]
## Risk Assessment
[Potential issues and mitigation strategies]
[Task-specific risks and mitigation strategies]
## Rollback Strategy
[System-wide rollback procedures]
```
#### TODO_LIST.md Structure
**Keep simple and focused on task tracking:**
```markdown
# Task Progress List: [Session Topic]
@@ -159,8 +243,20 @@ impl-2 # Another main task
### Subtasks (Auto-expanded when active)
- [ ] **IMPL-001.1**: [Subtask Description] → [📋 Details](./.task/impl-001.1.json)
- [ ] **IMPL-001.1.1**: [Action Item] → [📋 Details](./.task/impl-001.1.1.json)
- [ ] **IMPL-001.2**: [Subtask Description] → [📋 Details](./.task/impl-001.2.json)
## Notes
[Quick notes and reminders for the project]
```
**Format Notes**:
- Main tasks use bold formatting: `**IMPL-XXX**`
- Subtasks indent under parent tasks
- Links to task JSON files for details
- Links to summaries when completed
- Keep format simple and scannable
## Chat Session Management
### Chat Directory Structure