blueprint

Produces an approved implementation design from a spec before any code is written.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill blueprint-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/sandsower/beislid/tree/main/skills/blueprint
Command: npx skills add https://github.com/sandsower/beislid --skill blueprint-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents coding agents from jumping straight into implementation by enforcing a design-first gate: requirements are validated, approaches are compared, and the user must approve a design before any code is written. ## Core Features & Use Cases - Hard approval gate: Blocks all implementation code, scaffolding, and implementation actions until the user explicitly approves a presented design. - Structured design process: Loads spec or Work Contract context, checks scope classification, asks implementation questions one at a time, and proposes 2-3 approaches with trade-offs and a recommendation. - Lifecycle integration: Runs configured blueprint_approved lifecycle actions (design artifact writes, CLI hooks) from .beislid/workflow.md, then hands off to the implement skill. - Use Case: After a product spec is approved for a new API endpoint, invoke this skill to explore the existing codebase, compare architecture options, agree on data flow and tests, and record an approved design artifact before implementation begins. ## Quick Start Ask the agent to plan the implementation for the approved spec and approve one of the proposed design approaches before any code is written.

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I plan an implementation before writing code with an AI agent?▼

Invoke the blueprint skill after your spec is approved. It loads the spec or Work Contract, asks implementation questions one at a time, proposes 2-3 approaches with trade-offs, and waits for your explicit approval before any code is written.

What is the difference between spec and blueprint skills?▼

The spec skill defines what product should exist: problem, users, and success criteria. Blueprint starts only after desired behavior is known and decides how to build it: architecture, files, data flow, and tests. Vague requirements are routed back to spec.

Can blueprint write code or scaffold files automatically?▼

No. A hard gate forbids implementation code, scaffolding, or implementation actions until a design is presented and explicitly approved. After approval it runs configured lifecycle actions and transitions to the implement skill.

When should work be routed to break-spec instead of blueprint?▼

When scope classification is multi_slice without a selected phase, or project-sized work without an approved boundary. Blueprint handles atomic and single_pr scopes directly; larger work must be split first.

Does blueprint support writing design documents to the repo?▼

Yes, but only through configured blueprint_approved lifecycle actions in .beislid/workflow.md. Artifact actions write Markdown design files under paths like plans/{feature}-design.md, with prompt or auto approval modes and policy checks.