Back to the Playbook
DefineDE-01
Write feature brief
Make the case for whether an opportunity is worth investing in, before detailed requirements are written.
Product statusAvailable now
Context in4 required inputsProblem and target users · Customer evidence · Product objectives
TransformationProduct Manager + Product AgentLocal Files · Atlassian · Code Analysis
OutcomeOne- to two-page feature brief.Artifact: Feature brief
Owner
Product Manager
Human-led
Participants · Agents
Head of ProductProduct Agent
Trigger
An opportunity has enough evidence to seek alignment or roadmap consideration.
Required context
Product BrainProblem and target usersCustomer evidenceCustomer evidenceProduct BrainProduct objectivesFilesOpportunity size or business relevance
Optional context
CodeCurrent product behaviourArchitectureRough effort and riskFilesCompetitor evidence
Skills
Local FilesAtlassianCode Analysis
Activity steps
- 1Frame the problem and the target user.
- 2Connect to the objectives and summarise the evidence.
- 3State the approach, the risks and the success criteria.
- 4Ask for the investment decision.
Output
One- to two-page feature brief.
Artifacts
Creates: Feature brief
What good looks like
- Answers «should we invest?».
- No premature detailed requirements.
- Evidence, business case and risks are explicit.
- Success criteria are named.
Quality gate
Product leadership decides on the investment.
Destination
ConfluenceTeklens only
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.