technical-planner

Organize software execution into sequenced phases with dependency mapping and MVP scope.

Updated May 9, 2026

Search Tags:#technical planning #risk mitigation #dependency mapping #mvp scope #phase sequencing #execution roadmap #architecture runway

Ready to run

npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill technical-planner-gustavogutierrez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-planner
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/technical-planner
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill technical-planner-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical Planner helps you convert a high-level idea or spec into a realistic, dependency-aware execution plan that prevents foundational work from being delayed and avoids building features before critical risks and unknowns are addressed.

Core Features & Use Cases

Execution-phase planning: Organizes work into sequenced phases with clear goals and exit criteria.
Dependency and risk mapping: Identifies architecture, infrastructure, data, integration, security/compliance, team coordination, and operational readiness dependencies.
Incremental MVP delivery: Defines must-have foundations and capabilities, plus what to defer, to deliver usable value early.

Quick Start

Ask an AI agent to produce a technical execution plan for your MVP by sequencing foundation work first, mapping dependencies and risks, and defining phase entry/exit criteria.

Frequently Asked Questions about technical-planner

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

FAQPage Schema

How do I create an execution roadmap from a high-level software spec?▼

An execution roadmap organizes software work into sequenced phases with clear goals, dependency mapping, and exit criteria. It sequences foundation work first and defines incremental MVP delivery phases to prevent delayed foundational work and mitigate risks early.

How do I map dependencies and risks for an MVP scope?▼

Mapping dependencies and risks for an MVP scope involves classifying architecture, infrastructure, data, integration, security, and team coordination requirements. This process identifies must-have foundations versus deferrable capabilities to ensure usable value delivery early.

What is the best way to sequence foundation work before building features?▼

Sequencing foundation work first requires organizing an execution roadmap with dependency classification and phase sequencing. This approach ensures critical risks and architecture runway unknowns are addressed before features are built, preventing foundational delays.

Can I turn a PRD or backlog into an incremental delivery plan?▼

Yes, you can turn a PRD or backlog into an incremental delivery plan by defining MVP scope, sequencing phases, and establishing verification evidence per phase. The plan maps operational readiness dependencies and uses neutral placeholders for unknown teams.

Does technical planning work for systems with unknown teams and environments?▼

Technical planning works for systems with unknown teams and environments by applying neutral placeholders for providers, teams, and environments. It maps team coordination dependencies and operational readiness requirements without blocking phase sequencing.