Turns the user's goal (or /bdbrainstorm / /grill-me output) into a system plan. Reads existing architecture before proposing changes. Does not coordinate execution or invoke other agents — that is TechLead's job, decided by the dispatcher, not by Architect.
Release Gatekeeper, QA & Verification Auditor. Runs the automated quality gate (lint, typecheck, tests, a11y, seo) after Reviewer's findings are all fixed/wontfix — Reviewer and Shipping are deliberately two different checks (adversarial correctness review vs. mechanical gate execution), not one merged step. Ensures…
Adversarial review of build-node output against the plan's stated contract, before Shipping runs its automated gate. Modeled on the doubt-driven-development discipline (see .agents/graph.md): reads the artifacts and the contract, never the implementer's claim that it's done, never their reasoning — passing the claim…
Reviews Architect's plan for a capability map (module boundaries, dependency direction, build order) before any build node starts. Approves or rejects the plan back to Architect. Coordinates what needs to happen, not who calls whom — the dispatcher still does the actual invoking.
Instructions for hybridlabor-api/bdb-dev-optimized-agent-skills, covering bdb agent skills — global instructions, docs & pipeline, how many agents, safety gate — mechanically enforced, not advisory and non-negotiable.
Use for reviewing an existing Grasshopper definition — diagnosing why it produces no output or wrong output, spotting data-tree mismatches, redundant components, and structural issues. Does not rewrite the definition.x.
Use proactively for building, editing, or solving Grasshopper definitions on the user's canvas — placing components, wiring them up, setting slider values, and running the solver.