cqt-agent/expansion-packs/hubtel-workflow/checklists/project-understanding-checklist.md

CQT Agent

# Project Understanding Checklist

## Overview

This checklist validates that an engineer has achieved comprehensive project understanding and is ready for independent, confident contribution. Use this as both an onboarding validation tool and a self-assessment guide.

## Business Context Understanding ✅

### Project Purpose & Value
- [ ] **Business Problem**: Can clearly explain what business problem this project solves
- [ ] **User Value**: Understands how end users benefit from this system
- [ ] **Success Metrics**: Knows how project success is measured and tracked
- [ ] **Hubtel Ecosystem Role**: Understands how this project fits into Hubtel's broader platform
- [ ] **Stakeholder Impact**: Can identify who is affected by changes to this system

### User Understanding
- [ ] **Primary Users**: Can describe who the main users are and their typical workflows
- [ ] **User Journeys**: Understands critical user paths through the system
- [ ] **Pain Points**: Aware of common user issues and system limitations
- [ ] **Usage Patterns**: Knows when and how the system experiences peak usage
- [ ] **Feature Priorities**: Understands which features are most critical to users

### Business Context Application
- [ ] **Change Prioritization**: Can assess business impact of different types of changes
- [ ] **Feature Decisions**: Understands rationale behind existing feature choices
- [ ] **Resource Allocation**: Aware of team priorities and resource constraints
- [ ] **Competitive Landscape**: Knows how this system compares to alternatives
- [ ] **Regulatory Requirements**: Understands any compliance or regulatory considerations

## Technical Architecture Mastery ✅

### System Design Understanding
- [ ] **High-Level Architecture**: Can draw and explain the system architecture diagram
- [ ] **Component Relationships**: Understands how major components interact and depend on each other
- [ ] **Data Flow**: Can trace data movement through the entire system
- [ ] **System Boundaries**: Clearly understands what's internal vs external to the system
- [ ] **Integration Points**: Knows all external systems, APIs, and services integrated

### Technology Stack Proficiency
- [ ] **Primary Technologies**: Confident with main frameworks, languages, and tools used
- [ ] **Architecture Patterns**: Understands design patterns used and why they were chosen
- [ ] **Database Design**: Comfortable with data models, relationships, and query patterns
- [ ] **Performance Characteristics**: Aware of system performance patterns and bottlenecks
- [ ] **Scalability Considerations**: Understands how system handles load and growth

### Code Organization Mastery
- [ ] **Directory Structure**: Can navigate codebase efficiently and understands organization logic
- [ ] **Naming Conventions**: Follows and understands project naming and coding conventions
- [ ] **Abstraction Layers**: Comfortable with different abstraction levels and their purposes
- [ ] **Dependency Management**: Understands how components depend on each other
- [ ] **Configuration Management**: Knows how system configuration is managed across environments

## Development Workflow Proficiency ✅

### Local Development Mastery
- [ ] **Environment Setup**: Can set up development environment from scratch without guidance
- [ ] **Development Tools**: Proficient with IDE, debugger, and development utilities
- [ ] **Local Testing**: Can run full test suite locally and understands test categories
- [ ] **Database Management**: Comfortable with local database setup and migrations
- [ ] **Service Dependencies**: Can start and manage external service dependencies locally

### Testing Competence
- [ ] **Test Types**: Understands unit, integration, and E2E testing approaches used
- [ ] **Test Execution**: Can run different test categories and interpret results
- [ ] **Test Writing**: Can write tests following project patterns and conventions
- [ ] **Coverage Understanding**: Knows coverage expectations and can assess test completeness
- [ ] **Test Debugging**: Can debug failing tests and understand root causes

### Development Process Understanding
- [ ] **Branching Strategy**: Understands git workflow and branching conventions
- [ ] **Code Review Process**: Knows how to request reviews and provide quality feedback
- [ ] **CI/CD Pipeline**: Understands build, test, and deployment automation
- [ ] **Quality Gates**: Aware of quality checks and requirements before code merge
- [ ] **Documentation Standards**: Knows when and how to update project documentation

