القائمة
Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Systematic 4-phase debugging with root cause investigation. Use when fixing bugs to prevent random fixes.
Generate and iterate images in Cursor using the built-in image model and strong prompts. Use when creating icons, illustrations, UI mockups, diagrams, marketing visuals, or any raster asset from a text description or reference image.
Search and navigate large codebases efficiently. Use when finding specific code patterns, tracing function calls, understanding code structure, or locating bugs. Handles semantic search, grep patterns, AST analysis.
Apply appropriate design patterns (Singleton, Factory, Observer, Strategy, etc.) to solve architectural problems. Use when refactoring code architecture, implementing extensible systems, or following SOLID principles.
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.
| name | technical-roadmap-planning |
| description | Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years. |
A technical roadmap provides a strategic plan for technology evolution, guiding architectural decisions, infrastructure investments, and capability development aligned with business objectives.
Technical Roadmap Template:
Organization: [Company]
Planning Period: 2025-2027
Last Updated: January 2025
Owner: CTO / VP Engineering
---
Vision Statement: |
Transform our technology platform to enable global scale, improve
developer productivity, and deliver world-class customer experiences
through modern, cloud-native architecture.
Strategic Goals:
1. Reduce infrastructure costs by 40% through cloud optimization
2. Improve deployment frequency from monthly to daily
3. Achieve 99.99% availability (4 nines)
4. Enable data-driven decision making across organization
---
## Q1 2025: Foundation & Planning
Theme: Infrastructure Foundation
Initiatives:
- Kubernetes Migration Phase 1
Status: In Progress
Team: 4 DevOps engineers
Expected Completion: March 31
Business Impact: 30% cost reduction
Risks: Learning curve, resource constraints
- Database Modernization Planning
Status: Planning
Team: Data Engineering
Expected Completion: February 28
Business Impact: 10x query performance
Blockers: Vendor selection
---
## Q2 2025: Execution Phase 1
Theme: Scale & Performance
Initiatives:
- Kubernetes Migration Phase 2
Dependency: Q1 completion
Team: 5 engineers
Expected Completion: June 30
Risk Level: Medium
- Microservices Architecture
Team: Architecture + Development
Expected Completion: May 31
Effort: 3 person-months
Strategic Impact: High
- Redis Caching Layer
Team: 2 engineers
Expected Completion: April 30
Estimated Impact: 50% faster API responses
---
## Q3 2025: Execution Phase 2
Theme: Reliability & Observability
Initiatives:
- Observability Platform (ELK/DataDog)
- Chaos Engineering & Resilience Testing
- Multi-region Deployment Capability
- Database Sharding Strategy Implementation
---
## Q4 2025: Consolidation & Planning
Theme: Stabilization & Innovation
Initiatives:
- Platform Stabilization & Bug Fixes
- Developer Experience Improvements
- 2026 Strategic Planning
---
## 2026-2027 Vision
Long-term Initiatives (Candidate):
- AI/ML Platform Development
- Real-time Data Pipeline
- Graph Database Evaluation
- Blockchain Integration (Future)
// Technical dependency management
class RoadmapDependency {
constructor() {
this.initiatives = [];
this.dependencies = [];
}
mapDependencies(initiatives) {
const dependencyMap = {};
initiatives.forEach(init => {
dependencyMap[init.id] = {
name: init.name,
dependsOn: init.blockedBy || [],
enables: init.enables || [],
criticalPath: init.criticalPath || false,
startDate: init.plannedStart,
endDate: init.plannedEnd,
buffer: init.buffer || '2 weeks'
};
});
return this.validateDependencies(dependencyMap);
}
validateDependencies(dependencyMap) {
const issues = [];
for (let init in dependencyMap) {
const current = dependencyMap[init];
// Check for circular dependencies
if (this.hasCircularDependency(init, current.dependsOn, dependencyMap)) {
issues.push({
type: 'Circular Dependency',
initiative: current.name,
severity: 'Critical'
});
}
// Check for timeline conflicts
current.dependsOn.forEach(dep => {
const depInit = dependencyMap[dep];
if (depInit && depInit.endDate > current.startDate) {
issues.push({
type: 'Timeline Conflict',
initiative: current.name,
blockedBy: depInit.name,
gap: this.calculateGap(depInit.endDate, current.startDate),
severity: 'Medium'
});
}
});
}
return {
dependencyMap,
issues,
isValid: issues.length === 0
};
}
hasCircularDependency(node, deps, map, visited = new Set()) {
if (visited.has(node)) return true;
visited.add(node);
for (let dep of deps) {
if (this.hasCircularDependency(dep, map[dep]?.dependsOn || [], map, visited)) {
return true;
}
}
return false;
}
calculateCriticalPath(dependencyMap) {
// Identify longest dependency chain
let criticalPath = [];
let maxDuration = 0;
for (let init in dependencyMap) {
const duration = this.calculatePathDuration(init, dependencyMap);
if (duration > maxDuration) {
maxDuration = duration;
criticalPath = this.getPath(init, dependencyMap);
}
}
return {
path: criticalPath,
duration: maxDuration,
initiatives: criticalPath,
delayImpact: 'All dependent initiatives delayed'
};
}
}
# Technology selection framework
class TechnologyEvaluation:
EVALUATION_CRITERIA = {
'Maturity': {'weight': 0.15, 'factors': ['Adoption', 'Stability', 'Support']},
'Performance': {'weight': 0.20, 'factors': ['Throughput', 'Latency', 'Scalability']},
'Integration': {'weight': 0.15, 'factors': ['Existing Stack', 'APIs', 'Ecosystem']},
'Cost': {'weight': 0.15, 'factors': ['License', 'Infrastructure', 'Maintenance']},
'Team Capability': {'weight': 0.15, 'factors': ['Learning Curve', 'Skills Available', 'Training']},
'Vendor Stability': {'weight': 0.10, 'factors': ['Company Health', 'Roadmap', 'Support']},
'Security': {'weight': 0.10, 'factors': ['Compliance', 'Vulnerabilities', 'Updates']}
}
@staticmethod
def evaluate_technology(tech_option, scores):
"""
Score technology on weighted criteria
Each criterion scored 1-10
"""
total_score = 0
for criterion, score in scores.items():
weight = TechnologyEvaluation.EVALUATION_CRITERIA[criterion]['weight']
weighted = score * weight
total_score += weighted
return {
'technology': tech_option,
'weighted_score': round(total_score, 2),
'recommendation': 'Recommended' if total_score > 7 else 'Consider alternatives'
}
@staticmethod
def create_comparison_matrix(technologies):
"""Create side-by-side comparison"""
return {
'evaluation_date': str(datetime.now()),
'technologies': technologies,
'criteria': TechnologyEvaluation.EVALUATION_CRITERIA,
'results': []
}
@staticmethod
def technology_debt_score(technology):
"""Assess technology debt risk"""
return {
'maintenance_burden': 'Low' if technology['support_available'] else 'High',
'replacement_cost': 'Low' if technology['replaceable'] else 'High',
'knowledge_risk': 'Low' if technology['team_familiar'] else 'High',
'overall_debt_score': 'Medium'
}
Initiative Execution Plan:
Initiative: Kubernetes Migration
Quarter: Q1-Q2 2025
Owner: VP Infrastructure
---
Phase 1: Planning & Preparation (Jan-Feb)
Milestones:
- Week 1: Team assembled, knowledge transfer
- Week 2: Infrastructure provisioning
- Week 3: Proof of concept deployment
- Week 4-8: Detailed planning & tooling setup
Success Criteria:
- POC running production workload
- Migration runbook completed
- Team trained and certified
- No blockers identified
---
Phase 2: Pilot Deployment (Mar-Apr)
Target: Non-critical workloads first
Success: All pilots running successfully
Rollback Plan: Full rollback to current infrastructure
Services Migrating:
- Analytics pipeline
- Logging service
- Cache layer
- Message queue
---
Phase 3: Production Migration (May-Jun)
Order of Migration:
1. Legacy services (lower risk)
2. Core services (higher stakes)
3. Customer-facing APIs (last)
Validation: Zero downtime, 99.9% success rate
---
Success Metrics:
- Infrastructure cost reduced by 30%
- Deployment time reduced by 50%
- Zero security incidents
- 98% uptime during migration