devthrottle

Relocate a live session to another cc-director slot or Director - approval-gated handover through the GATEWAY, the seed identifies itself as a moved session, the TARGET keeps the source's original name, the source is renamed "[MOVED]" and put on hold so the user can close it. Triggers on "/move-session", "move session", "migrate session", "transfer session".

INTERNAL reference, NOT shipped with the installer. The in-repo expert on every coding-agent CLI CC Director can run (Claude Code, Codex, Gemini, OpenCode, Grok, Copilot, Cursor, Pi). Knows each agent's command line, config files, context-injection points, lifecycle hooks and events, SDK/API/server mode, transcript format, session semantics, and how CC Director drives it. Triggers on "agent-expert", "agent expert", "how does <agent> inject context", "<agent> hooks", "<agent> events", "<agent> CLI reference", "which agents support X", "agent capability matrix".

How a mission is RUN in this repository - the Architect, the Manager, the Workers, and the independent Inspector, plus the four standing laws (ask up front then run alone, and NEVER guess - bring the owner in when something is genuinely undecidable; the mission branch holds the work and only the Architect lands it on main; a different agent family inspects before anything reaches main; merged to origin/main is the only done). Read this BEFORE starting or seeding any mission, and before writing any mission brief. Triggers on "/mission", "start a mission", "run a mission", "seed an architect", "write a mission brief", "mission brief", "who merges", "mission roles".

DevThrottle - "Mission Control for Claude Code". A desktop app (binary cc-director.exe) that runs and supervises multiple Claude Code sessions and ships cc-* CLI tools on PATH. Agents drive the fleet through the cc-devthrottle command, not by calling the Director over HTTP. Triggers on "/dev-throttle", "/devthrottle", "/cc-director", "what cc tools", "list tools", "available tools", "devthrottle api", "session manager", "mission control".

Talk to other DevThrottle sessions across the fleet. Use when you want to list running sessions, rename this session, message another session, ask another session a question and get its answer, or open a new session - from inside a session. Triggers on "/fleet-comms", "message another session", "talk to another session", "ask another session", "rename this session", "rename session", "list sessions", "what sessions are running", "open a session", "spawn a session", "cc-devthrottle", "fleet messaging", "session intercommunication".

Guided run-book for cutting a DevThrottle release - assemble the changes, write the release notes, coordinate the internal docs site, cut the tag, and announce it. Triggers on "/release-manager", "cut a release", "prepare a release", "ship a release", "do the release".

Create a git commit following the project's commit standards. Triggers on "/commit" or when user asks to commit changes.

Browser automation via Playwright CLI. Use for ALL browser tasks where the target site has NO bot/human detection. Faster, 90k fewer tokens, supports parallel agents. Falls back to cc-browser ONLY for bot-protected sites (LinkedIn, Reddit, Spotify). Triggers on "playwright", "browser test", "UI test", "web test", "form test", "screenshot site".

Create a GitHub issue from screenshots, images, text descriptions, or any combination. Use this when the user wants to file a new issue or report a bug.

Find dead code and unused files/components in CC Director. Use when you need to identify unused projects, classes, or services that can be safely removed to simplify the codebase.

The Developer Agent in the CenCon Development Method for cc-director. Implements ONE GitHub issue labeled flow:ready-dev. Always requires an issue (never writes code without one), always follows review-code/CodingStyle.md/VisualStyle.md and the CenCon method. Plans before implementing; if the issue is not detailed enough it rejects it back to the Product Agent (flow:rejected) instead of guessing. On completion commits proof (screenshot + HTML report) to the PR branch and labels flow:ready-qa. Triggers on "/developer-agent", "developer agent", "implement this issue", "pick up the next ready-dev item".

Supervisor of the CenCon Implementation session for cc-director (issue

The Product Agent in the CenCon Development Method for cc-director. Owns GitHub issues - turns a raw request into a clearly-defined issue that meets the Definition of Ready, then hands it to the Developer Agent via the flow:ready-dev label. Also re-sharpens issues the Developer Agent rejected. NEVER writes implementation code. Triggers on "/product-agent", "product agent", "write a work item", "make this ready for dev", "sharpen this issue".

The QA Agent in the CenCon Development Method for cc-director. Loops over GitHub issues labeled flow:ready-qa, independently verifies each one with proof in the running app (never trusting the Developer Agent's report), and either passes it (flow:done, closes the issue) or bounces it back to the Developer Agent (flow:qa-failed) with a specific written defect. Never stops on its own until the queue is empty. Triggers on "/qa-agent", "qa agent", "run the QA queue", "verify the ready-qa items", "pick up the next QA item".

The Support Agent in the CenCon Development Method for cc-director. The idle question-answering seat - answers questions about the cc-director codebase and about what the Product, Developer, and QA agents are doing, and owns/maintains the CenCon documents. Strictly read-only with respect to product code and issues - it never implements, never creates or moves issues. Triggers on "/support-agent", "support agent", "ask about the codebase", "what are the agents doing", "explain how X works".

Fix compiler warnings using proper null handling and senior developer practices. Use when asked to fix warnings in a file, clean up nullable warnings, or resolve CS warnings. Works one file at a time with test coverage.

Adversarial cold-reader review of saved wingman turn briefs - blind-judges the brief alone, then checks it against TurnPackage terminal evidence, scores content + visual presentation, emits an HTML verdict report with a should-be rewrite. Triggers on "/wingman-brief-reviewer", "review briefs", "review the wingman", "wingman review loop".

Review recent code changes for security issues, PII leaks, and bugs against CodingStyle.md. Triggers on "/review-code" or when called by commit skill.

Read and write CC Director app settings (screenshots location, gateway connection, any config.json key) by calling a running Director's Control API. Triggers on "/cc-settings-api", "set the gateway", "connect this director to the gateway", "set screenshots location", "configure cc-director settings".

Generate and refresh the public feature documentation in docs/public/features/ - scan the code to decide what is implemented, screenshot the running app, and update the pages. Triggers on "/document-features", "document the features", "refresh feature screenshots", "regenerate feature docs".

Audit the cc-director repo for hygiene problems (junk files, root clutter, stale docs, dead/unreferenced code, archived dirs) and produce an incremental cleanup plan, optionally filing one-at-a-time GitHub cleanup issues. Triggers on "/code-maintenance", "clean up the repo", "repo hygiene", "code maintenance", "tidy the codebase".

List GitHub issues, let the user pick one, and download all content including images so an agent can work on it. Use this when the user wants to browse, review, or select issues to work on.

Meta-skill for managing Claude Code skills. Create, review, edit, and list skills in a standardized way. Triggers on "/skill-manager", "create skill", "review skill", "list skills", "edit skill", "skill management".

Review the voice-turn comparison log for fidelity drift (what the user said vs what was cleaned, and what the agent said vs what the wingman spoke), archive flagged turns locally, and file sanitized GitHub issues. Triggers on "/voice-review", "review voice log", "review wingman fidelity", "review voice turns".

Update public documentation in docs/public/ when features or tools change. Triggers on "/update-docs", "update docs", "update documentation".

Interact with and test the CC Director WPF app using the cc-click CLI tool. Use this to click buttons, read text, take screenshots, list elements, right-click session tabs, and navigate the UI.

Analyze .NET source code and generate CenCon documentation (architecture_manifest.yaml, security_profile.yaml, INDEX.md). Triggers on "/cencon-generate".