Skip to main content
The same four commands come three ways. Which names you see depends on how you connected: You get one set, not two: with the plugin installed, the CLI login skips the /os-* copies. All of them work on the customer loaded in the session; with none loaded, the agent lists your deployments and asks.

​
What each one does

Requirements. Reads what’s new for this customer since you last looked, compares it with the plan, and proposes a plan change for anything new or different, each cited word for word. You approve it under Needs you on the deployment’s Customer tab. Run it after a customer call or a batch of new tickets. What changed. Summarizes what changed for this customer since your last session, in up to 10 bullets: plan changes, new calls, tickets and emails, changes waiting for you. Check plan. Gets an independent review of your current change. The agent picks the plan items it works on, runs the acceptance scenarios that touch the change and fixes what fails, then runs npx @openscaffold/cli review, which collects the diff itself (staged, unstaged and new files; in a folder git doesn’t track, the files it changed) and prints the verdict, or after about 2 minutes a review id to check with get_review; without a CLI login it calls request_review with the diff. OpenScaffold’s reviewer, separate from your agent, checks that the change does what the customer asked: those items, the customer’s rules and terms, what’s out of scope and your playbooks’ caveats. It doesn’t review code quality. The agent shows you the verdict and findings, fixes blockers and issues, and asks for a new review. The review is the record: it shows on the deployment’s Build tab. See The review. You don’t need the command name. Saying “check my work” (or “review this”, “verify it”) in plain words does the same, and agents are told to request a review before finishing any change. With the CLI’s hooks, Claude Code is also reminded once per session if it edited files and never asked for one. Demo check. For each must-have, looks in the repo for evidence it’s done, and lists done, partial and missing with file references, plus the open questions to raise in the demo.