sciagent

Drive ONE SciAgent backlog story from docs/reference/core.md to verified, gate-green, committed code — goal-directed end-to-end. The controller (Opus) takes the next story off the execution order, branches, gathers the contract (story + CLAUDE.md invariants + Context7 for any SDK), then executes it subagent-driven — implementation ALWAYS on cheaper models (Sonnet default, Haiku for fully-pinned mechanical tasks), Opus NEVER writes code. When ruff + pyright + pytest and the story's acceptance criteria are all green (verified by the verification-gate agent), it commits and reports. Use when the user runs /deliver-story or asks to build/ship/deliver a story (e.g. "AGT-12", "the gap-finder story", "the next story") from docs/reference/core.md.

Regenerate the typed TypeScript SciAgent API client(s) from the backend's live OpenAPI schema, so the Zotero add-on and the mechai.pl web app stay in lockstep with the FastAPI backend instead of drifting against hand-written types. Use when src/agt/api/** or src/agt/models.py changed, when api-contract-guardian reports drift, or when bootstrapping a new client (the mechai.pl web app). Run /gen-api-client.

Background policy for which Claude model tier to use when delegating SciAgent work to subagents — plan/architect on Opus, implement on Sonnet, fully-pinned mechanical tasks and gate-running on Haiku. Applies whenever Claude spawns subagents for SciAgent work, even outside the full deliver-story pipeline, so cost/quality tiering happens automatically without the user restating it.

Translate docs/reference/core.md epics into delivery-ready tickets, implementation plans, and validation checklists.

Apply docs/reference/settings.md to bootstrap local development and quality tooling in a reproducible way.

Build and validate Zotero plugin features based on docs/reference/zotero.md milestones and constraints.