Skip to content
Skills Library
Management & product · Planning

implementation-roadmaps

/implementation-roadmaps

Create or improve a phased product or engineering roadmap with milestones and dependencies. Use when organizing a larger initiative, sequencing releases, or turning a strategy into trackable work.

Repository
skillsmo ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create or improve a phased product or engineering roadmap with milestones and dependencies. Use when organizing a larger initiative, sequencing releases, or turning a strategy into trackable work.

Original author description

Create or improve a phased product or engineering roadmap with milestones and dependencies. Use when organizing a larger initiative, sequencing releases, or turning a strategy into trackable work.

How it works

  1. Goal
  2. Workflow
  3. Decision rules
  4. Boundaries
  5. Completion standard
  6. Further reading
Original SKILL.md headings · 35 lines, 232 words
SKILL.md preview
---
name: implementation-roadmaps
description: "Create or improve a phased product or engineering roadmap with milestones and dependencies. Use when organizing a larger initiative, sequencing releases, or turning a strategy into trackable work."
---

# Implementation roadmap design

## Goal

Make a roadmap that communicates outcomes, sequence, dependencies, and evidence without implying false certainty.

## Workflow

1. Define the audience, planning horizon, product outcome, scope, and constraints.
2. Group work by user or system outcome rather than by a flat list of technical activities.
3. Sequence milestones using dependencies, risk reduction, learning value, and team capacity.
4. For each milestone, state the outcome, deliverables, acceptance evidence, dependencies, and explicit exclusions.
5. Add decision points and review dates for uncertain work; identify what would change the order or scope.

## Decision rules

- Separate committed work from exploratory opportunities and unprioritized ideas.
- Use relative order or ranges when dates are uncertain; do not invent precision.
- Prefer an early milestone that tests the riskiest assumption or integration.

## Boundaries

- Do not represent estimates as commitments unless the owner confirms them.
- Do not use a roadmap as a substitute for implementation-level acceptance criteria.

## Completion standard

Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request.

## Further reading

- [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases.
- [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
  • SKILL.md 2 KB
  • references/field-guide.md 1 KB
  • references/source-notes.md 1 KB

Versions

The database has no other skills named implementation-roadmaps.

Database snapshot: 13.11.2026 · package version e55801cbca25 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90integrated-roadmap
    Integrates every AI programme workstream plan - adoption, Champions, learning, knowledge, platform, agent delivery, governance and value - into one dated delivery plan with milestones, a critical path, cross-workstream dependencies and a baseline that changes only by decision.…
  • 100timeline-creator
    Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
  • 100unikit-roadmap
    Create or update a strategic project roadmap with major milestones. Generates .unikit/ROADMAP.md — a high-level checklist of project goals. Use when user says "roadmap", "project plan", "milestones", "what to build next", "strategic goals", or wants to see big-picture progress.…
  • 90program-planning
    Creates program plans with timelines, milestones, dependencies, and critical path analysis. Use when starting a new program or replanning an existing one.
  • 100timeline
    Writes valid timeline JSON for uml-mcp (diagram_type=timeline, bundled plugin timeline). Use when the user asks for a project timeline, product roadmap or Gantt-style plan with swimlanes, milestones and dependencies; then call validate_uml, then generate_uml_image (chat PNG) or…
  • 10090-day-plan-builder
    Use when a founder has diagnosed their AI adoption blockers and picked a first use case, and now needs a phased rollout plan with milestones aligned to board reporting cycles

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.