migrate-to-teamcity
Migrating CI/CD pipelines to TeamCity. Use when the user wants to migrate, convert, or switch to TeamCity from GitHub Actions (.github/workflows/) or Bamboo (bamboo-specs/*.yml), even if they only say "move our CI". Other CI systems (GitLab, Jenkins, CircleCI, Azure DevOps, Travis, Bitbucket) are not supported yet.
orchestrate-tickets
Coordinate claude-ui worker sessions over a batch of tickets through a staged pipeline: pull the backlog from the project's tracker, plan each ticket with an opus worker, implement it with a sonnet worker in its own git worktree, prove it with human-like Playwright UI testing and screenshot evidence, push and watch the CI build, open the pull request and get it reviewed by a fresh agent with the pr-review skill. Tracker, code host and CI are adapters (Jira, GitHub Issues, Bitbucket, GitHub, Jenkins, GitHub Actions); each repo supplies a ticket playbook. All findings land in local reports; the agent never comments on tickets or pull requests. Use when the user asks to orchestrate, run or work through a set of tickets or issues with parallel agents: "orchestrate these tickets", "work through the backlog", "chạy backlog", "spawn worker cho mấy ticket nà y". Needs a claude-ui session with orchestration on; the coordinator stays live to route worker questions.