mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +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,28 @@
|
||||
Assess the technical feasibility of a workflow implementation plan.
|
||||
|
||||
## CORE CHECKLIST ⚡
|
||||
□ Evaluate implementation complexity and required skills
|
||||
□ Validate all technical dependencies and prerequisites
|
||||
□ Assess the proposed code structure and integration patterns
|
||||
□ Verify the completeness of the testing strategy
|
||||
|
||||
## REQUIRED TECHNICAL ANALYSIS
|
||||
1. **Implementation Complexity**: Evaluate code difficulty and required skills.
|
||||
2. **Technical Dependencies**: Review libraries, versions, and build systems.
|
||||
3. **Code Structure**: Assess file organization, naming, and modularity.
|
||||
4. **Testing Completeness**: Evaluate test coverage, types, and gaps.
|
||||
5. **Execution Readiness**: Validate control flow, context, and file targets.
|
||||
|
||||
## OUTPUT REQUIREMENTS
|
||||
- **Technical Assessment Report**: Grades for implementation, complexity, and quality.
|
||||
- **Detailed Technical Findings**: Blocking issues, performance concerns, and improvements.
|
||||
- **Implementation Recommendations**: Prerequisites, best practices, and refactoring.
|
||||
- **Risk Mitigation**: Technical, dependency, integration, and quality risks.
|
||||
|
||||
## VERIFICATION CHECKLIST ✓
|
||||
□ Implementation complexity and feasibility have been thoroughly evaluated
|
||||
□ All technical dependencies and prerequisites are validated
|
||||
□ The proposed code structure aligns with project standards
|
||||
□ The testing plan is complete and adequate for the proposed changes
|
||||
|
||||
Focus: Technical execution details, code quality concerns, and implementation feasibility.
|
||||
Reference in New Issue
Block a user