building-interactive-prototypesTakes an approved Discovery Plan to a working, clickable prototype: presents plain-language layout options (A, B, C), builds the prototype component by component with a review after each, and walks the expert through it. Use when the user says "build the prototype", "let's build it", "show me a work
capturing-business-requirementsCaptures what a business explorer knows as structured documents: business requirements (BRD with rules, constraints, assumptions), user stories with acceptance criteria, Mermaid workflow diagrams, and prototype observation notes. Use when the user says "capture requirements", "generate a BRD", "docu
handing-off-to-engineeringCloses exploration and routes the result: assesses risk and rigor (tiers 1 to 3), writes the handoff package for the right consumer, runs read-only technical codebase discovery that produces a diagnostic brief, and scopes a re-entry when engineering finds an unresolved ambiguity. Use when the user s
reengineering-vibe-codeRescues an existing vibe-coded prototype: audits the running app, builds a characterization test safety net, consolidates specs/REQS.md, extracts a pure domain layer and migrates vertical slices with independent certification. Use when the user says "harden our local prototype", "rescue this vibe-co
running-exploration-cycleRuns the business exploration cycle end to end: starts or resumes a session (intake interview, session brief), enforces the Discovery Plan HARD-GATE, routes the four phases (Discovery Plan, Visual Blueprinting, Prototype, Handoff) to the sibling skills and keeps session state. Use when the user says