ai-protocol

Extract and organise an early product or project idea through short executive-level conversation rounds before canonical docs/concept/ files or implementation plans exist. Use when the user invokes concept intake, starts a new project from an unstructured idea, wants to think aloud or dictate rough ideas, or needs a durable intake document without prematurely planning architecture or implementation.

Keep BUILD_STATE.md lean and self-consistent. Use when BUILD_STATE.md has grown large, Now exceeds one screen, logs sprawl, git/test reality contradicts Now, a workspace Components table drifts, or three shipped slices have accumulated since the last archive. Mirrors consolidate-memory, but for the agent working state.

Create or revise an approved mechanical execution contract from accepted docs/concept/ by choosing and verifying the stack, defining validation gates, updating AGENTS.md Project Specifics and BUILD_STATE.md, and conditionally creating or revising DESIGN.md and ROADMAP.md. Use for initial operational planning, explicit re-planning of an operationally planned project, or when new architecture, phases, slices, roadmap order, or release gates must be resolved without writing product code.

Create or revise coherent canonical docs/concept/ documents through short proposal, drafting, research, and refinement rounds without creating implementation plans or modifying mechanical protocol files. Use after accepted concept intake, or when an operationally planned project must deliberately change accepted product intent before re-planning.

Reconcile an existing operational contract against accepted docs/concept/ and implementation reality after toolchain, validation, harness, command, runtime, or other project-specific behaviour changes. Use when the user says sync protocol, implementation may have drifted from AGENTS.md or DESIGN.md, or closeout requires a no-op protocol audit. Do not use for initial planning, roadmap creation, or BUILD_STATE.md generation.