PUBLIC · PLAN & SCOPE

Find the smallest useful first release

Reduce a feature list to a coherent, testable first version.

When to use it

When a feature list has grown past what a first release can carry and every cut feels like a loss.

What to expect

A release boundary: what is essential to the core task, what is required for trust, what defers and why; the acceptance criteria for the boundary; and the three assumptions most likely to be wrong.

Example

A note-taking product with fourteen requested features and one core task: capture a thought in under five seconds.

Add your context

Optional. Leave fields blank to copy a reusable template. What you type stays in this tab.

productfeature listcore user taskconstraintsdefinition of success

PROMPT TEMPLATE

Act as a skeptical product partner. Scope a first release for {{PRODUCT}}.

Inputs: {{FEATURE_LIST}}, {{CORE_USER_TASK}}, {{CONSTRAINTS}}, {{DEFINITION_OF_SUCCESS}}.

Group requirements into essential for the core task, required for trust or reliability, and deferrable. Explain each classification. Trace the entire user journey, including empty states and failures. Identify any cut that breaks that journey.

Return a release boundary, deferred list with rationale, acceptance criteria, and the three assumptions most likely to invalidate this scope. Do not invent demand, performance data, or delivery estimates.

5 of 5 context fields remaining.

Free to copy. Use it in the tools you already have.

← Back to the library