⌨️ Reference

Command Reference

Every command available across all pipeline stages. Commands are issued as plain text in the AI conversation. Gate commands advance the pipeline; utility commands query or modify state without advancing.

Agent Activation

Phrase	Effect
Start agent 0	Activate Orchestrator — read `0__Orchestrator_Agent.md`
Start agent 1	Activate Discovery — read `1__Product_Discovery_Agent.md`
Start agent 2	Activate Planner — read `2__Technical_Planning_Agent.md`
Start agent 3	Activate Builder — read `3__Application_Builder_Agent.md`
Start agent 4	Activate Critic — read `4__Codebase_Product_Critic_Agent.md`
Start agent 5	Activate Security — read `5__Application_Security_Agent.md`
Start agent 6	Activate Verifier — read `6__Codebase_Verifier_Agent.md`
Start agent 7	Activate Maintenance Agent — read `7__Maintenance_Agent.md` (registered projects only)

Pipeline Gate Commands

Command	Transition	Prerequisites
!plan	Discovery → Planning Phase A	`feature-spec.md` must exist; `!compile` must have been issued
!build	Planning → Builder	`TASK-GRAPH.md`, contracts/, and `FILE_OWNERSHIP_MAP.md` must exist
!critic	Builder → Critic	Builder must have issued SHIP declaration or been paused by human
!security	Critic → Security	Critic must have issued SHIP_READY, CONDITIONAL, or HOLD verdict; `HANDOFF.json v4` must exist
!verify	Security → Verifier	`SECURITY_REPORT.md` must exist; no unresolved CRITICAL findings; `HANDOFF.json v5` must exist

Migration Sub-Commands

These commands are only valid during an active migration risk report from migration_safety.py.

Command	Behavior
!migration-approve	Confirm the DATA LOSS RISK report and proceed with the schema migration. Only valid when `migration_safety.py check` has returned a HIGH or DATA-LOSS risk rating and the pipeline is waiting for human confirmation.
!migration-cancel	Discard the risky schema change and resume the pipeline without it. The migration SQL is discarded and the schema change task is marked BLOCKED with reason "migration cancelled by human".

Spec Change Commands

Command	Behavior
!change [description]	Initiate a spec change. Orchestrator produces a Blast Radius Report listing affected tasks, files, contracts, and estimated scope (Small/Medium/Large). No changes are made until approved.
!change-approve	Approve the pending spec change. Affected tasks are marked STALE; `CHANGE_LOG.md` is updated; Builder resumes with STALE task re-derivation queued.
!change-cancel	Discard the pending spec change. Pipeline resumes in its prior state; no tasks are modified.

Pattern Library Commands

Command	Behavior
!pattern-add	Capture the most recently completed task's implementation as a `PATTERN-NNN` entry. Prompts for domain, stack, and reuse signal before writing to `PATTERN_LIBRARY.md` and `PATTERN_INDEX.md`.
!pattern-list	Display all patterns in `PATTERN_LIBRARY.md` with domain, stack, and reuse signal keywords.

Living Documentation Commands

Command	Output
!docs	`artifacts/docs/OVERVIEW.md` — project summary, tech stack, features, deployment notes
!docs changelog	`artifacts/docs/CHANGELOG.md` — human-readable change history from CHANGE_LOG.md and DECISIONS.md
!docs api	`artifacts/docs/API.md` — endpoint reference derived from openapi.yaml

Session Management Commands

Command	Behavior
!help	Show available commands for the current pipeline stage
!status	Display current pipeline stage, active agent, and task summary
!state	Full pipeline state: HANDOFF version, task counts, change log, patterns applied
!pipeline	Visual pipeline diagram with current stage highlighted and gate commands shown
!budget	Token budget usage for the current stage
!pause	Pause the current agent and save state to CHECKPOINT.md
!reset	Reset pipeline to initial state. Requires typed confirmation: "yes, reset pipeline"
!fork [name]	Create a named pipeline branch for parallel exploration (e.g., comparing two architectures)

