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.
Create comprehensive technical roadmaps aligned with business goals.
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "technical-roadmap-planning" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planning into .claude/skills/technical-roadmap-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-roadmap-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/technical-roadmap-planning .agents/skills/technical-roadmap-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-roadmap-planning" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planning into .agents/skills/technical-roadmap-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-roadmap-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/technical-roadmap-planning .cursor/skills/technical-roadmap-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-roadmap-planning" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planning into .cursor/skills/technical-roadmap-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-roadmap-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tmcfarlane/oh-my-cursor.git --path skills/technical-roadmap-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/technical-roadmap-planning .gemini/skills/technical-roadmap-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-roadmap-planning" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planning into .gemini/skills/technical-roadmap-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-roadmap-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/technical-roadmap-planning .github/skills/technical-roadmap-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-roadmap-planning" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planning into .github/skills/technical-roadmap-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-roadmap-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tmcfarlane/oh-my-cursor --skill technical-roadmap-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tmcfarlane/oh-my-cursor technical-roadmap-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/technical-roadmap-planning .opencode/skills/technical-roadmap-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-roadmap-planning" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/technical-roadmap-planning into .opencode/skills/technical-roadmap-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-roadmap-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
technical-roadmap-planningCreate 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. 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.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 5bad458. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from tmcfarlane/oh-my-cursor at commit 5bad458, republished under its MIT licence (© tmcfarlane). 207 words, ~2,508 tokens.
.claude/skills/technical-roadmap-planning/SKILL.md (or your agent's skills folder).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© tmcfarlane, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/technical-roadmap-planning of tmcfarlane/oh-my-cursor.
Open the folder on GitHubat commit 5bad458
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Roadmap Planning this skilltmcfarlane/oh-my-cursor | 109 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Product Strategistalirezarezvani/claude-skills | 28k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Strategic Roadmap Planningdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.7k | Automated safety check: Pass | Custom licence | |
| Walking Skeleton Roadmap Scopingprime-radiant-inc/iterative-development | 181 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| AI Product Strategy InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Product PlannerBuildGreatProducts/builder-os | 227 | — | ~4.6k | Automated safety check: Pass | MIT |
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.
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
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.
PrepLabsAI/InterviewMentor
A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.
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…
avelikiy/great_cto
Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.
tmcfarlane/oh-my-cursor
Write documentation following Metabase's conversational, clear, and user-focused style.
tmcfarlane/oh-my-cursor
Systematic 4-phase debugging with root cause investigation. An agent skill from tmcfarlane/oh-my-cursor.
tmcfarlane/oh-my-cursor
Technical documentation expert for creating clear, comprehensive documentation.
tmcfarlane/oh-my-cursor
Technical implementation planning and architecture design. An agent skill from tmcfarlane/oh-my-cursor.
tmcfarlane/oh-my-cursor
Search and navigate large codebases efficiently. An agent skill from tmcfarlane/oh-my-cursor.
tmcfarlane/oh-my-cursor
Generate and iterate images in Cursor using the built-in image model and strong prompts.
Categories
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.
Technical Roadmap Planning fits situations like: tasks that involve Product roadmapping.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Technical Roadmap Planning is instructions for the agent only. Our summary lists: Python 3.
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.
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.
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.
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.
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.
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.