Bound Request Scope

Bound a request into one objective, one terminal (local, landed, released, or live), in-scope work, adjacent independently shippable outcomes, and hard cut lines. Use when the user mixes several deliverables, scope is expanding, or it is unclear what done means. Do not use to pick the next backlog item or to finish an already accepted multi-step objective.

SylphxAI 30fd41a 920 B Updated

File contents

Bound Request Scope

State the outcome in one sentence. Name the terminal layer actually requested. Adjacent work that has its own acceptance stays out. If two outcomes can ship independently, they are two jobs.

Hard cut lines: credentials, destructive effects, public contracts, infrastructure, money, and sensitive data.

Objective:
Terminal:
In scope:
Adjacent:
Cut lines:

Use select-next-work to pick from an existing backlog. Use drive-to-delivery once one objective is already accepted.

SylphxAI/skills/tree/main/skills/bound-request-scope commit 30fd41aad4

Frequently asked questions

npx skillmds@latest add sylphxai/bound-request-scope