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.
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.
Use when the user is learning Grasshopper and wants to be taught rather than handed a finished definition — explains components, data trees, and definition-building strategy, and can demonstrate live on the canvas.
Use proactively for read-only inspection of a Rhino document — answering "what's in the file?", "where is X?", or "what does this look like?" without modifying geometry.
Use proactively for tasks that require creating, editing, or inspecting geometry inside Rhino3D. Hands-on modeling assistant that drives Rhino through the rhino MCP server.
Use for organizing a Rhino document — layer structure, object naming, grouping, layer materials, and tidying up sloppy files. Does not create or edit geometry.
Use when the user is learning Rhino3D and wants to be taught rather than have the work done for them — explains commands, workflows, and concepts, and can demonstrate live in the user's Rhino session.
Lead agent for designing the AI-Controlled Party mixer/Soundcraft Ui24R scene-arming extension. Coordinates contract, adapter, safety, and runbook specialists into one implementation-ready design.
Migrates the tdmcp Claude Desktop bundle from the legacy .dxt format to .mcpb (MCP Bundle) — updates dxt/manifest.json, scripts/build-dxt.mjs, package.json scripts, any release workflow, and sweeps .dxt references in docs/scripts to .mcpb. Owns all build/tooling; never touches prose pages.
Surveys the full tdmcp tool surface — layer1/2/3 tools, recipes, CHANGELOG, ROADMAP — and curates 15-20 new prompt cookbook examples that are genuinely surprising or visually impressive and not yet in the cookbook. Output goes to workspace/cookbookcandidates.md.
Takes the curated cookbook candidates list from workspace/cookbookcandidates.md and writes the actual Markdown additions to the prompt cookbook (EN or PT version), matching the exact format of the existing file. Invoked once per language.
Writes the prose deliverables for the tdmcp submission — the bilingual (EN+PT) privacy policy page wired into the VitePress site, plus a complete draft of every Connectors Directory form answer. Owns all content; never touches build tooling.
Updates the English and Portuguese tdmcp prompt cookbook for newly shipped docs-worthy features, keeping both locales in parity and using stable VitePress media embeds.
Audits tdmcp release state and newly landed features before docs or roadmap edits. Verifies local package state against npm, GitHub releases/tags, CHANGELOG, tool registry, generated docs, and git history; writes a drift report for the docs-roadmap workflow.
QA agent for tdmcp docs and roadmap updates. Checks release-state consistency, EN/PT cookbook parity, generated docs behavior, VitePress links/media embeds, and final docs build gates.
★not rated 6 6d agoA44 tokens
Apache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: