technical-roadmaps

Create technical roadmaps using the Rumelt framework for engineering alignment.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill technical-roadmaps-cvillamarp-lgtm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-roadmaps
Source: https://github.com/cvillamarp-lgtm/skillspodcast/tree/main/skills/technical-roadmaps
Command: npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill technical-roadmaps-cvillamarp-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technical roadmaps translate vague goals into concrete, documented plans that guide engineering choices and allocation of resources.

Core Features & Use Cases

  • Structured planning: Use Rumelt's framework to frame Diagnosis, Guiding Policies, and Actions.
  • Alignment and documentation: Create a standard roadmap that ties tech work to business outcomes.
  • Scenarios: Prioritizing tech debt, architecture decisions, platform migrations, and tooling standards across teams.

Quick Start

Draft a 12-week technical roadmap for migrating a monolithic app to a microservices architecture with milestones, owners, and risk notes.

Frequently Asked Questions about technical-roadmaps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a technical roadmap that aligns engineering work with product strategy?

Structure a technical roadmap by applying the Rumelt framework to define Diagnosis, Guiding Policies, and Actions. This translates vague product goals into concrete engineering plans that tie tech work directly to business outcomes.

What is the Rumelt framework and how does it apply to engineering management prioritization?

The Rumelt framework is a strategy structuring method that segments plans into Diagnosis, Guiding Policies, and Actions. It applies to engineering management by providing a standard toolkit to reduce sprawl and prioritize tech debt or architecture decisions across teams.

How do I plan a platform migration roadmap with milestones and risk notes?

Plan a platform migration roadmap by drafting a structured timeline, such as a 12-week plan, that includes specific milestones, owners, and risk notes. This ensures architecture decisions and tooling standards are documented and actionable across teams.

Can I use this approach for prioritizing tech debt across multiple teams?

Yes, you can use this approach for prioritizing tech debt across multiple teams. It produces a standard roadmap that aligns engineering work with product strategy, reducing sprawl and ensuring consistent tooling standards.

What is the best way to document architecture decisions and tooling standards?

The best way to document architecture decisions and tooling standards is using a structured framework like Rumelt. It creates a standard roadmap toolkit that reduces sprawl and clearly aligns technical choices with business outcomes.