Which BeWith repo does this belong in, and how do they connect. Use when work spans repos, when placing a new feature, when telling an active repo from a deprecated one, or when orienting in a repo for the first time. Covers the iframe-embedded apps and backend-services as shared backend owner.
For an ad-hoc dev task with no PRD — brainstorm the approach, converge on a short written spec, and get explicit approval BEFORE writing code. A lightweight design-before-code gate. Triggers on "let's design this", "how should I approach", "brainstorm this".
Capture a what's-missing / could-change POC observation into docs/insights/ — fast, separate from proposals. Worktree-isolated. Invoked by /insight or when the developer voices a gap or possible change during the build. Does NOT create a proposal; the 2-3 day review promotes agreed insights.
Create version-controllable software diagrams with Mermaid's text syntax — flowcharts, sequence, class, ERD, C4/architecture, state. Use when documenting architecture, a data model, an API/auth flow, or a DB schema, or any "diagram / visualize / map out the flow" request.
Rank my open ClickUp tasks + assigned GitHub Issues by priority → urgency → effort and recommend what to start next; --fits-in Nm/Nh/Nd filters to what fits a time box. Read-only; the ranking is computed in a script, not by the model. Invoked by /next-task.
View or change your role (dev or product). Role controls which capabilities the capability-awareness hook and /help-me surface to you — dev role sees dev-tagged artifacts, product role sees product-tagged artifacts, both see "both"-tagged ones. Invoked via /role. Default role is dev.
Triage a production/staging signal for BeWith — verify, locate, classify, recommend; returns one JSON verdict. Read-only. Triggers on /sentinel-check, "triage this error", "is this a real bug", or investigating a prod/staging signal.
View or change your BeWith developer settings (conversation language, role, default language, notifications, docs path) from one place. Backed by ~/.bewith/config.json — works in chat as a table plus set, opens a local HTML page, and mirrors the SwiftBar menu. Invoked via /settings.
A 4-phase active-fix loop — reproduce, isolate, hypothesize+instrument, fix+verify — with a hard stop after 3 failed attempts. Instruments at the gateway/RPC/service/Mongo boundaries. Triggers on "debug this", "why is this failing", "help me fix this bug".
Investigate a Testim (app.testim.io) end-to-end test failure - the test flow, the failing step and its error, screenshots, and the code hook in our frontend. Wraps the testim-researcher agent. Use when a Testim link or result id appears in a bug report or a CI failure.