meridian-roadmap-strategist

Name: meridian-roadmap-strategist
Availability: InStock
Author: rodohasarrived

Reconcile Meridian roadmap artifacts with repository evidence and dependency-aware next waves.

Updated Mar 23, 2026

Search Tags:#roadmap #product strategy #opportunity mapping #target state #evidence-based planning #delivery waves #Meridian

Ready to run

npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-roadmap-strategist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meridian-roadmap-strategist
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.agents/skills/meridian-roadmap-strategist
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-roadmap-strategist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Meridian roadmap updates often drift from the actual state of evidence across docs, status, and code, creating confusion about what is truly complete, what remains open, and what the end-state product should be.

Core Features & Use Cases

Roadmap artifact generation and refresh: Creates or updates master roadmap, time-boxed plans, delivery waves, and opportunity maps grounded in current repository evidence.
Evidence reconciliation across planning sources: Separates items into complete, partial, planned, and optional while resolving conflicts across roadmap, plans, audit/evaluations, and status docs.
Target-state narrative and next waves: Produces a crisp end-product description and dependency-aware sequencing, turning gaps into prioritized opportunities.

Quick Start

Use Meridian Roadmap Strategist to refresh the active roadmap and provide a prioritized “what remains” plus “next waves” for the next delivery horizon.

Frequently Asked Questions about meridian-roadmap-strategist

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

FAQPage Schema

How do I create a product roadmap grounded in actual repository evidence?▼

You can generate a reconciled target-state product roadmap by reading shared project context and source-map references, classifying work into complete, partial, planned, and optional states, and reconciling conflicts across planning documents.

What is the best way to reconcile conflicting product strategy items across planning docs?▼

Reconciling conflicting product strategy items involves classifying work into complete, partial, planned, and optional categories, resolving discrepancies across roadmap and audit documents, and emitting dependency-aware opportunities.

How do I map remaining delivery waves from existing project status documents?▼

To map remaining delivery waves, summarize remaining work, identify dependency-aware sequencing from current gaps, and turn those gaps into prioritized opportunities for the next delivery horizon.

Can I generate a target-state product direction summary from opportunity mapping?▼

Yes, you can generate a target-state product direction summary by scanning opportunity maps, reconciling current evidence, and producing a crisp end-product description with dependency-aware next waves.

Does evidence-based planning require specific source-map references to work?▼

Yes, evidence-based planning requires reading shared project context and roadmap source-map references to separate items accurately and reconcile conflicts across planning, audit, and status documents.