brief5.95 KB
View saved version →
---
name: brief
description: Use Brief as the product-judgment and decision layer for engineering work. Activate when the user asks to ask, check, or record something in Brief; requests product advice or project onboarding; chooses scope, priorities, UX behavior, positioning, or roadmap direction; checks whether a relevant decision already exists; validates a consequential product or architecture proposal; or records a settled decision.
---
# Brief
Brief contains the product strategy, customer evidence, priorities, and decisions that code alone cannot provide.
Use Brief for **what, why, and for whom**. Use the repository for **how**.
When the user says "ask Brief," "check with Brief," "onboard this project," or similar, invoke Brief rather than answering only from local context.
## When to consult Brief
Consult Brief before:
- Recommending product scope, priorities, UX behavior, positioning, or what to build next.
- Endorsing a consequential product or architecture direction.
- Assuming a product or architecture question has not already been decided.
- Explaining why the product behaves a certain way when the answer is not established by code alone.
Do not consult Brief for routine implementation choices that do not affect product behavior, architecture, scope, or policy.
## Load context once
At the start of a fresh conversation, call `brief_get_onboarding_context` once before reasoning about the user's product. If the host or another instruction already loaded that context, do not call it again.
Also call it when the user explicitly asks to onboard, get caught up, or learn what Brief knows. Use the default full scope for an initial primer or broad catch-up, `product` for focused product context, and `identity` only to confirm the workspace.
If Brief has no useful context and the user asked to onboard, gather the minimum framing needed: what the product does, who it serves, and what the team is working on. Then use `brief_ask` with `onboarding: true` to synthesize that context.
If the host exposes MCP prompts, `brief-setup`, `brief-welcome-back`, and `brief-context` are optional shortcuts for these flows. Do not depend on slash commands being available.
## Choose the right operation
- To learn whether something was already decided, use `brief_search` and search decisions.
- For open-ended product advice or option evaluation, use `brief_ask` with `mode: "advise"`.
- To validate a concrete proposal, use `brief_ask` with `mode: "check"`. State the proposed direction and meaningful tradeoffs explicitly.
- After the current user explicitly authorizes recording a settled lasting choice meeting the decision standard below, use `brief_record_decision` with the decision and rationale.
- On hosts that do not render approval cards, use `brief_propose_decision` to save an eligible lasting choice for review instead.
- When a decision needs **someone else's** sign-off, or isn't settled yet, use `brief_propose_decision` instead — it creates a pending proposal directly, without depending on an approval-card-capable host. Never record an unsettled decision as confirmed; propose the lasting rule as a declarative statement for review. If multiple people must sign off, propose once per approver.
## Decision standard
A decision is a rule or choice that will still guide someone after the ticket ships. Ask: "Will this still guide someone after this ticket ships?" State it in plain language in 1–3 sentences, understandable without the ticket, PR or code, and explain why in product or business terms. A durable choice not to build something also counts when its product or business reason survives the ticket. Keep ticket-scoped notes in the ticket, PR description or a code comment. Keep file paths, branch names, function names, flags and run IDs out of decision text; put ticket, PR and decision IDs only in references. When a tool has no references field, keep reference links in the originating ticket or PR and omit IDs from the decision
Preview of the first 4,000 characters. Read full instructions →