devteam

A command for running stages of the Stagecraft software-development process, such as requirements, design, building, review, testing, and deployment.

In plain words
What is it for?
Use it to start a Stagecraft stage, list available stages or host adapters, and combine completed work from multiple build streams.
Why use it?
It turns a stage choice into prompts for the matching specialist agents and coordinates their work through saved checkpoints.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/telus-labs/stagecraft/devteam
Clone the repo
git clone --depth 1 https://github.com/telus-labs/stagecraft
Per session 71 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 480 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00071 $0.00480
Opus 5 $0.00036 $0.00240
Sonnet 5 $0.00014 $0.00096
Haiku 4.5 $0.00007 $0.00048

Measured 2d ago against content hash 33eec0c83af8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devteam scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

hosts/claude-code/install/commands/devteam.md · 49 lines

What it actually says

/devteam

Drive the Stagecraft pipeline.

Input

The text after /devteam is interpreted as a subcommand. Examples:

  • /devteam stage requirements — render the PM stage prompt
  • /devteam stage build — render all four build workstream prompts
  • /devteam merge build — merge per-workstream gates into the stage gate
  • /devteam stages — list known stages
  • /devteam hosts — list installed host adapters

If the input is empty, ask the user which stage they want to run, then re-invoke with stage <name>.

Behavior

  1. Run devteam <subcommand> in a Bash tool call. (Install devteam globally with npm link from the Stagecraft repo if it's not on the user's PATH.)
  2. The CLI prints one stage prompt per workstream (one for single-role stages, N for multi-role stages like build).
  3. For each printed prompt:
    • Identify the named subagent from the prompt (.claude/agents/<name>.md).
    • Invoke that subagent with the prompt's body.
    • Wait for it to write the workstream gate at pipeline/gates/<workstream-id>.json.
  4. For multi-role stages, after all workstream gates exist, run devteam merge <stage> to produce the stage-level merged gate.
  5. Report status back to the user and ask whether to proceed to the next stage.

Gate identity (per Stagecraft contract F)

Workstream gates carry: stage, workstream, status, track, timestamp, blockers, warnings, plus stage-specific fields. The orchestrator adds orchestrator and host at write/validation time. Do NOT write agent — it has been removed.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 49 lines · 71 tokens per session scan A 33eec0c83af8

Subscribe to this mod's changes

devteam is a command published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 480 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.