mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +08:00
39a35c24b1
- Streamlined analysis templates (architecture, pattern, performance, quality, security) - Simplified development templates (component, debugging, feature, refactor, testing) - Optimized documentation templates (api, folder-navigation, module-readme, project-architecture, project-examples, project-readme) - Enhanced planning templates (concept-eval, migration, task-breakdown) - Improved verification templates (codex-technical, cross-validation, gemini-strategic) - Updated claude-module-unified memory template - Refined workflow-architecture documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
29 lines
1.5 KiB
Plaintext
29 lines
1.5 KiB
Plaintext
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.
|