Investigates code-level issues in the agency's Python stack (Django, FastAPI, SQLAlchemy) — debugging, log analysis, query optimization, test-coverage gaps. Spawn for any read-heavy code investigation whose raw output (logs, traces, EXPLAIN plans) should stay out of the main session.
Runs and verifies deployments for the agency's two client stacks — BigCorp on AWS (Terraform, Lambda, RDS) and StartupXYZ on Vercel — including CI pipelines, migrations, and secret management. Spawn for deploy execution, rollback prep, or infrastructure checks.
Keeps the agency's multi-client task boards clean — GitHub Projects V2 sync, field updates, weekly client status prep, iteration planning. Spawn for board grooming or status-report collection across BigCorp, StartupXYZ, and internal work.
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
Single entry point for the example-org engagement — board sync against the example-board GitHub Project, status-report prep for the example-team mandant, documentation routing through the example-docs context, and tenant-aware cloud lookups via example-cloud. Reads field schemas from…
Archives every closed period still in the log: one summary per period, distils durable facts into memory (propose-then-confirm), resets log.md. Period follows work.archivecadence (weekly, bi-weekly, monthly, quarterly, yearly). Trigger: "/archive", "archive", "archive week", "archive month", "week wrap-up".
Board-driven implementation pipeline: polls a GitHub Project, arms an item when dragged into the trigger column, advances it stage by stage to a human-gated draft PR. Stages configured per project in workflow/projects/ .yaml. Trigger: "/board-pilot", "board pilot", "auto-implement from board", "pipeline runner".
Finds drift between docs and reality in Bridge repos: license badge vs LICENSE, README skill list vs skills/ dir, broken cross-refs, cross-instance skill shadowing. Returns a P0-P3 report with fix proposals. Trigger: "/bridge-audit", "audit", "drift check", "find drift", "are my skills shadowed".
Contribute features or improvements from your Bridge to the open-bridge OSS upstream (or org overlay) as a fork-based PR. Scans your user branch, classifies by scope, runs the mandatory content-safety gate. Trigger: "/contribute", "contribute", "share my skill", "PR to upstream", "give back".
Periodic background consolidation pass over the Bridge: scans skills/protocols/ rules/docs for drift, the proposal queue for staleness, and recent work for user-pattern observations, writing findings as proposals under work/learning/proposals/, never direct edits. Trigger: "/bridge-curator", "curator", "weekly…
Context-aware terminal greeting (MOTD) for Bridge instances: renders a per-instance logo, palette, today's calendar and the "Doing" board, resolved from which org folder the terminal opened in. Includes gen-logo.py (ANSI-Shadow generator). Trigger: "/bridge-greeting", "terminal greeting", "motd", "startup logo"…
Review surface for Bridge Learning-Loop improvement proposals: lists pending suggestions by severity, walks through accept/reject/edit/defer, applies accepted diffs via commit. Auto-surfaces in /briefing when proposals pile up. Trigger: "/bridge-learn", "review proposals", "pending proposals", "what did we learn"…
New user onboarding and reconfiguration: discovery-driven setup with a permission-gated system scan, evidence-based feature suggestions, and a read-only catalogue of what else Bridge can do. Six-phase wizard, works without GitHub. Trigger: "/bridge-onboard", "onboard", "setup", "configure bridge", "new user"…
Subscribe a Bridge to an ORG OVERLAY: a git repo publishing shared config (contexts, projects, mandants, org skills) as a flat mirror tree. Materializes copies via 3-way merge; your files always win. Trigger: "/overlay", "org overlay", "subscribe to overlay", "overlay status", "overlay diff".
Promote CORE changes from your user branch to upstream by scope (core to OSS upstream, org to org overlay). Runs mandatory content-safety checks, opens fork-based PRs. For file-level contributions use bridge-contribute. Trigger: "/bridge-promote", "promote", "cherry-pick", "push to upstream".
Checks this Bridge installation: branch, config, registries, local repos, work system, plus docs health and link checking. Not live service health, not the daily overview (briefing). Trigger: "/bridge-status", "bridge status", "bridge health", "docs health", "link check". Bare "bridge" or "status" are not triggers.
End-of-sprint batch-sync: pushes ALL pending scope:core + scope:org commits from the user branch to BOTH upstreams (open-bridge + org overlay) in one operation. NOT for a single commit (use /promote) or file-level adaptation (/contribute). Trigger: "/bridge-sync", "sync to upstreams", "push to both", "end-of-sprint…
Daily briefing from your own profile (workflow/briefings/ .yaml: sections, trackers incl. GitHub/Jira/GitLab/ADO/Linear, inbox rules): inbox first, then steer the day (approve, defer, drop, open agent tabs). /briefing picks a profile. Trigger: "/briefing", "briefing", "good morning", "daily standup", "what needs me"…
Calendar and recipient management: list, add, show, cancel, confirm entries in workflow/calendars/entries.yaml, plus mandant recipient groups (company, household, family, friends) with multi-recipient support and repeat patterns. Trigger: "/calendar", "scheduled messages", "calendar add", "mandants", "recipient…
Turns a capability gap into a gated acquisition: when no skill, CLI, MCP, or account covers a need, offers (never auto-acts) to research and provision a tool, or scaffold a skill. Trigger: "the bridge can't do that", "there's no skill for this", "build a skill for this", "capability gap", "self-extend".
Per-project view: open GitHub board items, recent commits and deployment health for the project detected from the current directory, in the terminal or as HTML. Not the daily overview (briefing). Trigger: "/dashboard", "/dashboard --all", "/dashboard --html", "show dashboard", "show tasks", "tasks for this project".
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: