Agent skill

Technical Roadmap Planning

by tmcfarlane in tmcfarlane/oh-my-cursor

Create comprehensive technical roadmaps aligned with business goals.

MITAuto-check passedProduct & Project Management

Install Technical Roadmap Planning

skills CLI
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/technical-roadmap-planning .claude/skills/technical-roadmap-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
technical-roadmap-planning
GitHub stars
109
Token cost
~2.5k tokens
SKILL.md length
207 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Create comprehensive technical roadmaps aligned with business goals.

  • Works in 4 steps: Roadmap Framework → Dependency Mapping → Technology Evaluation → …
  • Tasks that involve Product roadmapping
  • SKILL.md covers Overview, When to Use, Instructions and Best Practices, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Technical Roadmap Planning is an agent skill from tmcfarlane/oh-my-cursor. Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Product roadmapping. The repository describes itself as: Like “oh-my-opencode”, but for Cursor IDE. Multi-agent orchestration, natively, using nothing but a few config files. The licence is MIT.

When your agent uses it

  • Tasks that involve Product roadmapping

Example prompts

  • “/technical-roadmap-planning”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Roadmap Framework
  2. Dependency Mapping
  3. Technology Evaluation
  4. Execution Planning

What it can do on your machine

Read from SKILL.md and the folder at commit 5bad458. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, javascript and python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Technical Roadmap Planning loads about 2.5k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 207 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tmcfarlane/oh-my-cursor at commit 5bad458, republished under its MIT licence (© tmcfarlane). 207 words, ~2,508 tokens.

Download SKILL.mdSave it as .claude/skills/technical-roadmap-planning/SKILL.md (or your agent's skills folder).
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.

Technical Roadmap Planning

Overview

A technical roadmap provides a strategic plan for technology evolution, guiding architectural decisions, infrastructure investments, and capability development aligned with business objectives.

When to Use

  • Multi-year technology planning
  • Architecture modernization initiatives
  • Platform scaling and reliability improvements
  • Legacy system migration planning
  • Infrastructure upgrade scheduling
  • Technology stack standardization
  • Innovation investment planning

Instructions

1. Roadmap Framework
yaml
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)
2. Dependency Mapping
javascript
// 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'
    };
  }
}
3. Technology Evaluation
python
# 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'
        }
4. Execution Planning
yaml
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

Best Practices

✅ DO
  • Align technical roadmap with business strategy
  • Include time for technical debt reduction
  • Plan for buffer/contingency in critical paths
  • Review and update roadmap quarterly
  • Communicate roadmap transparently
  • Involve team in planning for buy-in
  • Prioritize based on business impact
  • Plan major changes during slower periods
  • Document rationale for technology choices
  • Build in learning & experimentation time
❌ DON'T
  • Pursue every new technology trend
  • Plan at 100% utilization (no buffer)
  • Ignore team capability and training needs
  • Make major changes during peak usage
  • Lock roadmap without flexibility
  • Underestimate legacy system complexity
  • Skip security considerations
  • Plan without resource availability
  • Ignore risk assessment
  • Chase technologies without business value

Roadmap Tips

  • Review roadmap quarterly, not annually
  • Use colored status indicators (On track, At risk, Blocked)
  • Show dependencies clearly in visual format
  • Keep roadmap to 3-5 major initiatives per quarter
  • Include 20% capacity for learning and debt reduction

© tmcfarlane, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/technical-roadmap-planning of tmcfarlane/oh-my-cursor.

Open the folder on GitHubat commit 5bad458

Compare with similar skills

Technical Roadmap Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Technical Roadmap Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Technical Roadmap Planning this skilltmcfarlane/oh-my-cursor109—~2.5kAutomated safety check: PassMIT
Product Strategistalirezarezvani/claude-skills28k2 repos~1.8kAutomated safety check: PassMIT
Strategic Roadmap Planningdeanpeters/Product-Manager-Skills7.2k2 repos~4.7kAutomated safety check: PassCustom licence
Walking Skeleton Roadmap Scopingprime-radiant-inc/iterative-development181—~1.7kAutomated safety check: PassApache-2.0
AI Product Strategy InterviewerPrepLabsAI/InterviewMentor112—~4.5kAutomated safety check: PassMIT
Product PlannerBuildGreatProducts/builder-os227—~4.6kAutomated safety check: PassMIT

