cawstudios

Orchestrate a Gantry plan to a finished PR — Claude writes a goal-prompt doc, delegates implementation stages to the Codex plugin (xhigh + ponytail), verifies and commits between stages, and closes with the autoreview loop. Use when the user asks to implement a plan/goal prompt, "run the goal pipeline", "same as the goal", or hands over a docs/architecture/*-goal-prompt.md to execute.

End-to-end Gantry plan implementation pipeline. Use when the user asks to implement or pursue a plan, goal prompt, feature, fix, refactor, PR update, or "same as the goal" workflow with subagent implementation, ponytail simplicity, no-commentary implementation, autoreview, build, launchctl restart, Knacklabs lead gen smoke, and PR/pipeline closeout.

Gantry self-administration reference for current host runtime operations: CLI commands, settings.yaml runtime settings, .env credential keys, agent management, scheduler tools, memory tools, browser tools, diagnostics, and service control. Use when asked to manage Gantry itself.

Guides Gantry tool, skill, MCP server, browser, local CLI, semantic capability, inventory, and permission lifecycle work. Use when changing durable capability selection, visible attached sources, transient request_permission flows, or agent access review paths.

Drives Gantry agent-chat tests through the local Control API session path and captures assistant responses. Use when testing an agent response, permission prompt, skill behavior, or runtime chat flow without needing Telegram UI rendering.

Use when creating or revising a Gantry product, UX, permission, job, ingress, provider, settings, or agent-flow plan that must be decision-complete with no room for assumptions. Triggers for PM plan, product manager plan, no assumptions, UX flow, user flow, agent flow, acceptance criteria, validation plan, provider-neutral plan, or Surface Impact Matrix.

Drives Gantry tests through the visible Telegram UI with Chrome. Use only when testing Telegram rendering, Telegram buttons, topic routing, or visible Telegram conversation behavior; use agent-chat-test for direct runtime agent-chat tests.

Use for folder movement, layer boundaries, and domain/application/runtime/adapters refactors in Gantry.

Migrate an EXISTING repo — a prototype or early project built with agents before the harness — into the Symphony Forge harness: vendor the machinery (forge adopt), sort existing content into prototype/ and docs/context/, harvest it into DISCOVERY/BRIEF and decision records, and hand off to the factory loop. Invoke when the user says "migrate this repo", "adopt the harness", "bring this project into symphony forge", "harness-ify this repo", or "/caw-migrate-project".

Bootstrap a new CAW client project from the Symphony Forge harness: update the harness clone, verify machine prerequisites (doctor), scaffold the repo (forge init), and hand off to the project's /forge skill. Invoke when the user says "new CAW project", "set up a client project", "start a project with the harness", "scaffold <name>", or "/caw-new-project".

Operate the Symphony Forge harness: start tasks, save approved plans, record decisions, assumptions, and client sign-off, harvest the docs/context inbox, check gate status, and review proposed skills. Invoke when the user says "start a task", "save this plan", "record a decision", "harvest context", "is this PR ready", "harness status", "what now", or "/forge".

CAW Studios' engineering standards ("Playbooks" + "Patterns and Practices") that all projects should adhere to. Covers monorepo/modular-monolith structure, NestJS + FastAPI coding standards, API/Swagger/database/branch/ environment naming, event & service bus, logging/observability, exception handling, notifications, the provider pattern, and AWS/Terraform DevOps standards. Invoke when writing or reviewing code, designing a service or schema, naming branches/environments/resources, setting up a repo, or making AWS/IaC decisions on a CAW project — then read the specific reference file(s) relevant to the task. Triggers: "engineering constitution", "CAW standards", "playbook", "PnP", "our coding standards", "/kl-engg-constitution".