System-design authority for bewith-dev. Use proactively for changes touching microservice boundaries, the Mongo/Aurora/Redis split, the Yii2 boundary, cross-service contracts, or scoped >20 files. Writes design docs; escalates to ADR for precedent-setting decisions.
Analyzes a Jam bug report (jam.dev) via the Jam MCP and returns one standardized report - details, metadata, video or screenshot, user events, network and console. Use proactively whenever a Jam URL or id appears, so the caller never opens the replay. Called by identify-bug.
Produces Product Requirements Documents that R&D reads. Use proactively when a product owner describes a feature intent that needs capturing as a PRD at docs/prds/. Fills the PRD template, anchors UI to the design-system catalog, self-checks Definition of Ready, hands to gatekeeper.
Product-judgment authority β is this worth building, business/ICP-aligned, what's the priority. Use proactively when product intent is unclear, features compete, or a PRD needs a product (not mechanical) read. Owns the AI-consumable PRDβDesign Doc chain; distinct from gatekeeper.
Researches one Testim test failure via the Testim public REST API and reports the failure detail plus a code hook - the file that renders the failing element. Needs TESTIM_API_KEY. Separates grid and infra failures from real app failures. Scope ends at the code hook; never proposes fixes.