team-brief SKILL.md skillA
team-brief from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/team-brief@git:20260303.e2bea1ePins git:20260303.e2bea1e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/pm/team-brief/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.e2bea1e, committed Mar 3, 2026
- Size
- 3,550 bytes
- Repository stars
- 25
- License
- MIT
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".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## 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: …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/team-brief@sha256:e33cde912911f137The line at the top of this page pins the label git:20260303.e2bea1e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wz2zu5vvz2hwawhq)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3550 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 25 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wz2zu5vvz2hwawhq GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/team-brief GET https://markdownregistry.com/api/v1/blob/e33cde912911f1379a659eebe201d02d64553cca874851e2702804887ff1fce2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills