mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-14 02:42:04 +08:00
feat(cli): 添加 --rule 选项支持模板自动发现
重构 ccw cli 模板系统: - 新增 template-discovery.ts 模块,支持扁平化模板自动发现 - 添加 --rule <template> 选项,自动加载 protocol 和 template - 模板目录从嵌套结构 (prompts/category/file.txt) 迁移到扁平结构 (prompts/category-function.txt) - 更新所有 agent/command 文件,使用 $PROTO $TMPL 环境变量替代 $(cat ...) 模式 - 支持模糊匹配:--rule 02-review-architecture 可匹配 analysis-review-architecture.txt 其他更新: - Dashboard: 添加 Claude Manager 和 Issue Manager 页面 - Codex-lens: 增强 chain_search 和 clustering 模块 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
Validate the strategic and architectural soundness of a workflow implementation plan.
|
||||
|
||||
## CORE CHECKLIST ⚡
|
||||
□ Evaluate the plan against high-level system architecture
|
||||
□ Assess the logic of the task breakdown and dependencies
|
||||
□ Verify alignment with stated business objectives and success criteria
|
||||
□ Identify strategic risks, not just low-level technical ones
|
||||
|
||||
## REQUIRED STRATEGIC ANALYSIS
|
||||
1. **Architectural Soundness**: Assess design coherence and pattern consistency.
|
||||
2. **Task Decomposition Logic**: Review task breakdown, granularity, and completeness.
|
||||
3. **Dependency Coherence**: Analyze task interdependencies and logical flow.
|
||||
4. **Business Alignment**: Validate against business objectives and requirements.
|
||||
5. **Strategic Risk Identification**: Identify architectural, resource, and timeline risks.
|
||||
|
||||
## OUTPUT REQUIREMENTS
|
||||
- **Strategic Assessment Report**: Grades for architecture, decomposition, and business alignment.
|
||||
- **Detailed Recommendations**: Critical issues, improvements, and alternative approaches.
|
||||
- **Action Items**: A prioritized list of changes (Immediate, Short-term, Long-term).
|
||||
|
||||
## VERIFICATION CHECKLIST ✓
|
||||
□ The plan's architectural soundness has been thoroughly assessed
|
||||
□ Task decomposition and dependencies are logical and coherent
|
||||
□ The plan is confirmed to be in alignment with business goals
|
||||
□ Strategic risks are identified with clear recommendations
|
||||
|
||||
Focus: High-level strategic concerns, business alignment, and long-term architectural implications.
|
||||
Reference in New Issue
Block a user