roadmap

Generate a milestone-driven execution alignment document with roadmap, risk log, and kickoff agenda.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill roadmap-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roadmap
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/align/roadmap
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill roadmap-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams entering Sprint 1 often lack a single, signed artifact that aligns everyone on timeline, milestones, risks, roles, and communication, leading to scope creep and misaligned expectations. This Skill consolidates roadmap planning, risk management, and kickoff preparation into one 2-3 page Execution Alignment document gated by human signature. ## Core Features & Use Cases - Milestone-Driven Roadmap: Generates a sprint-by-sprint plan with concrete success criteria and named approvers per milestone, ending with a hardening and go-live sprint containing no new features. - Managed Risk Log: Produces a maximum-10 risk register ordered by impact, with mandatory scope-creep risk, concrete mitigations, and named individual owners. - Kickoff Agenda: Builds a 60-90 minute kickoff agenda including a mandatory Won't v1 scope walkthrough and explicit go/no-go success criteria. - Use Case: After your prioritized backlog and software architecture document are signed, invoke this Skill to produce the Execution Alignment document that the Product Owner signs before Sprint 1 begins. ## Quick Start Ask the agent to generate the Execution Alignment roadmap for your project using the signed backlog and software architecture document, providing your start date, go-live target, and team composition.

Frequently Asked Questions about roadmap

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

FAQPage Schema
How do I create a project roadmap before Sprint 1?▼

Invoke the roadmap skill after your backlog and software architecture document are signed. Provide the start date, go-live target, team composition, and sprint structure, and it generates a milestone-driven roadmap with success criteria and named approvers.

What should a sprint risk log include?▼

A risk log should contain at most 10 risks ordered by impact, each with probability, a concrete mitigation action, and a named individual owner. A scope creep risk with a change-control process is mandatory in this document.

What documents are required before generating the execution alignment roadmap?▼

Two signed documents are required: the prioritized backlog with US-XXX stories, sprint assignments, and Won't v1 list, plus the software architecture document with component breakdown, technology stack, and deployment model.

Can the last sprint include new feature stories?▼

No. The final sprint is reserved for hardening and go-live only, covering UAT fixes, performance optimization, security review, and deployment. Any new stories must move to Should Have or the Won't v1 list.

Who approves and signs the execution alignment document?▼

The Product Owner holds final approval authority and signs the document. The Sponsor approves the go-live timeline and investment, and the Tech Lead validates sprint structure and risk mitigations.