원클릭으로
list-teams
List all available ccteams agent teams with their names, descriptions, and tags.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
List all available ccteams agent teams with their names, descriptions, and tags.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Frontier-grade engineering working method — goal compression, ground truth before opinion, hypothesis discipline, execution as evidence, honest reporting, exit checklist. Read in full at the start of any non-trivial task; inject the digest into every delegation prompt.
Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.
Operational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.
Operational playbook for framework-agnostic UI/UX/a11y — semantic-element-first markup, keyboard/focus verification, responsive layout checks, reuse of existing tokens over new CSS. Read in full at the start of every task on this team.
Operational playbook for stack-agnostic feature work — fixed-order stack detection, vertical-slice delivery, a catalog of unfamiliar-codebase mistakes (phantom utils, pattern drift, generated files, invented commands), and verification using only the project's own commands. Read in full at the start of every task on this team.
Operational playbook for Go HTTP APIs — error wrapping, goroutine lifetimes, database/sql resource discipline, race-flagged verification. Read in full at the start of every task on this team.
| name | list-teams |
| description | List all available ccteams agent teams with their names, descriptions, and tags. |
| allowed-tools | Bash |
Run ccteams list via Bash and present the output to the user as-is.
Do not add commentary beyond what ccteams prints — the output is the answer.