blueprint-phase-execution

Execute Blueprint plans in wave order and produce durable summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate Blueprint's execution flows to run saved plans in wave-aware order, ensuring durable summaries and reports are produced for each completed plan.

Core Features & Use Cases

  • Orchestrates wave-based plan execution and bounded quick tasks within the Blueprint lifecycle.
  • Persists durable summary artifacts and routes follow-up actions inside the Blueprint surface.
  • Provides clear guidance for state management, validation gates, and post-execution routing.

Quick Start

Instruct Blueprint to execute the saved plans in wave order and generate a durable summary artifact.

Frequently Asked Questions about blueprint-phase-execution

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

FAQPage Schema
How do I execute saved plans in wave order with state management?

Plan execution in wave order is handled by orchestrating bounded tasks sequentially, using state management tools to track progress and producing a durable summary artifact for each completed plan.

What is wave-based plan execution and when do I need it?

Wave-based plan execution is an orchestration method that runs saved plans in sequential phases. You need it when coordinating bounded quick tasks and follow-up routing within a structured lifecycle surface.

Can I enforce validation gates before and after executing plans?

Yes, the execution flow enforces pre-execution and post-execution checks. Validation gates are applied to ensure state consistency before running and durable reports are generated after each plan completes.

How do I generate durable summary artifacts for completed plans?

Durable summary artifacts are generated automatically upon plan completion. The orchestration flow persists these artifacts alongside execution reports using MCP tools for state and artifact management.

Does this workflow support safe routing to subsequent commands after execution?

Yes, safe routing to subsequent commands is supported. After post-execution checks pass, the workflow routes follow-up actions inside the Blueprint surface to ensure safe transitions between phases.

What are the limitations of bounded quick tasks within the Blueprint surface?

Bounded quick tasks are limited to the implemented Blueprint surface and cannot route outside it. Execution is constrained to wave-order phases, meaning out-of-sequence tasks require separate validation gates.