product-cli

Run an end-to-end test of a Product CLI feature in a fresh tmp directory. Build the release binary, init a clean .product/ project, then exercise every CLI command the feature adds — including the existing commands the feature touches — against the new repo. Use when the user asks to "do an end-to-end test of FT-XXX", "verify FT-XXX works in a fresh repo", "test FT-XXX end to end", or "shake out FT-XXX from scratch".

Guide the Build phase of a product session — partition the What into shippable slices, define deliverables with checkable acceptance (§7), dispatch cells into work units, run the autonomous build, and finalize. Use when the session is in the Build phase or the user says "create a slice", "add acceptance", "build the deliverable", "dispatch", "run the build", or "finalize the session".

Launch, resume, and drive a phase-gated What→How→Build workshop session over the Product framework graph, and route to the right phase skill. Use when the user says "start a product session", "run a workshop session", "product session start", "product mcp --workflow", "resume the session", "advance the phase", or "finalize the session". Owns start / status / advance / finalize and the locked-session guardrails; hands the actual authoring to product-what, product-how, and product-build.

Guide authoring the What — the domain model (§3.1) and event model (§3.2) — inside a product session's What phase: bounded contexts, entities, value objects, commands, events, read-models, triggers, systems, flows, plus Deciders (§3.3) and Projectors (§3.4). Use when the session is in the What phase or the user says "model the domain", "add an entity/command/event", "add a system", "derive the decider", or "validate the what".

Cut a new release of the Product CLI by bumping the workspace version in lockstep, committing, tagging `vX.Y.Z`, and pushing the tag to trigger the cargo-dist release workflow. Use when the user asks to "cut a release", "release version X", "ship 0.X.Y", "tag a release", "publish a release", or "bump and tag for release".

Guide authoring the How — the §4 architecture contract — inside a product session's How phase: the Why cascade (decisions → principles → patterns), the application/infrastructure contracts, interfaces, plus archetypes, cells (task-types), and work units. Use when the session is in the How phase or the user says "specify the how", "add a principle/pattern/decision", "set the app contract", "do we need a new archetype", "scaffold a cell/work unit", or "dispatch a cell".

Shake out a full What→How→Build session end-to-end in a fresh `init --demo` repo, driving each phase skill's worked example through the CLI and asserting every phase gate. Use when the user asks to "run the session e2e", "verify the phase skills", "shake out a session end to end", or after changing the domain/how/build tool surface to confirm the skills still hold.