blueprint-phase-discovery

Coordinate pre-planning discovery for the Blueprint lifecycle with MCP reads and writes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Blueprint Phase Discovery orchestrates pre-planning discovery for the Blueprint lifecycle, anchoring phase scope, required artifacts, and evidence so teams can proceed with confidence.

Core Features & Use Cases

  • Orchestrates MCP-owned phase discovery artifacts and state transitions for the blueprint lifecycle
  • Normalizes and routes discovery output through canonical contracts and artifact writes
  • Provides checkpointing, evidence density, and gray-area scoping to support planning and risk assessment
  • Supports common discovery flows: /blu-discuss-phase, /blu-research-phase, /blu-ui-phase, and /blu-plan-phase to keep work aligned

Quick Start

Run /blu-discuss-phase to begin a discovery cycle and seed the initial phase context.

Frequently Asked Questions about blueprint-phase-discovery

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

FAQPage Schema
How do I coordinate pre-planning discovery for a project blueprint lifecycle?

Pre-planning discovery coordinates phase scope, research, and UI-spec planning to anchor artifacts. It enforces deterministic MCP reads and writes while normalizing outputs to canonical authoring templates for planner-ready persistence.

What is MCP artifact checkpointing and when do I need it for phase planning?

MCP artifact checkpointing captures evidence density and gray-area scoping to support planning and risk assessment. It is needed when orchestrating phase discovery state transitions to ensure work remains aligned across workflows.

How do I start a discovery cycle to gather assumptions and seed phase context?

Run the /blu-discuss-phase workflow command to begin a discovery cycle and seed the initial phase context. This initiates the orchestration of MCP-owned phase discovery artifacts and state transitions.

Can I use MCP commands for UI-spec planning and phase research?

Yes, MCP commands support common discovery flows including /blu-research-phase and /blu-ui-phase. These workflows route discovery output through canonical contracts and artifact writes to keep work aligned.

Do I need to normalize discovery output before persisting MCP artifacts?

Yes, final normalization to canonical authoring templates is required before persistence. This ensures deterministic MCP reads and writes maintain consistent artifact contracts across the blueprint lifecycle.

What are the limitations of using blueprint phase discovery for workflow planning?

Blueprint phase discovery is limited to pre-planning orchestration and does not execute the actual build phase. It requires strict adherence to deterministic MCP reads and writes, meaning non-canonical artifact formats are not persisted.