PUBLIC · PLAN & SCOPE

Turn an idea into a focused build spec

Define the problem, the boundaries, and what done should look like.

When to use it

When an idea is clear enough to be exciting and not yet clear enough to build: before the first line of code or the first ticket.

What to expect

A bounded specification: the user problem, confirmed requirements separated from assumptions, in and out of scope, the data and interfaces involved, observable acceptance criteria with failure cases, and an ordered plan with a check per milestone.

Example

A bookmark manager for a two-person team, with the constraint that it must work offline.

Add your context

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

ideasystemconstraintssuccess criteria

PROMPT TEMPLATE

Act as a pragmatic product engineer. Turn the following idea into a bounded implementation specification.

CONTEXT
Idea: {{IDEA}}
Existing system: {{SYSTEM}}
Constraints: {{CONSTRAINTS}}
Success criteria: {{SUCCESS_CRITERIA}}

TASK
1. Restate the user problem and the smallest useful outcome.
2. Separate confirmed requirements from assumptions.
3. Define in-scope and out-of-scope behavior.
4. List the data, interfaces, and dependencies involved.
5. Write observable acceptance criteria, including failure cases.
6. Propose an ordered implementation plan with a verification step per milestone.

BOUNDARIES
Do not write code yet. Do not add features to fill perceived gaps. Ask only questions whose answers materially affect the implementation. Identify unresolved decisions explicitly.

OUTPUT
A concise specification with requirements, exclusions, acceptance checks, and the next actionable step.

4 of 4 context fields remaining.

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

← Back to the library