blueprint-router

Route user inputs to implemented Blueprint commands and surface waiting state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routing generic user requests to the safest implemented Blueprint runtime commands and surfacing the current waiting state to prevent exposure to planned or blocked surface commands.

Core Features & Use Cases

  • Safe, implementation-aware routing that prioritizes implemented commands over planned or blocked ones.
  • Context-aware guidance for ambiguous requests, preserving the runtime surface integrity.
  • State visibility: reveal the current waiting state and prerequisites needed to proceed with routing decisions.

Quick Start

Route a root '/blu' request to the safest implemented command and surface the current waiting state to guide the next action.

Frequently Asked Questions about blueprint-router

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

FAQPage Schema
How do I route user inputs to safe Blueprint commands at runtime?

Blueprint routing directs user inputs to the safest implemented command surface by filtering out planned or blocked commands, ensuring only operational subcommands are exposed during runtime execution.

What is safe CLI routing for Blueprint subcommands?

Safe CLI routing for Blueprint subcommands is the process of mapping generic user requests to implemented '/blu' commands while preventing exposure to unimplemented or planned runtime command surfaces.

How do I get context-aware guidance for ambiguous Blueprint CLI requests?

Context-aware guidance for ambiguous Blueprint CLI requests is provided by evaluating the request against implemented commands and surfacing the current waiting state and prerequisites needed to proceed.

Can I use runtime gating constraints to hide planned Blueprint commands?

Yes, runtime gating constraints filter the Blueprint command surface to hide planned or blocked commands, ensuring only implemented and safe commands are surfaced to the user during execution.

Why does Blueprint routing expose the current waiting state during command execution?

Blueprint routing exposes the current waiting state to provide state visibility, revealing the exact prerequisites needed to proceed with routing decisions and preventing users from hitting blocked command paths.

What are the limitations of routing generic requests to Blueprint command surfaces?

Routing limitations include strict adherence to runtime gating constraints and parity goals, meaning requests cannot bypass the filter to access planned commands or commands lacking the required inputs and tools described in the manifest.