blueprint-roadmap-admin

Coordinate Blueprint roadmap mutations, milestone audits, and state evolution.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/rakole/blueprint --skill blueprint-roadmap-admin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint-roadmap-admin
Source: https://github.com/rakole/blueprint/tree/main/skills/blueprint-roadmap-admin
Command: npx skills add https://github.com/rakole/blueprint --skill blueprint-roadmap-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates roadmap mutations, milestone audits, and state evolution to keep project plans durable and auditable.

Core Features & Use Cases

  • Coordinate roadmap mutations (add/insert/remove phases) with deterministic numbering and scaffolding.
  • Audit milestones, plan gaps, and milestone summaries to keep state aligned with durable artifacts.
  • Route changes through the Blueprint MCP workflow to ensure provenance, traceability, and recoverability.

Quick Start

Start by running /blu-help to load the Roadmap Admin surface and begin mutating your blueprint roadmap.

Frequently Asked Questions about blueprint-roadmap-admin

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

FAQPage Schema
How do I coordinate roadmap mutations when adding or removing project phases?

Coordinate roadmap mutations by enforcing deterministic phase numbering, explicit confirmations, and scaffold creation. This ensures durable, auditable project plans with proper traceability and recoverability.

How do I audit project milestones and plan gaps in a blueprint roadmap?

Audit milestones by enforcing MCP-tool requirements and explicit confirmations, returning authoritative phase metadata and artifact paths to keep state aligned with durable artifacts.

What is the best way to ensure deterministic changes when completing project milestones?

Ensure deterministic milestone completion by enforcing explicit confirmations, scaffold creation, and final state routing to the next safe action, returning authoritative phase metadata and artifact paths.

Do I need MCP tools to manage blueprint roadmap state evolution and phase scaffolding?

Yes, MCP tools are required. The workflow enforces MCP-tool dependencies to ensure provenance, traceability, and recoverability of all phase mutations and milestone audits.

Can I insert a new phase into an existing roadmap without breaking milestone state alignment?

Yes, inserting phases uses deterministic numbering and scaffold creation to prevent breaking milestone state alignment, routing changes through explicit confirmations to the next safe action.

When should I not use automated roadmap mutations for project phase management?

Avoid automated roadmap mutations when lacking MCP workflow infrastructure to support provenance, traceability, and recoverability of phase artifacts, as explicit confirmations and MCP-tool dependencies are required.