1. Critique before publishing.
Inspect repository and environmental evidence, then classify feedback as blocker, material risk, suggestion, question, or positive observation.
Guided demo
See the two-part Commentary workflow in one review loop.
A practice skill challenges the plan. A technical skill opens the durable review, retrieves independently authored feedback, and waits for the human-controlled gate.
This walkthrough is read-only. It demonstrates operating-surface selection and review behavior without creating a review or mutating a provider.
- Practice first
- One mutation surface
- Authorship-aware
- Human approval
The comment changes the decision, not the prose.
Good plan review starts with goals, assumptions, alternatives, state ownership, cross-cutting risks, verification, and unresolved human choices.
Operating surface
- Local Draft ReviewUse the CLI while the local file remains authoritative.
- Remote review or PRUse MCP for comments, participants, Forms, Research, and gate state.
- Never duplicateDo not perform the same mutation through both CLI and MCP.
Four checkpoints make the loop reliable.
Each checkpoint answers a different question and leaves the final preference or approval decision with a person.
2. Open one durable artifact.
Choose CLI for a local file-backed review or MCP for an existing remote/provider-backed review. Combine them only for distinct operations.
3. Revise without erasing authorship.
Inspect thread authorship and gate state. Reply or revise when appropriate; do not resolve independently authored feedback prematurely.
4. Stop at the human gate.
The agent can report that evidence and acceptance criteria are satisfied. Only the existing human-controlled path approves downstream work.
A realistic plan-review sequence.
The agent separates evaluation, publication, revision, and approval instead of treating them as one tool call.
- 01
Review the plan
Find unsupported assumptions and missing decisions in the actual environment.
- 02
Open Commentary
Create or locate the review through the correct surface and retain its stable identifier.
- 03
Address feedback
Retrieve unresolved comments, preserve author attribution with a stable agentAlias, and revise only the affected source.
- 04
Wait for approval
Reinspect unresolved threads and gate state; stop when the review is decision-complete.
Try the loop with a real artifact.
Start with the sample, then install the review pack when you are ready to connect a local file or remote review.