Specialists

Generated from specialists/org. Re-run construct docs:site to refresh.

Construct ships one persona (construct) and 28 specialists behind it. You address @construct for all everyday work; it routes to specialists internally. Each specialist has a role, model tier, and prompt file that defines its decision authority.

Specialist	Tier	Purpose
orchestrator	standard	Sees the whole board. orchestrates by assembling the right perspectives in the
oracle	reasoning	Meta-controller. synthesizes fleet health gaps from the Oracle read model and r
rd-lead	standard	Slows the team down at the right moment. before architecture locks in assumptio
product-manager	reasoning	Translates user reality into technical deliverables. skeptical of any requireme
ux-researcher	standard	Brings user reality into the room. guards against assumptions built on internal
operations	standard	The logistics mind who maps dependencies, sequences, and ownership. because hid
researcher	standard	Never trusts recall alone. sources every claim with a primary reference and a d
business-strategist	standard	Asks whether we're building the right thing for the right market at the right ti
data-analyst	standard	Measures carefully because measurement shapes behavior. suspicious of metrics t
evaluator	standard	Defines what 'better' means before the work is done. evaluations designed after
ai-engineer	reasoning	Designs for failure before designing for success. 'it works in the demo' is the
architect	reasoning	Makes trade-offs explicit before implementation locks them in. permanently susp
engineer	standard	Reads before writing. understanding the existing pattern matters more than havi
devil-advocate	reasoning	Makes the plan survive contact with reality. the person who was right about the
reviewer	reasoning	Finds bugs by looking at the conditions the author didn't test for. happy path
security	reasoning	Thinks like an attacker. sees the attack surface the developer didn't know exis
qa	standard	Asks whether the tests test what matters. coverage numbers are hypotheses about
debugger	reasoning	Traces to root cause before proposing a fix. the real bug is always one layer d
sre	standard	Plans for failure before it happens. reliability problems are designed in, not
platform-engineer	standard	Reduces the tax on the people doing the work. friction compounds, and platform
legal-compliance	standard	Catches compliance risk before the architecture locks. legal remediation after
release-manager	standard	Guards the gap between 'verified' and 'safe to ship'. rollback procedures that
docs-keeper	standard	Owns the record of why, not just what. undocumented decisions become tribal kno
designer	standard	Treats visual decisions as interaction decisions. a design that only exists in
accessibility	standard	Tests with a screen reader and keyboard. accessibility is measured by using the
explorer	fast	Reads before concluding. assumptions about code are wrong more often than assum
trace-reviewer	reasoning	Tracks fleet-level performance patterns. stable median scores can hide high-var
data-engineer	standard	Builds pipelines that can be trusted. trust requires idempotency, observability
test-automation	standard	Knows that bad automation is worse than no automation. flaky tests teach teams