What shipped
Scope Fence is a self-contained browser tool for fencing an MVP. Title the product, add feature cards with effort (S/M/L mapped to points, or 1–8), and park each as In (inside the fence), Maybe (on the rail), or Out (explicitly cut). A three-column board shows committed vs tempting vs discarded scope; stats track In/Maybe effort and a leak risk score that rises when high-effort items sit in Maybe or when Out items get resurrected. Presets cover a landing page MVP, an AI ops pilot, and an internal admin tool. Copy a plain-text scope receipt for Slack or a PRD. Optional localStorage persistence; no accounts, no network beyond fonts.
How to try
- Open the live demo (iframe on the right, or full-page link below).
- Load a preset (start with Landing page MVP) or title your own fence.
- Move features between In / Maybe / Out; watch leak risk and effort totals update.
- Hit Copy scope receipt for a plain-text dump you can paste into Slack.
Scope trim
No drag-and-drop (buttons only), no collaboration, no story-point sync with Jira/Linear, and no export formats beyond clipboard text. Leak risk is a documented heuristic (Maybe effort + high-effort Maybe bonus + Out→In/Maybe resurrect penalty), not a delivery forecast. Persistence is local to the browser only.
Limitations
- Leak risk is illustrative — it ranks relative scope creep pressure, not calendar risk.
- Effort is coarse (S/M/L or 1–8); real estimates still need a conversation.
- Clipboard copy needs permission; otherwise select the receipt manually.
- Not a roadmap or backlog tool — use it to draw the fence, then track work elsewhere.
Suggested next steps
- Shareable URL hash encoding the board for async review.
- Optional “owner” and “must-ship-by” on In cards.
- Export a tiny Markdown or PNG card for Slack.