Similar skills

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Product & Project ManagementAuto-check passed
  • Strategic Roadmap Planning

    deanpeters/Product-Manager-Skills

    Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.

    7.2k GitHub starsUsed in 2 repos~4.7k tokens
    Product & Project ManagementAuto-check passed
  • Walking Skeleton Roadmap Scoping

    prime-radiant-inc/iterative-development

    Turns extracted requirements into a roadmap by choosing a walking skeleton iteration with its first journey scenario and ordering the remaining work into follow-on iterations.

    181 GitHub stars~1.7k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed
  • AI Product Strategy Interviewer

    PrepLabsAI/InterviewMentor

    A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.

    112 GitHub stars~4.5k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Product Planner

    BuildGreatProducts/builder-os

    Vision intake conversation followed by generation of three product documents — docs/product-vision.md (strategy and brand), docs/prd.md (technical spec for coding agents), and…

    227 GitHub stars~4.6k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed
  • Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.

    103 GitHub stars~1.3k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from tmcfarlane/oh-my-cursor

All 14 skills in this repo
  • Docs Write

    tmcfarlane/oh-my-cursor

    Write documentation following Metabase's conversational, clear, and user-focused style.

    109 GitHub starsUsed in 3 repos~716 tokens
    Auto-check: notes
  • Debugging

    tmcfarlane/oh-my-cursor

    Systematic 4-phase debugging with root cause investigation. An agent skill from tmcfarlane/oh-my-cursor.

    109 GitHub stars~4.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Documentation Engineer

    tmcfarlane/oh-my-cursor

    Technical documentation expert for creating clear, comprehensive documentation.

    109 GitHub stars~881 tokensUpdated 3 mo ago
    Auto-check passed
  • Planning

    tmcfarlane/oh-my-cursor

    Technical implementation planning and architecture design. An agent skill from tmcfarlane/oh-my-cursor.

    109 GitHub stars~815 tokensUpdated 3 mo ago
    Auto-check passed
  • Codebase Search

    tmcfarlane/oh-my-cursor

    Search and navigate large codebases efficiently. An agent skill from tmcfarlane/oh-my-cursor.

    109 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check: notes
  • Cursor Image Generation

    tmcfarlane/oh-my-cursor

    Generate and iterate images in Cursor using the built-in image model and strong prompts.

    109 GitHub stars~1.8k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Technical Roadmap Planning

What does Technical Roadmap Planning do?

Create comprehensive technical roadmaps aligned with business goals. Technical Roadmap Planning is an agent skill from tmcfarlane/oh-my-cursor. Create comprehensive technical roadmaps aligned with business goals.

When should I use Technical Roadmap Planning?

Technical Roadmap Planning fits situations like: tasks that involve Product roadmapping.

How do I install Technical Roadmap Planning in Claude Code?

Run `npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a claude-code`. Or copy the skill folder (skills/technical-roadmap-planning in tmcfarlane/oh-my-cursor) into .claude/skills/technical-roadmap-planning in your project. Claude Code loads it when a task matches its description.

How do I install Technical Roadmap Planning in Codex?

Run `npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a codex`. Or copy the skill folder (skills/technical-roadmap-planning in tmcfarlane/oh-my-cursor) into .agents/skills/technical-roadmap-planning in your project. Codex loads it when a task matches its description.

Can I use Technical Roadmap Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-roadmap-planning, .gemini/skills/technical-roadmap-planning, .github/skills/technical-roadmap-planning and .opencode/skills/technical-roadmap-planning in your project.

What does Technical Roadmap Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Technical Roadmap Planning is instructions for the agent only. Our summary lists: Python 3.

Does Technical Roadmap Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Technical Roadmap Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Technical Roadmap Planning use?

Technical Roadmap Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Technical Roadmap Planning use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Technical Roadmap Planning?

Skills that share tags, products or a category with Technical Roadmap Planning: Product Strategist (alirezarezvani/claude-skills, 28k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars), Walking Skeleton Roadmap Scoping (prime-radiant-inc/iterative-development, 181 stars) and AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Technical Roadmap Planning?

tmcfarlane (a GitHub user) maintains it in tmcfarlane/oh-my-cursor, which has 109 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on July 2, 2026.

Source: tmcfarlane/oh-my-cursor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.