One-click install
npx skills add https://github.com/PSkinnerTech/lenny-skills --skill technical-roadmaps-pskinnertech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-roadmaps
Source: https://github.com/PSkinnerTech/lenny-skills/tree/main/skills/technical-roadmaps
Command: npx skills add https://github.com/PSkinnerTech/lenny-skills --skill technical-roadmaps-pskinnertech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates actionable technical roadmaps that guide engineering work and align it with product strategy.

Core Features & Use Cases

  • Apply the Rumelt framework to structure technical roadmaps with Diagnosis, Guiding Policies, and Actions.
  • Define a standard toolkit of approved tools, practices, and documentation to reduce tool sprawl.
  • Use case examples include planning architecture, prioritizing tech debt, and aligning cross-functional teams with the roadmap.

Quick Start

Describe your current architecture, tech debt priorities, team size, and business constraints to generate a first-cut technical roadmap.

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 with product strategy?

A technical roadmap aligns engineering work with product strategy by applying the Rumelt framework. It structures plans into Diagnosis, Guiding Policies, and Actions, ensuring cross-functional teams understand architectural goals and technical debt priorities.

What is the best way to prioritize tech debt in an engineering roadmap?

The best way to prioritize tech debt in an engineering roadmap is using the Rumelt framework's diagnosis phase. By evaluating current architecture and business constraints, you can identify which technical debt issues most impact product strategy and require immediate action.

How do I use the Rumelt framework for engineering planning?

To use the Rumelt framework for engineering planning, structure your technical roadmap into Diagnosis, Guiding Policies, and Actions. This approach identifies architectural problems, sets standard toolkits, and defines actionable steps to align cross-functional teams.

What do I need to generate a technical roadmap for cross-functional teams?

Generating a technical roadmap for cross-functional teams requires a documented starter roadmap detailing current architecture, tech debt priorities, team size, and business constraints. These inputs drive strategy alignment and actionable engineering planning.

Can I use this approach to reduce tool sprawl across engineering teams?

Yes, you can reduce tool sprawl by using the technical roadmap to define a standard toolkit of approved tools and practices. Establishing guiding policies ensures cross-functional teams adhere to consistent documentation and engineering standards.