菜单
Team CLI — manage team members, post messages, and run activity updates. ALWAYS check this skill before running any `team` command. Use when listing members, adding members, posting messages, or running team activity updates. Note - `afx team` is deprecated; use `team` directly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Agent Farm CLI — the tool for spawning builders, managing Tower, workspaces, and cron tasks. ALWAYS consult this skill BEFORE running any `afx` command to get the exact syntax. This prevents wasting time guessing flags that don't exist. Use this whenever you need to spawn a builder, check status, send messages, clean up worktrees, manage Tower, or run cron tasks. If you're about to type `afx` followed by anything, check here first.
Protocol orchestrator CLI — drives SPIR, ASPIR, AIR, TICK, and BUGFIX protocols via a state machine. ALWAYS check this skill before running any `porch` command. Use when you need to check project status, approve gates, signal phase completion, or manage protocol state. Also use when a builder asks about gate approvals or phase transitions.
Audit, prune, and update the project's governance docs — the COLD reference archives `codev/resources/arch.md` and `codev/resources/lessons-learned.md` AND their always-on HOT companions `codev/resources/arch-critical.md` and `codev/resources/lessons-critical.md` (Spec 987, hot/cold two-tier model). Use this skill when running MAINTAIN's arch-doc step, or when asked to update / audit / prune any of those four files. It polices the hot-tier cap (capped facts/lessons + a bounded cold-doc map), enforces displacement (demote to cold when full), keeps each hot file's map accurate, and is opinionated about what NOT to put in each tier (per-spec changelogs, exhaustive enumerations, aspirational state). Two modes: diff-mode (apply a specific change) and audit-mode (propose cuts with reasons). Edits files directly via normal file-edit tooling; no destructive shell commands.
AI consultation CLI — query Gemini, Codex, or Claude for reviews and analysis. ALWAYS check this skill before running any `consult` command. Use when reviewing specs, plans, implementations, or PRs with external models, running parallel 3-way reviews (cmap), or checking consultation stats. The `-m` model flag is always required except for `consult stats`.
Agent Farm CLI — the tool for spawning builders, managing Tower, workspaces, and cron tasks. ALWAYS consult this skill BEFORE running any `afx` command to get the exact syntax. This prevents wasting time guessing flags that don't exist. Use this whenever you need to spawn a builder, check status, send messages, clean up worktrees, manage Tower, or run cron tasks. If you're about to type `afx` followed by anything, check here first.
Protocol orchestrator CLI — drives SPIR, ASPIR, AIR, and BUGFIX protocols via a state machine. ALWAYS check this skill before running any `porch` command. Use when you need to check project status, approve gates, signal phase completion, or manage protocol state. Also use when a builder asks about gate approvals or phase transitions.
| name | team |
| description | Team CLI — manage team members, post messages, and run activity updates. ALWAYS check this skill before running any `team` command. Use when listing members, adding members, posting messages, or running team activity updates. Note - `afx team` is deprecated; use `team` directly. |
Manage team members and messages for your Codev project. Team data is stored in codev/team/ and displayed in the Tower dashboard.
team list
team message <text> [-a <author>]
team update
team add <github-handle> [-n <name>] [-r <role>]
List all team members from codev/team/people/.
team list
Displays a formatted table with Name, GitHub handle, and Role columns.
Post a message to the team message log (codev/team/messages.md).
team message "Spec 42 is ready for review"
team message "Deployed to staging" -a deploy-bot
Options:
-a, --author <name> — Override author (default: auto-detected from gh CLI or git config)Post an hourly activity summary. Called automatically by cron (.af-cron/team-update.yaml) or manually.
team update
Collects notable events from the last hour (builder spawns, gate approvals, PR merges, completed reviews) and posts a summary. Exits silently if no events occurred.
Scaffold a new team member file.
team add waleedkadous
team add jdoe --name "Jane Doe" --role "Developer"
Options:
-n, --name <name> — Full name (default: github handle)-r, --role <role> — Role (default: "Team Member")Creates codev/team/people/<handle>.md with YAML frontmatter. Handle is normalized to lowercase. Fails if the member already exists.
codev/team/
├── people/
│ ├── waleedkadous.md # YAML frontmatter + optional bio
│ └── jdoe.md
└── messages.md # Append-only message log
---
name: M Waleed Kadous
github: waleedkadous
role: Lead Architect
---
Optional freeform bio or notes (not displayed in Tower).
Required frontmatter fields:
name — Display namegithub — GitHub handle (used for API data enrichment)role — Team role (displayed in Tower)# Team Messages
<!-- Append new messages below. Do not edit or delete existing entries. -->
---
**waleedkadous** | 2026-03-09 14:30 UTC
Spec 42 is ready for review.
---
**tower-cron** | 2026-03-09 15:00 UTC
Hourly update: Merged PR #123: Add user auth. Gate approved for #42.
Messages are append-only. Each entry has an author, UTC timestamp, and body text.
afx team commands still work but print a deprecation warning. Use team directly:
afx team list → team listafx team message → team messageafx team update → team updateTo set up a team directory for a new project:
team add first-member --name "First Member" --role "Architect"
team add second-member --name "Second Member" --role "Developer"
The Team tab appears in Tower when 2+ valid members exist.