Intake · brief-intake

The
intake
form

Seven steps that turn a raw brief into one project file

The same questions the brief-intake skill asks, in order. Every later step of the method reads from the file this produces. Answers save in this browser only and nothing is sent anywhere. Gaps are allowed: an honest UNRESOLVED beats an invented number.

01 · Engagement

What kind of work this is

The engagement type decides which questions matter in step 07. The three people-and-date questions are asked on every project, whatever the type.

Engagement type
Also true

Read everything once and produce nothing. Log what it raises before structuring anything.

02 · Problem

Separate the solution from the problem

Most briefs arrive describing a solution. The problem underneath it gets written in the client’s own words, quoted. Paraphrase is drift.

RuleIf the material contradicts itself, record both positions and what each costs. Do not quietly pick one.
03 · Metric

What number this has to move

If the material does not say, that is an open question, not something to invent. Mark it unresolved and it becomes one of the three questions.

RuleNever fill a metric you were not given. UNRESOLVED is the correct answer.
04 · Users and jobs

Who, and what they are hiring it to finish

Not personas. Jobs. Each row names a person, the thing they are trying to get done, and how that is known rather than assumed.

05 · Constraints

What the work has to live inside

Platform, data, integrations, compliance, timeline, team. Each one is marked by who confirmed it. Anything unconfirmed is flagged for an engineer before it shapes a wireframe.

Why this is hereA stated back-end constraint accepted in week one and questioned at hi-fi is the most expensive mistake in the method. The inventory with the lead engineer sits in phase 01 for that reason.
06 · Assumptions

Everything ambiguous, with an owner and a cost

Every ambiguity becomes a row. The register sorts itself by cost of being wrong, highest first. Cheap-to-test rows get tested this week. Expensive ones get decided by the client, on the record.

RuleEvery assumption needs a named owner. “The team” is not an owner.
07 · The three questions

Three back, not thirty

Pick the three whose answers change the shape of the work, not the three that are easiest to answer. The bank below is filtered by the engagement type from step 01. Click one to place it in a slot, or write your own.

01
02
03
Output · project-brief.md

      

The file every later step reads from

Intake ends when the client signs the problem statement and the metric. If the metric can’t be written, the feature isn’t designed yet.