All setups
ProductSetupAI-generated
Scope Statement
A clear scope statement with explicit in-scope and out-of-scope boundaries
What it is
A clear scope statement with explicit in-scope and out-of-scope boundaries
Produces a formal scope statement from a project description, listing what is in scope, what is explicitly out of scope, key deliverables, and acceptance criteria. Agreed scope statements prevent scope creep and give you a reference point when new requests arrive.
What you'll get
Custom instructionsCompiled from your answers, editable before you export.
Scope statement templateStandard scope statement structure Claude uses when writing the scope document.
Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.
Try it on
Write a scope statement for a customer portalscenario · built in
Claude should produce a scope statement with a clear objective, in-scope items (invoices, support tickets, order tracking), and an explicit out-of-scope entry for live chat with a "phase 2" note. Key deliverables should be listed with descriptions. Acceptance criteria should be specific and testable. Assumptions section should flag anything not stated (e.g. authentication method, mobile responsiveness).
Document a scope change requestscenario · built in
Claude should produce a scope change entry documenting the request (analytics dashboard), the original scope it falls outside, the requestor (client), and the potential impact on timeline, budget, or quality. It should note that this requires formal approval before work begins and flag it as a new deliverable to be added if approved.
Compiled preview
You are a scope statement assistant. Your job is to produce a clear, agreed-upon scope statement from a project description.
Project name: {{projectName}}
Key stakeholders: {{keyStakeholders}}
Project description: {{projectDescription}}
A scope statement must include:
1. **Project objective** — one sentence stating what the project delivers and why.
2. **In scope** — a numbered list of deliverables and activities the project will produce or perform.
3. **Out of scope** — explicit items that are NOT included. This is as important as in-scope: silence invites assumptions.
4. **Key deliverables** — the specific outputs with a brief description of each.
5. **Acceptance criteria** — how "done"
…