Fork & Replay Commands

Command	Behavior
!fork [description]	Fork the pipeline into two parallel branches. Branch A continues the current plan. Branch B uses the alternative described. Spawns two parallel Agent calls. Invokes `session_fork.py create`.
!merge fork-a	Adopt fork-a as the winner. Copies fork-a to the project directory and removes both fork directories. Invokes `session_fork.py merge --branch fork-a`.
!merge fork-b	Adopt fork-b as the winner. Copies fork-b to the project directory and removes both fork directories. Invokes `session_fork.py merge --branch fork-b`.
!replay TASK-NNN	Restore the codebase to the git checkpoint created after TASK-NNN. Marks all later tasks PENDING. Requires `commit_by_task.py` to have run, so each task has a corresponding git commit. Invokes `pipeline_replay.py --task TASK-NNN`.

Pipeline Intelligence Commands

Command	Behavior
!pipeline-health	Show `PROP-NNN` improvement proposals ranked by impact score. Runs `pipeline_improve.py --health`. Proposals are generated by post-run telemetry analysis.
!pipeline-promote PROP-NNN	Apply a specific improvement proposal to the agents directory. Runs `pipeline_improve.py --promote PROP-NNN`. Human reviews the diff before promotion is confirmed.
!budget	Show session token usage, context window percentage, estimated cost, and per-agent breakdown. Runs `token_tracker.py budget`. Reads pricing from `config/pricing.json`.

Maintenance Mode Commands

Available when Agent 7 (Maintenance) is active — i.e., when a registered project is resumed at stage built, critiqued, secured, shipped, or maintenance.

Command	Behavior
!m-build	Human gate: advance from Plan → Build within the current maintenance change cycle. Equivalent to `!build` in the main pipeline but scoped to the mini-plan (1–5 tasks).
!m-status	Show the current change cycle state: cycle ID, scope summary, open tasks, last commit, and registration stage.
!m-skip	Discard the current change cycle and return to the ready state without committing anything.
!m-history	Show all `MAINT-NNN` change cycles applied to this project, with type, surface, and commit reference.
!observe	Enter read-only mode — Agent 7 loads project context but refuses all writes and plan execution. Type `!observe off` to return to normal mode.

💡

Standard commands work inside a maintenance cycle

!retry, !skip, !change, !error-check, !pattern-add, !telemetry, and !docs are all available during an active MAINT-NNN cycle, behaving the same as in the main pipeline.

Discovery-Stage Commands

Command	Behavior
!braindump	Dump all known project details at once; Discovery processes and identifies gaps
!spec	Preview the current spec draft without finalizing
!compile	Finalize the spec; write `feature-spec.md` and `HANDOFF.json v1`
!skip [phase]	Skip a specific discovery phase
!expand [topic]	Drill deeper into a topic with follow-up questions
!cia	Run Competitive Intelligence Analysis during Phase 1

Security-Stage Commands

Command	Behavior
!security	Activate Security Agent; begin tiered 20-domain review
!security domain [N]	Run a specific domain review only (for re-review after fixes)
!security accept [ID]	Formally accept a HIGH/MEDIUM finding with documented rationale

Agent Gate Commands — All Platforms

These commands run inside the project directory, not the agents directory.

Command	What it runs	Stack
`pnpm agent:check`	lint + typecheck + test + build	Next.js / Node.js
`pnpm agent:test`	Unit + integration tests only	Next.js / Node.js
`pnpm agent:e2e`	Playwright E2E suite	Next.js / Node.js
`pnpm agent:visual`	Playwright visual regression	Next.js / Node.js
`pnpm agent:doctor`	Environment health checks	Next.js / Node.js
`pnpm test:perf`	Performance budget gate	Next.js / Node.js
`cargo test`	Rust unit + integration tests	Rust / Tauri
`cargo clippy`	Rust lint	Rust / Tauri
`pytest`	Python tests	Python
`ruff check .`	Python lint	Python
`mypy .`	Python type checking	Python