team
Run the four-role Herdr team (pm, po, dev, qa panes) that ships one feature of this repo. In the main session the user runs /team as the orchestrator (up, status, go, down); in a role pane the orchestrator prompts /team role: pm|po|dev|qa. Requires HERDR_ENV=1.
shenysun · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add shenysun/skills-manager --skill team技能说明
name: team description: "Run the four-role Herdr team (pm, po, dev, qa panes) that ships one feature of this repo. In the main session the user runs /team as the orchestrator (up, status, go, down); in a role pane the orchestrator prompts /team role: pm|po|dev|qa. Requires HERDR_ENV=1." disable-model-invocation: true
Team
Four roles in Herdr panes ship one feature: pm grills and publishes the spec, po answers the grilling and rules on defects on the user's behalf, dev implements one ticket per invocation, qa derives and executes the acceptance checklist. This one skill serves both sides: the orchestrator (main session, routed by subcommand) and the roles (role panes, routed by role:).
Roles never share context. Files are the interface: every artifact lives in .scratch/<feature-slug>/, and the stage is always re-derived from those files — never from memory.
Reserved slash commands (/to-spec, /to-tickets, /implement, /triage) are user-invoked only, so roles cannot call them via the Skill tool — the orchestrator relays them into the pane. Roles call the primitives (grilling, domain-modeling, tdd, code-review) themselves.
Orchestrator mode
You are not a fifth worker: you create the layout, route turns, and surface escalations to the user. For exact herdr command sequences, prompt texts, and the team.md format, load references/orchestration.md.
Guards
- Verify
test "${HERDR_ENV:-}" = 1; otherwise say you are not inside Herdr and stop. - Confirm the cwd is this repo's root — role panes must start there to load
.claude/skills/. - Never prompt an agent that is not
idleordone: checkherdr agent getfirst. Ablockedrole is waiting at a question or approval UI — never re-prompt it.
up <feature-slug> [one-line idea]
- If
.scratch/<slug>/team.mdexists and its agents are live (herdr agent list), adopt them; never create duplicates. Abort if any team name is live but not ours. - Otherwise create the layout and agents per orchestration.md §Up, recording the tab/pane IDs and
git rev-parse HEADas the Base SHA in team.md. - Send the PM kickoff prompt with
--wait --timeout 120000. - Tell the user: PM will interview via PO, then run
/team go. Mention the cost: this runs four parallel Claude sessions.
status
herdr agent geteach of pm/po/dev/qa.- Derive the stage from files (§Stage). Grep
Status:lines; do not read whole files. - Report the stage, each agent's state, the frontier ticket, open defects, and any escalation awaiting the user.
go
- Derive the stage (§Stage) and perform only that stage's action. Everything you do must be idempotent:
/team gois safe to run at any time and no-ops when no role's turn is due. - Prompting dev with a ticket: send
/clearfirst without--wait(a slash command starts no turn;--waitwould misreportagent_prompt_stalled), then the ticket prompt, also without--wait— a ticket can run for many minutes. - Report what you did, and what the user is expected to do next.
down
Ask for confirmation. Send /exit to each agent (no --wait), close only the tab recorded in team.md, then list the leftover .scratch/<slug>/ paths. Never close panes or tabs you did not create.
Stage
Derive from .scratch/<slug>/, first match wins. The same table serves status and go.
| Condition | Stage | Action |
|---|---|---|
| no team.md | not-started | suggest /team up |
| no spec.md | pm-interview | run the Answering loop (orchestration.md §Answering) |
pm announces ready for /to-spec | pm-spec | relay /to-spec (--wait --timeout 180000) |
| no tickets in issues/ | dev-tickets | relay /to-tickets <spec path> into the dev pane; when it asks for breakdown approval, route the questions through po |
| a ticket is ready-for-agent with all blockers done | dev-ticket | /clear dev, then prompt dev: ticket NN |
| a ticket is in-progress | dev-working | wait; if dev is idle without the Status flip, read the pane and recover (orchestration.md §Recovery) |
| all tickets done, no acceptance.md | qa-kickoff | prompt qa: kickoff |
| acceptance.md Status: in-progress | qa-running | wait; surface anything blocked |
| a ticket is needs-triage | triage | put the decision to po; spec contradictions get a PM ruling |
| acceptance.md Status: passed, no open tickets | done | summarize (commits, scenarios, defects); suggest /team down |
| anything else | stuck | report the file state vs agent states to the user and stop |
Blocked roles
A blocked role (or an agent_blocked reply) is waiting at a question or approval UI — never re-prompt it. Run herdr agent read <name> --source recent-unwrapped --lines 40, quote the question to the user here, and offer herdr agent focus <name> — do not auto-focus. Then stop: the user answers in the pane and re-runs /team go.
Role mode
Triggered by /team role: <pm|po|dev|qa> feature: <slug> plus role-specific arguments. Read only your own section; the other roles' files are read-only to you.
PM
Your deliverable is exactly one file: .scratch/<feature-slug>/spec.md. You never write tickets or code.
- Load context: read
CONTEXT.mdfor vocabulary and the ADRs touching the area. - Interview: call the Skill tool twice, for grilling and domain-modeling — that is what /grill-with-docs does internally. The answers arrive in this pane from the PO (relayed by the orchestrator): keep asking in rounds until the frontier is empty, letting domain-modeling record decisions into
CONTEXT.mdand ADRs as they land. - Hand off to /to-spec: it is reserved, you cannot invoke it. When the frontier is empty, announce
ready for /to-specand stop. The orchestrator relays/to-specinto this pane — it runs here, with the full interview as its raw material, so nothing may clear this pane yet. - Stop. After /to-spec publishes the spec, announce the spec pat