relayview-skills/packages/planner-scope/scope.md

Scope guide

• State the user-visible outcome and the exact part of the system affected.
• Name prerequisites and neighboring work that change the boundary.
• Cite the current contract, code, or test that supports each existing-behavior claim.
• Distinguish verified current behavior from a proposal.
• Identify one observable success path and one meaningful failure or recovery path.
• Record uncertainty as an open decision; do not turn silence into approval.