claude-sdk-rs: Command for Claude Code

Sequence — Cut a verified seam map into an ordered set of blocks each of which ships something.

Stage 3 of the pre-plan pipeline: /assess → /seams → /sequence → /plan. Method: docs/how-to-plan-with-agents.md in the brain repo.

Variables

$ARGUMENTS — the slug, plus optional flags. Example: orchestration-extensions

Flag	What it does
--single-repo	The work lands in one repo; skip the ownership split and hand off to /plan
--no-redteam	Skip the adversarial pass. Do not use before authoring a real plan

Purpose

Turn seams.md into the cut: an ordered set of candidate blocks, each with an owning repo, each shipping something the operator can use on its own, sequenced by dependency and by what makes later work verifiable.

Output: planning/<slug>/sequence.md. It is the only input /plan (one repo) or /generate-roadmap (multiple repos) needs.

This stage does not author block records or register state.json. That is /plan.

Instructions

1. Read planning/<slug>/seams.md, assessment.md, verification.md, CLAUDE.md, and the in-scope repos' planning/context.md. If seams.md is missing, stop and point at /seams — sequencing from an assessment alone produces a cut along architectural layers, which is the failure mode this whole pipeline exists to avoid.

2. Resolve the forks first. Every fork in seams.md must have an answer before cutting — the cut depends on them. Present them to the user with your recommendations and get a decision. Record each answer and its date in sequence.md. This is a blocking gate: an unresolved fork silently becomes a decision made by whichever agent hits it first.

3. Cut by deliverable, not by layer. The governing constraint:

   Every block ships something the operator can use the day it lands.

   This deliberately rules out the natural engineering cut (all the plumbing, then all the value). Test every candidate block against it: "what can the operator do on the day this merges that they could not do the day before?" If the answer is "nothing yet," the block is mis-cut — re-cut it so it lands with a visible surface, however small (a command that prints a plan, one gate that actually fires, a report you can read in the morning).