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.