Guardrails
- •Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- •Keep changes tightly scoped to the requested outcome.
- •Refer to
opence/AGENTS.md(located inside theopence/directory—runls openceoropence updateif you don't see it) if you need additional opence conventions or clarifications. - •Stage boundary: This stage ends when the review findings are reported. Do NOT automatically proceed to the compound stage.
Steps
- •Inspect the change outputs and identify issues in priority order (severity high to low).
- •Cite file paths for each finding and explain expected vs actual behavior.
- •Call out any remaining risks, edge cases, or test gaps explicitly.
Reference
- •Use
opence show <id>,opence list, and targeted file reads to ground the review.
Stage Complete
When findings are reported, conclude with: "Review phase complete. When ready, invoke /opence-compound to proceed."