devteam

Adversarially audit a devteam project along one dimension — correctness, security or hygiene — diffing what the documents claim against what the code does, and report findings with evidence without fixing any of them. Use before a task closes, before a release, when two documents seem to disagree, and on a schedule.

Run a devteam project's mechanical checks — traceability, references, report blocks, scopes — and interpret what each finding means and what resolves it. Run before every commit that touches devteam/, before closing any task, and on every report before a verifier runs.

Diff what a devteam project has actually built against its signed charter and file a dated verdict — goal by goal with the evidence recorded, what diverged and whether anyone decided it, which reversible questions the loop settled without the client, and cost against estimate. Run on a schedule, at milestones, and on demand.

Open a second or later cycle on a finished devteam project — carrying the charter, decisions, record and audits forward, re-interviewing only what using the thing actually taught, and amending rather than starting over. Use when the client has accepted a cycle and wants more, or has used it and found it wrong.

Interview the client and turn an idea into a signed charter and numbered, testable requirements — researching first so questions are about judgement rather than fact, pressing on ambiguity rather than accepting it, and stopping at the client's signature before any planning. Run by the project manager in the main session, once per project, after setup.

Turn a devteam project's signed requirements into a task graph — one file per task with its goal, the requirements it discharges, its declared write scope, its dependencies, its gate, its verification command and its estimate — ordered so the riskiest unknown is answered first. Also decomposes one task into steps. Used by the project manager and the planner agent.

Find and record one up-to-date fact from outside a devteam project — a standard's current edition, a release number, a known defect, current guidance — as a dated, sourced digest citing a primary source. Used by the researcher agent, and inline by anyone for a single fetch.

Pick a devteam project back up after an interruption — a crash, a killed session, a machine reboot, or simply coming back tomorrow. Reconciles what the record claims against what the tree actually holds, reports the difference, and gets the client's confirmation before re-dispatching anything that could destroy work.

Review a pull request or a branch for a devteam project — what changed against what was asked, the evidence behind it, and what a reader six months from now will need. Comments and recommends; never pushes, merges or closes.

Run a devteam project's build loop as the project manager — take the writer lock, recover stale claims, pin the environment, claim and dispatch one supervisor per task up to the width, independently verify every report before the board moves, schedule checkpoints, batch escalations by reversibility class, and keep the record. Reads width, start and tick. Writes no product code.

Scaffold the devteam pipeline into a project — install the artifact set, detect the project's existing toolchain, agree the minimal permission grant with the client, and print the one line to run next. Use once per project, before onboarding. Never overwrites an existing devteam/ directory.

Report where a devteam project actually stands — what is running, what is blocked, what is waiting on the client, what was decided without them, and what the evidence says has genuinely been discharged. Reads the board, the record and the tree; changes nothing.

Run one task of a devteam project — read the task and what it must satisfy, decompose it into steps, dispatch one worker per step, verify every step before accepting it, escalate what the project's documents do not settle, and report upward with every worker report appended verbatim. Used by the supervisor agent.

Independently re-run a devteam report's checks against the committed tree and answer PASS or FAIL. Used by the verifier agent before a supervisor accepts a step or a project manager advances the board. Writes nothing.

The worker discipline for a devteam project — the inputs a step dispatch carries, the scope and tree checks before touching anything, what to read and in what order, the commit form, and the REPORT block a supervisor reads. Use when working any step dispatched by a supervisor.