Manual Review

Sometimes the right way to verify something is for a person to just look at it. /check guide produces exactly that walkthrough.

Invocation

/check guide            for the current work
/check guide latest     for the most recently completed work
/check guide checkout   for a named scope

What comes out of it

A read-only walkthrough: where to go, what to click, what you ought to see, and what it looks like when something’s wrong. It’s written for a person to follow — not something an agent executes.

What it deliberately refuses to do

Guide mode has nothing to do with verification. It never:

• runs a check
• records acceptance
• writes activity state
• marks anything as verified

That boundary is the whole point. A guide that quietly logged acceptance would let “here’s how you’d test it” masquerade as “this was tested.”

Guide against check

	/check	/check guide
Drives the app	Yes	No
Produces evidence	Yes	No
Records acceptance	Yes	Never
Who it’s for	The workflow	You

When it’s the right call

• Visual or design judgment that no assertion can capture
• A flow that needs real credentials or an actual payment method
• Behavior on hardware the agent simply can’t reach
• Wanting a second opinion before merging something sensitive

Configuring when it runs

qualityGates.regular.tryGuide and qualityGates.continuous.tryGuide control this. Both default to manual; setting either to when-user-facing generates a guide automatically for user-facing work. See Project Configuration for the rest.

What this isn’t

For repeatable, human-run testing that leaves a durable record, reach for the QA track instead: /test-cases designs cases for someone to actually execute, and /test-run records what happened as evidence. /check guide is a one-off explanation — it’s not a tracked cycle.