## Change Implementation Confidence ✅

### Change Planning Ability
- [ ] **Impact Assessment**: Can analyze the impact of proposed changes across the system
- [ ] **Risk Evaluation**: Able to identify high-risk vs low-risk changes
- [ ] **Testing Strategy**: Can determine appropriate testing approach for different changes
- [ ] **Rollback Planning**: Understands how to safely undo changes if problems arise
- [ ] **Performance Consideration**: Aware of performance implications of different changes

### Implementation Patterns
- [ ] **Common Scenarios**: Confident implementing common change patterns (CRUD, API endpoints, UI components)
- [ ] **Code Patterns**: Consistently follows established coding patterns and conventions
- [ ] **Error Handling**: Implements proper error handling following project standards
- [ ] **Security Practices**: Applies appropriate security measures for different types of changes
- [ ] **Performance Optimization**: Considers and implements performance best practices

### Feature Development Capability
- [ ] **Requirements Analysis**: Can break down feature requirements into implementation tasks
- [ ] **Design Decisions**: Makes appropriate technical design choices within project constraints
- [ ] **Integration Implementation**: Can integrate new features with existing system components
- [ ] **User Experience**: Considers user experience implications of implementation choices
- [ ] **Backward Compatibility**: Ensures changes don't break existing functionality

## Debugging & Troubleshooting Mastery ✅

### Investigation Skills
- [ ] **Log Analysis**: Can effectively use logs to investigate issues
- [ ] **Monitoring Tools**: Proficient with system monitoring and observability tools
- [ ] **Debugging Techniques**: Can use debugger and other tools to investigate code issues
- [ ] **Performance Profiling**: Can identify and investigate performance problems
- [ ] **Error Reproduction**: Can reproduce issues based on user reports or bug descriptions

### Problem-Solving Approach
- [ ] **Systematic Investigation**: Follows logical approach to isolate and identify root causes
- [ ] **Hypothesis Testing**: Can form and test hypotheses about potential issue causes
- [ ] **Documentation Review**: Knows where to find relevant documentation and resources
- [ ] **Code History Analysis**: Can use git history and blame to understand change context
- [ ] **Collaborative Problem Solving**: Knows when and how to involve team members in investigation

### Issue Resolution Capability
- [ ] **Fix Implementation**: Can implement appropriate fixes based on root cause analysis
- [ ] **Testing Fixes**: Thoroughly tests fixes to ensure they resolve issues without side effects
- [ ] **Prevention Measures**: Can identify and implement measures to prevent similar issues
- [ ] **Knowledge Sharing**: Documents solutions and shares knowledge with team
- [ ] **Escalation Judgment**: Knows when issues require escalation or additional expertise

## Production & Deployment Understanding ✅

### Deployment Process Knowledge
- [ ] **Deployment Pipeline**: Understands the complete deployment process from code to production
- [ ] **Environment Differences**: Aware of differences between dev, staging, and production environments
- [ ] **Deployment Verification**: Knows how to verify successful deployments
- [ ] **Rollback Procedures**: Understands when and how to execute rollback procedures
- [ ] **Deployment Scheduling**: Aware of deployment windows and scheduling considerations

### Production Monitoring
- [ ] **Health Monitoring**: Can check system health using monitoring dashboards and tools
- [ ] **Alert Understanding**: Understands different types of alerts and their significance
- [ ] **Performance Monitoring**: Can assess system performance using production metrics
- [ ] **Error Tracking**: Knows how to investigate production errors and exceptions
- [ ] **User Impact Assessment**: Can evaluate the user impact of production issues

### Incident Response Readiness
- [ ] **Incident Classification**: Can assess incident severity and priority appropriately
- [ ] **Communication Protocols**: Knows who to notify and how during production issues
- [ ] **Investigation Procedures**: Can investigate production issues following established procedures
- [ ] **Mitigation Strategies**: Understands available mitigation options for different issue types
- [ ] **Post-Incident Actions**: Knows post-incident procedures including retrospectives and improvements

## Team Collaboration & Communication ✅

