← Plugin catalog
Business & Operations

Brief

Brief Labs Inc. v1.0.4

Product strategy agent

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Answer product strategy questions
  • Check proposals against decisions
  • Search workspace knowledge

Declared limitations

  • Do not trigger Brief for an unrelated weather request.
  • Do not trigger Brief to modify local source code.
  • Do not trigger Brief for travel booking.

Not specified in the available declarations: pricing & account requirements.

Onboarding example

Catch me up on our product, users, current work, and recent decisions.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

Brief is a product strategy agent that answers from the workspace's decisions, personas, strategy, customers, and competitive landscape. Product teams and coding agents use Brief to load product context, ask for recommendations, check a proposed direction against existing decisions, search workspace knowledge, and record decisions after the user approves them. When you ask it to, Brief can also create, update, or delete workspace data and act in the integrations your workspace has connected. Brief needs a Brief account. It acts within your permissions, in the workspace you sign in to and that workspace's connected integrations. It does not edit or run code in your local repository.

Language: English · Automatically detected from descriptions.

Matches for “agent code”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher full description

Brief is a product strategy agent that answers from the workspace's decisions, personas, strategy, customers, and competitive landscape. Product teams and coding agents use Brief to load product context, ask for recommendations, check a proposed direction against existing decisions, search workspace knowledge, and record decisions after the user approves them. When you ask it to, Brief can also create, update, or delete workspace data and act in the integrations your workspace has connected. Brief needs a Brief account. It acts within your permissions, in the workspace you sign in to and that workspace's connected integrations. It does not edit or run code in your local repository.

Publisher subtitle

Product strategy agent

Publisher description

Brief is a product strategy agent that answers from the workspace's decisions, personas, strategy, customers, and competitive landscape.

What changed

· 3 observations

Capabilities & instructions

App-69e1134e88008191bf1198105b2b5292 updated; open the comparison for details. Brief updated; open the comparison for details. Full description changed from “Brief helps product teams and coding agents retrieve product context, reason over strategy, find and manage decisions, browse workspace knowledge, and...” to...

View comparison →
Capabilities & instructions

App-69e1134e88008191bf1198105b2b5292 updated; open the comparison for details. Brief updated; open the comparison for details. Full description changed from “Brief helps product teams and coding agents retrieve product context, reason over strategy, find and manage decisions, browse workspace knowledge, and...” to...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Keywords

Files & skills

File archives

Plugin package8 files · 15.6 KBBrowse files →
Skill instructions
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 →

Release notes

Updates the publisher and listing details, and adds the Brief skill.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
ISC
Package author
Brief Labs Inc.
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Answer product strategy questions
  • Check proposals against decisions
  • Search workspace knowledge
  • Record approved decisions
  • Change workspace data and connected tools on request

Package observed Nov 16, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 16, 2026 · 06:00 UTC
Latest observed change
Nov 11, 2026 · 00:08 UTC
Collection status
Collected

plugin_asdk_app_69e1134e88008191bf1198105b2b5292

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.