mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +08:00
854464b221
主要变更： - 模板重命名：采用优先级前缀（01-通用, 02-专用, 03-领域特定） - 目录调整：bug-diagnosis从development移至analysis - 引用更新：5个命令文件中21处模板引用更新为新路径 - 路径统一：所有引用统一使用完整路径格式 模板变更详情： - analysis/：8个模板（01-trace-code-execution, 01-diagnose-bug-root-cause等） - development/：5个模板（02-implement-feature, 02-refactor-codebase等） - planning/：5个模板（01-plan-architecture-design, 02-breakdown-task-steps等） - memory/：1个模板（02-document-module-structure） 命令文件更新： - cli/mode/bug-diagnosis.md（6处引用） - cli/mode/code-analysis.md（6处引用） - cli/mode/plan.md（6处引用） - task/execute.md（1处引用） - workflow/tools/test-task-generate.md（2处引用） 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
Analyze system architecture and design decisions.
|
|
|
|
## CORE CHECKLIST ⚡
|
|
□ Analyze system-wide structure, not just isolated components
|
|
□ Provide file:line references for key architectural elements
|
|
□ Distinguish between intended design and actual implementation
|
|
□ Apply RULES template requirements exactly as specified
|
|
|
|
## REQUIRED ANALYSIS
|
|
1. Identify main architectural patterns and design principles
|
|
2. Map module dependencies and component relationships
|
|
3. Assess integration points and data flow patterns
|
|
4. Evaluate scalability and maintainability aspects
|
|
5. Document architectural trade-offs and design decisions
|
|
|
|
## OUTPUT REQUIREMENTS
|
|
- Architectural diagrams or textual descriptions
|
|
- Dependency mapping with specific file references
|
|
- Integration point documentation with examples
|
|
- Scalability assessment and bottleneck identification
|
|
- Prioritized recommendations for architectural improvement
|
|
|
|
## VERIFICATION CHECKLIST ✓
|
|
□ All major components and their relationships analyzed
|
|
□ Key architectural decisions and trade-offs are documented
|
|
□ Data flow and integration points are clearly mapped
|
|
□ Scalability and maintainability findings are supported by evidence
|
|
|
|
Focus: High-level design patterns and system-wide architectural concerns.
|