shiplisted

# Ship `/slice` gives you a SPEC. This runs the rest of the chain against it: ``` Prepare --> Implement --> Review --> Verify --> Explain prep tdd 5 lenses real app artifact refactor + fix ``` Each step runs in a context that never saw the one before it. That's the whole point — a session that just wrote the code is the worst possible reviewer of it, and a session that watched the review happen writes a walkthrough that defends the review instead of the change. ## Run it Hand `assets/workflow.js` to the Workflow tool, with the SPEC path as `args`: ``` Workflow({ scriptPath: "<this skill's directory>/assets/workflow.js", args: { spec: "docs/specs/<the-slug>.md" } }) ``` If `scriptPath` is refused, read the file and pass its contents as `script` instead. Don't rewrite it inline from memory. No SPEC path? Ask for one. The script throws without it, and every step after `Prepare` measures itself against those acceptance criteria — the chain has nothing to aim at otherwise. ## When it returns The return value is the whole report — nothing reaches the user on its own. Open the walkthrough for them (`Artifact` with `action: "open"` on `walkthrough`), then say these four things before you summarize anything: - `suiteGreen` — false means the branch is red, whatever else the run says - `bugsFound` — the explainer hit something real while writing up - `criteriaUnbuilt` and `reviewLeft` — what's still owed - `verified` and `lensesUn