agentickode

Use when the user wants to dispatch a coding task to a remote workspace — fixing bugs, implementing features, running an agentic coding run, or creating a PR automatically. Use this even if the user just says "fix the login bug on myproject" or "run this task" or "create a run" or "implement X on Y". Also use when the user asks to approve or reject a pending run.

Full development workflow orchestration — requirements analysis, architecture planning, implementation, code review, and testing using specialized sub-agents with approval gates. Use when the user wants to develop a complete feature end-to-end, or asks for the full development flow. Triggers on /dev-flow.

Use when the user wants to start an AI agent (Claude, Codex, Gemini, Aider) on a remote workspace server for a project. Use this even if they just say "launch claude on myproject", "start an agent", "open a session on the server", "connect to workspace", or "I want to work on project X remotely".

Use when the user wants to manage projects on the platform — listing configured projects, adding a new repo, updating project settings, or checking if a project is cloned on its workspace. Use this for "show my projects", "add this repo", "register a new project", "which projects do I have", "is this project ready on the workspace", or any project configuration task.

Use when the user asks about workspace servers — listing them, testing SSH connectivity, checking what agents are installed, viewing server details, or troubleshooting server issues. Use this for "show me my servers", "is the server reachable", "what agents are on server X", "test connection to workspace", or any infrastructure-level question about the remote machines.

Use when the user wants to interact with a running agent session on a workspace server — sending commands, reading output, listing active sessions, or closing them. Use this for "send this to the agent", "what's the agent doing", "check session output", "close that session", "list my sessions", or any tmux-based agent interaction.

Use when the user asks about what's happening on the platform — active runs, failed tasks, pending approvals, system health, or analytics. Use this for "what's running", "any failures", "show me the status", "is everything healthy", "how many runs today", or any question about current platform state.

AI workflow editor for CC Workflow Studio. Create and edit visual AI agent workflows through interactive conversation using MCP tools (get_workflow_schema, get_current_workflow, apply_workflow). Use when the user wants to create a new workflow, modify an existing workflow, or edit the workflow canvas in CC Workflow Studio via the built-in MCP server.

Run targeted or full CI checks in Docker. Use when verifying code changes, before commits, or when the user wants to lint/test/typecheck. Triggers on /check or when user asks to run tests, lint, or validate code.

Database migration helper — create, apply, or check Alembic migrations in Docker. Use when the user needs to create a new migration, apply pending migrations, check migration status, or roll back. Triggers on /migrate.

Quick feature planning that writes implementation plans to docs/plans/. Use when the user runs /plan or asks to plan a feature, endpoint, integration, or architectural change.

Scaffold new backend endpoints, services, worker phases, or frontend pages with proper structure, license headers, and tests. Use when creating new API routes, services, pipeline phases, or React pages. Triggers on /scaffold.

Analyze codebase changes and update CLAUDE.md and README.md to reflect current state. Use after major refactoring, structural changes, or when documentation may be stale. Triggers on /updatedocs.