跳到正文
cccskills
免费在 GitHub 公开

team-brief

Write an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Overview

Based on Empowered by Marty Cagan. The difference between a feature team and an empowered product team is what they're asked to deliver. Feature teams get a roadmap of features to build. Empowered teams get a problem to solve and the autonomy to figure out how.

A team brief is the artifact that makes empowerment concrete. It gives the team a clear outcome to own, context to understand the problem, and constraints to work within - without prescribing the solution.

Workflow

Step 1: Define the team's mission (one sentence)

The mission is why this team exists. It should be stable for 12-24 months. Format: "Enable [user type] to [achieve outcome] so that [business result]."

Example: "Enable [your product] users to onboard independently so that time-to-first-value drops under 3 days."

Step 2: Set the objective (this quarter)

One specific outcome the team owns this quarter. This is NOT a feature - it's a measurable change in user or business behavior.

Bad: "Build a new onboarding flow" Good: "Increase onboarding completion rate from 45% to 70%"

Step 3: Provide context

Give the team what they need to make good decisions:

  • Customer insight - what you know about the problem from discovery
  • Business context - why this matters to the company now
  • Constraints - technical, legal, or business limits they must work within
  • What's already been tried - avoid sending them down known dead ends

Step 4: Define success metrics

Quantify the objective:

  • Primary metric (the one that matters most)
  • Guard metrics (things the team must NOT break)

Guard metrics are as important as success metrics. A team that hits the primary metric by breaking something else hasn't succeeded.

Step 5: Set the time horizon

How long does the team have to achieve this objective? Cagan's guidance: long enough to make meaningful progress (a quarter minimum), short enough to create accountability.

Step 6: State what's NOT their problem

Explicit scope boundary. Prevents teams from expanding into adjacent problems and losing focus.

Anti-Patterns

1. Briefing solutions, not problems Bad: "Your brief is to build a dashboard with these 5 widgets." Good: "Your brief is to help [user type] track their progress. You decide how."

2. Too many objectives Bad: Team brief with 4-5 objectives. Good: One primary objective per quarter. Cagan: focus is the most important gift you can give a team.

3. No guard metrics Bad: Brief with only success metric. Good: Always include what must NOT get worse. Teams optimize for what's measured.

4. Brief without context Bad: Handing a team a metric without customer insight. Good: Brief includes what you know from discovery so the team doesn't start from zero.

Quality Checklist

  • Mission is stable (12-24 months), objective is this quarter
  • Objective is an outcome (behavior change), not an output (feature shipped)
  • Context includes customer insight, business reason, and constraints
  • Primary success metric is defined and measurable
  • Guard metrics listed (what must not break)
  • Out-of-scope boundary is explicit
  • Time horizon is clear

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

中文简介正在准备中。当前显示原文说明。

qa-aman/claude-skills212026年10月19日 更新

查看 qa-aman 的全部技能

报告此技能的问题