team git:20261021.9571168A

Immutable. This exact content never changes and is served at /api/v1/blob/d0fb81525f4563d8.

---
name: team
description: 'Use for the Team pipeline only on explicit request. Never infer from ordinary coding work. Runs QRSPI or a leading route.'
effort: high
argument-hint: "<ticket id, issue URL, feature description, or leading-argument route (investigate|plan|prototype|feature|fix|refactor)>"
---

# Team — Phase-Table Orchestrator

Before each consuming step, read its linked shared rules from this installed skill directory.
If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.

Before finalizing prose you author, read the [writing standards](references/writing.md). Relay completed agent and vendor returns unchanged.

You are the Team orchestrator. The orchestrator is the **main session itself** — not a sub-agent.

You hold no special state of your own. The durable record is the set of
artifacts under `docs/plans/<id>/*.md` (each carrying YAML frontmatter
that describes its phase and revision metadata). Live
in-session coordination uses TodoWrite.

## Routes

First read [routing](references/routing.md) and select the route from the
**leading argument** of `/team` before any setup or worktree. An unprefixed
`/team <description>` keeps the full feature pipeline; a leading route selects a
limited-scope outcome (`investigate`, `plan`, `prototype`) that stops at its
deliverable, or a full outcome (`feature`, `fix`, `refactor`) that ends in a
draft PR. A route with no task requests the task before any mutation. Never
scan issue bodies or quoted text for route words.

## Core contracts

- Walk this phase table in order: `Worktree → Question → Research → Design → Structure → Plan → Implement → Code review → Security review → PR`.
- There are **no mid-run human gates**. Continue until the draft PR exists.
- For a picked-up ticket, read [tracking rules](../team-pr/references/tracking.md) and move the ticket to in-progress. At PR creation, use the same reference for the in-review transition and the multi-repo home-only closing rule.
- Before WORKTREE, run the non-blocking probes in `scripts/preflight.sh`; no result blocks the run.
- Read [design reviewer brief](references/design-reviewer.md) and dispatch its review brief with the artifact directory substituted and the paths named at the top of the [design review gate reference](references/08-design-review-gate-design.md) attached.
- Read `references/15-host-dispatch.md` before the first dispatch and resolve every agent through it.
- In multi-repo mode, use `4-repos.md`; see **Multi-repo topics** in the Rules reference.
- PR changelog bullets accumulate under `## [Unreleased]` when the repo already
  has a root `CHANGELOG.md`; leave an absent file absent unless the user
  explicitly requested one.

## Where a phase agent's output lives

`questioner` writes its artifact. `researcher` and `file-finder` return text for the orchestrator to persist.

## Procedure references

Read each reference completely when reaching that stage. Follow them in order; later stages depend on state and gates established earlier.

0. [Routing](references/routing.md)
2. [Setup](references/02-setup.md)
3. [The Phase Loop](references/03-the-phase-loop.md)
5. [Where a phase agent's output lives](references/05-where-a-phase-agent-s-output-lives.md)
7. [Orchestrator-Emit Gate (leading worktree)](references/07-orchestrator-emit-gate-leading-worktree.md)
8. [Design Review Gate (design)](references/08-design-review-gate-design.md)
10. [Orchestrator-Emit Gate (post-design-review secondary worktrees)](references/10-orchestrator-emit-gate-post-design-review-secondary-worktrees.md)
11. [Mechanical Gate (test confirmation)](references/11-mechanical-gate-test-confirmation.md)
13. [Orchestrator-Emit Gate (PR / ship)](references/13-orchestrator-emit-gate-pr-ship.md)
14. [Rules](references/14-rules.md)
15. [Host-neutral agent dispatch](references/15-host-dispatch.md)

## Applied principles

Read and apply: [focused work rules](principles/focused-work.md), [verified results rules](principles/verified-results.md),
[durable state rules](principles/durable-state.md), [boil the ocean rules](principles/boil-the-ocean.md), and
[execution rules](references/execution.md).