Brief

An idea in your head is nothing a team can work with, and writing it down properly is the part everybody postpones. This skill does it with you in one session. You describe what you want, the skill proposes each section, and you correct it. The result is one page that says why the product should exist and what it has to do.

Skill name: discovery-brief-atlassian. It needs nothing before it. This is where the chain starts.

How to start it

Nothing has to exist before this step. Describe the idea in your own words and say what you want from it:

I'd like to build something that keeps my freelance invoices in order.
Let's write a brief for it.

In a new session, or when another skill would fit your sentence too, name this one:

/discovery-brief-atlassian I want to build a tool for my freelance invoices.
Let's start with the brief.

What it works out with you

Seven sections, one after the other. The skill proposes each one from what you already said, and you correct it. You never face an empty form.

Section	What it wants from you
In one sentence	The idea in one short line: for whom, what, and what it is worth.
Problem / why	The real problem, as text. While your answer stays on the surface, the skill keeps asking: what exactly is wrong, who is affected, and what causes it.
Audience	Two or three user groups, split by role, even when one person does two of them. A role you leave out has needs of its own, and the personas later contradict the brief.
Core capabilities	What the product has to do, as short descriptions and not as single words. The epics later come from these.
Out of scope	What does not belong in the product. The skill asks for this directly, and it is the section that keeps the scope from growing later.
How we know it works	One to three signals you can observe. Not a measurement system.
Assumptions / frame	What is already fixed, the technology you know of, and what you postpone on purpose. For each postponed point it also asks what you have to do today to keep that option open.

One rule holds for all of it: a brief describes a problem and its value, not a solution. If you start listing features, the skill asks you what they are for.

Where it lands

One Confluence page, called <Product> | Brief. At the end you pick the space and the parent page it goes under. This page is the top of the tree. Personas, journeys, the domain model, the technical frame and the design brief all end up under it.

Note

If the page already exists, the skill asks whether to update it or create a new one. It reads your comments on the page first. Your comments are the work order, and it does not touch sections you wrote yourself unless you ask for it.

Next

Personas and journeys. They come from the audience in the brief, and together they have to cover every capability it lists.