team-mode

Append the [T] token to the work command to spawn a real agent team with a verifier teammate that has an independent context window. Use [T+] to additionally spawn a risk-guard teammate that intercepts high-risk paths like auth, payment, or migration before each unit starts.

A team contract is a .team-contract.md file with YAML frontmatter defining allowed_files, forbidden_surfaces, and required_invariants. It is generated automatically during the plan phase by extracting file lists from implementation units and acceptance criteria from the plan document.

The skill degrades gracefully to role simulation mode where the main agent sequentially performs verification itself. Contract boundaries and risk-guard keyword detection remain active, and a warning announces the fallback behavior.

Only the executor role may modify shared code, preventing conflicts, overwrites, and inconsistent state that arise when multiple agents write concurrently. Verifier and risk-guard roles are strictly read-only and any violation triggers an immediate stop with user confirmation.

The lead receives a FAIL message with the reason and command output, then fixes the issue and requests re-verification. After two failed rounds, a blocked checkpoint asks the user to manually fix, skip verification with a PR annotation, or stop entirely.

Yes, but with degraded behavior. The work command warns and asks for confirmation to proceed without boundary checks, while the review command skips the patch gate entirely and logs a warning that the contract was not found.