SeemSeam

Delegate file I/O to Codex via FileOpsREQ protocol. Use when Claude needs Codex to modify files.

Dual review with Claude and Codex for quality verification. Use for step or task review.

Manage lightweight role routing (executor/reviewer/documenter/designer) for all tasks. Use for /roles.

Create a task plan with dual design. Use when starting a new task or running /tp.

Execute current step in AutoFlow workflow. Use when running /tr or continuing task execution.

Send structured prompt to Gemini and parse JSON response. Use for direct Gemini communication.

Switch between plan and bypass modes. Use when changing Claude's execution mode.

Send structured prompt to Codex and parse JSON response. Use for direct Codex communication.

Design, edit, or migrate CCB project teams by updating .ccb/ccb.config. Use when the user wants to add, rename, remove, or reorganize CCB agents; choose providers, worktree isolation, models, API shortcuts, single-window or multi-window layout; migrate an old ccb.config to the current windows topology; handle optional skill inheritance or injection requests for agents; or turn a natural-language team/workflow description into a valid CCB config. Only update shared or per-agent memory when the user explicitly asks for workflow memory design.

Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.

Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.

Send a request to a CCB agent with `ask`.

Send a request to a CCB agent with `ask`.

Send a request to a CCB agent with `ask`.

Maintain this CCB project's GitHub-facing release surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README_zh.md, CHANGELOG.md, VERSION, GitHub release notes/assets, repository description/topics, or GitHub Actions release/test status.

Produce architecture improvement advice from existing-code Archi analysis. Use when the user wants concrete modification suggestions, sequencing advice, or a practical refactor roadmap based on the current codebase rather than task-goal planning.

Run diff-based architecture analysis with archi. Use when the user asks whether current changes are architecturally safe, what the current git diff impacts, or which changed components carry structural risk.

Run full-project architecture analysis with archi. Use when the user asks for an overall architecture score, full hotspot review, package topology diagnosis, or the main structural weaknesses of the current codebase.

Produce architecture improvement advice from existing-code Archi analysis. Use when the user wants concrete modification suggestions, sequencing advice, or a practical refactor roadmap based on the current codebase rather than task-goal planning.

Run diff-based architecture analysis with archi. Use when the user asks whether current changes are architecturally safe, what the current git diff impacts, or which changed components carry structural risk.

Run full-project architecture analysis with archi. Use when the user asks for an overall architecture score, full hotspot review, package topology diagnosis, or the main structural weaknesses of the current codebase.