meridian-blueprint

Convert a prioritized Meridian idea into a developer-ready technical design.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-blueprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meridian-blueprint
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.agents/skills/meridian-blueprint
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-blueprint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents promising Meridian ideas from stalling by turning a single prioritized input into an implementable, contract-grounded design that the developer can execute immediately.

Core Features & Use Cases

  • Blueprints Meridian features end-to-end: produces a code-ready technical design with scope, architecture overview, interface & API contracts, component design, data flow, and UI/XAML sketches when relevant.
  • Supports three delivery depths: full (complete 9-section blueprint), spike (riskiest unknowns first with a PoC plan), and interface-only (contracts-first alignment).
  • Integrates with Meridian’s ideation-to-implementation pipeline: fits after Brainstorm/Roadmap Builder and before code review and test writing, enabling a structured handoff.
  • Produces implementation artifacts on demand: generates a step-by-step implementation checklist and a named test plan, and can also emit an optional blueprint.json summary when requested.

Quick Start

Use the blueprint mode to design “the feature you want” by providing one idea card or idea title, along with the desired depth (full, spike, or interface-only).

Frequently Asked Questions about meridian-blueprint

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

FAQPage Schema
How do I turn a feature idea into a build-ready technical design for .NET and WPF?

To turn a feature idea into a build-ready technical design, provide a single prioritized idea to generate scoped architecture, interface contracts, data flow, and UI/XAML sketches aligned with .NET 10 structure and WPF/browser UI integration.

Can I generate API contracts and interface designs before writing code?

Yes, you can generate API contracts and interface designs before writing code by using the interface-only delivery depth, which prioritizes contracts-first alignment for your technical design.

What is the best way to plan a spike or proof of concept for a new feature?

The best way to plan a spike or proof of concept is using the spike delivery depth, which identifies the riskiest unknowns first and produces a targeted PoC plan and implementation checklist.

Does this approach support EventPipeline conventions and bounded channels?

Yes, the technical blueprinting approach supports EventPipeline conventions and bounded channels by explicitly honoring Meridian stack patterns, cancellation/token rules, and the Options pattern in the design.

How do I create a test plan and implementation checklist for a technical blueprint?

You create a test plan and implementation checklist by generating a complete technical design blueprint, which explicitly includes a named test plan and step-by-step implementation artifacts on demand.

When do I need a full technical blueprint versus interface-only contracts?

You need a full technical blueprint for complete end-to-end feature design with architecture and data flow, whereas interface-only contracts suffice for quick API alignment without generating the complete nine-section design.