### Knowledge Sharing
- [ ] **Documentation Contribution**: Actively contributes to team documentation and knowledge base
- [ ] **Code Review Participation**: Provides valuable feedback in code reviews and learns from others
- [ ] **Team Meetings**: Contributes meaningfully to technical discussions and planning meetings
- [ ] **Mentoring Capability**: Can help onboard and mentor other team members
- [ ] **Knowledge Transfer**: Effectively shares expertise and lessons learned with colleagues

### Communication Skills
- [ ] **Technical Communication**: Can explain technical concepts clearly to different audiences
- [ ] **Problem Reporting**: Reports issues and bugs with appropriate detail and context
- [ ] **Solution Proposals**: Can propose technical solutions with clear rationale
- [ ] **Status Updates**: Provides clear, concise updates on work progress and blockers
- [ ] **Cross-Team Collaboration**: Communicates effectively with other teams and stakeholders

### Professional Development
- [ ] **Continuous Learning**: Actively learns new technologies and improves existing skills
- [ ] **Industry Awareness**: Stays current with relevant industry trends and best practices
- [ ] **Feedback Reception**: Receives and applies feedback constructively
- [ ] **Initiative Taking**: Identifies and proposes improvements to processes and systems
- [ ] **Team Culture**: Contributes positively to team culture and collaborative environment

## Confidence Validation Scenarios ✅

### Practical Application Tests
- [ ] **Feature Implementation**: Successfully implement a medium-complexity feature independently
- [ ] **Bug Investigation**: Investigate and resolve a production issue with minimal guidance
- [ ] **Performance Optimization**: Identify and implement a performance improvement
- [ ] **Code Refactoring**: Refactor existing code to improve maintainability without breaking functionality
- [ ] **Integration Development**: Implement integration with a new external service or API

### Knowledge Application Scenarios
- [ ] **Architecture Explanation**: Can explain system architecture to a new team member
- [ ] **Change Impact Analysis**: Accurately assess the impact of a proposed significant change
- [ ] **Technical Decision Making**: Make appropriate technical decisions within project constraints
- [ ] **Problem-Solution Matching**: Identify appropriate solutions for different types of problems
- [ ] **Risk Assessment**: Evaluate and communicate technical risks of different approaches

### Independence Indicators
- [ ] **Self-Directed Work**: Can work independently on tasks without constant guidance
- [ ] **Resource Utilization**: Effectively uses available resources (documentation, tools, team knowledge)
- [ ] **Decision Making**: Makes good technical decisions and knows when to seek input
- [ ] **Quality Ownership**: Takes ownership of code quality and follows testing best practices
- [ ] **Proactive Communication**: Communicates proactively about progress, blockers, and discoveries

## Scoring and Assessment

### Competency Levels
- **90-100% Complete**: **Expert Level** - Ready for complex tasks and mentoring others
- **80-89% Complete**: **Proficient Level** - Ready for independent work with occasional guidance
- **70-79% Complete**: **Developing Level** - Can work independently on routine tasks
- **60-69% Complete**: **Basic Level** - Needs continued mentoring and guidance
- **Below 60%**: **Novice Level** - Requires intensive mentoring and structured learning

### Critical Competencies
These areas are essential and must be at least 80% complete:
- Business Context Understanding
- Technical Architecture Mastery  
- Development Workflow Proficiency
- Change Implementation Confidence
- Debugging & Troubleshooting Mastery

### Usage Guidelines

**For Onboarding Mentors:**
- Use this checklist to plan and track onboarding progress
- Focus on critical competencies first, then fill in supporting areas
- Validate understanding through practical application, not just theoretical knowledge

**For Engineers:**
- Use as self-assessment tool to identify learning priorities
- Seek specific help in areas where you're below 70% confidence
- Practice scenarios and hands-on application to build real competence

**For Team Leads:**
- Use to assess readiness for different types of task assignments
- Identify team knowledge gaps and training opportunities
- Plan career development paths based on competency assessment

This checklist ensures engineers develop not just surface familiarity, but deep, practical competence that enables confident, independent contribution to any project! 🚀