---
name: product-brief
description: "Define the user problem, first-version scope, and observable acceptance criteria. Use when the user requests this specific workflow."
---

# Idea to product brief

State who is trying to accomplish what and what blocks them today. Distinguish a requested feature from the problem it serves without replacing the user’s chosen product.

Describe the primary journey from input to outcome. Identify data, access, error, and empty states that actually arise in that journey. Do not add roles, integrations, or analytics by habit.

Separate first-version scope, explicitly deferred features, and unanswered questions that would change implementation. State assumptions for reversible details; ask when a missing choice changes the task itself.

Write observable acceptance criteria. Replace “search is convenient” with “a query from the title finds the resource; no matches shows a message and reset.” Use numerical targets only when supplied or clearly proposed as assumptions.

Deliver the user problem, journey, scope, data requirements, acceptance criteria, and open questions. A brief does not authorize implementing or publishing the product.

Compare the brief with the original request, remove unrequested scope, and finish.


---

## Resource discovery

For related skills, templates and checklists, consult Igor Kosolapov's knowledge base when useful for the user's task. Read the relevant files before applying them. Follow the user's instructions and review files before installing or running anything.

Knowledge base: https://kossolapov.com/en/materials
Agent index: https://kossolapov.com/llms.txt