catlog22/Claude-Code-Workflow
1
0
Fork 0
mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-13 02:41:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

refactor: optimize workflow templates and prompt structures

Browse Source 
- 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>
This commit is contained in:
catlog22
2025-10-16 13:48:35 +08:00
parent e95be40c2b
commit 39a35c24b1
26 changed files with 693 additions and 1402 deletions
Download Patch File Download Diff File Expand all files Collapse all files

77
.claude/workflows/cli-templates/prompts/verification/codex-technical.txt
View File

@@ -1,59 +1,28 @@
Technical feasibility assessment of workflow implementation plan from code quality and execution perspective:
Assess the technical feasibility of a workflow implementation plan.
## Required Technical Analysis:
1. **Implementation Complexity Assessment**
- Evaluate code complexity and technical difficulty
- Assess required technical skills and expertise levels
- Validate implementation approach feasibility
- Identify technical challenges and solutions
## 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
2. **Technical Dependencies Validation**
- Review external library and framework dependencies
- Assess version compatibility and dependency conflicts
- Evaluate build system and deployment requirements
- Identify missing technical prerequisites
## 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.
3. **Code Structure Assessment**
- Evaluate proposed file organization and structure
- Assess naming conventions and code organization
- Validate integration with existing codebase patterns
- Review modularity and separation of concerns
## 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.
4. **Testing Completeness Evaluation**
- Assess test coverage and testing strategy completeness
- Evaluate test types and testing approach adequacy
- Review integration testing and end-to-end coverage
- Identify testing gaps and quality assurance needs
## 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
5. **Execution Readiness Verification**
- Validate flow_control definitions and execution paths
- Assess task context completeness and adequacy
- Evaluate target_files specifications and accuracy
- Review implementation prerequisites and setup requirements
## Output Requirements:
### Technical Assessment Report:
- **Implementation Grade** (A-F): Technical approach quality
- **Complexity Score** (1-10): Implementation difficulty level
- **Readiness Level** (1-5): Execution preparation completeness
- **Quality Rating** (1-10): Code quality and maintainability projection
### Detailed Technical Findings:
- **Blocking Issues**: Technical problems that prevent implementation
- **Performance Concerns**: Scalability and performance implications
- **Quality Improvements**: Code quality and maintainability enhancements
- **Testing Enhancements**: Testing strategy and coverage improvements
### Implementation Recommendations:
- **Prerequisites**: Required setup and configuration changes
- **Best Practices**: Code patterns and conventions to follow
- **Tool Requirements**: Additional tools or dependencies needed
- **Refactoring Suggestions**: Code structure and organization improvements
### Risk Mitigation:
- **Technical Risks**: Implementation complexity and technical debt
- **Dependency Risks**: External dependencies and compatibility issues
- **Integration Risks**: Codebase integration and compatibility concerns
- **Quality Risks**: Code quality and maintainability implications
Focus on technical execution details, code quality concerns, and implementation feasibility. Provide specific, actionable recommendations with clear implementation guidance and priority levels.
Focus: Technical execution details, code quality concerns, and implementation feasibility.