How builders ship the right thing.
Follow a proposal from request to review, bring evidence into a decision, or prepare the handoff to your coding agent. Pick a workflow or role to find the relevant steps.
Review and correct an agent's proposal before it builds
Follow Maria and Sam from a cancellation proposal through correction, approval, and a later cleanup request that uses the same paid-access decision.
Catch the experience gaps in a spec before build
The happy path is in the spec. The empty state, the error, the slow connection, the screen-reader user — usually aren't. Review the spec from the experience side and add the states a coding agent will otherwise invent badly.
Pressure-test a spec against your strategy before the team commits
Compare the proposal with workspace strategy, product boundaries, and constitution rules. Record why this work deserves priority before approving the build.
Review a spec for implementation risk before build
The product side wrote the goal and the evidence. You add what they can't see — the technical edge cases, the constraints, the out-of-scope lines that keep an agent from wandering. Catch the expensive surprises while they're still cheap to fix.
Audit a draft spec for missing edge cases
Compare a draft proposal with its request, identify missing failure cases, and review the agent’s corrections before approving implementation.
Spot the conflict between two stakeholder requests
Keep both stakeholder requests visible, name the conflicting behavior, and review an explicit decision before the coding agent implements it.