team-product-team
Skill2 starsChanged 3 months agoMITView on GitHub
Product evaluation team: user value, feasibility, experience quality, and measurement in one recommendation. Use for feature proposals, go/no-go decisions, or scope negotiation.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Do not let feature momentum substitute for user-value evidence.
- Distinctive: line 56
Do not expand scope beyond the feature under review.
- Distinctive: line 57
If team cannot reach consensus, state the disagreement and escalate.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Team
Purpose
Decide whether a feature or product move is worth doing, feasible to ship, and measurable after launch.
Composition
- role-product-manager: user value, prioritization, outcome framing
- role-technical-product-manager: feasibility, dependencies, hidden complexity
- role-game-designer: player experience quality, engagement, progression
- role-analytics-engineer: success metrics, experiments, validation plan
- Synthesis: conflict handling, acceptance
Use When
- Evaluating feature proposal, roadmap item, scope trade-off
- Making go/no-go product decision
- Deciding MVP vs later phases
- Checking measurable success criteria
Do NOT Use When
- Pure implementation review with no product decision
- Architecture-only or deployment-only
- Economy-specialist question (use
team-economy-team)
Workflow
- Define user problem, audience, expected outcome, and current status quo or workaround.
- Pressure-test the narrowest buildable wedge before endorsing broader scope.
- Review value, feasibility, experience quality, and measurement together.
- Make scope cuts explicit; compare alternatives only when multiple plausible directions would change the decision.
- Produce recommendation with launch conditions and success checks.
Default Output
PRODUCT TEAM REVIEW
===================
Problem: user need, target segment, current status quo
Recommendation: go / no-go / re-scope, narrowest wedge
Scope: explicit cuts, alternatives if decision-relevant
Risks: feasibility, experience, adoption/measurement risks
Measurement: success metric, guardrails, post-launch checksConflict Resolution
- Product Manager has final go/no-go decision. TPM escalates feasibility blockers as hard constraints, not suggestions.
- Game Designer can request experience-quality gates but cannot override product-value judgment.
- Disagreements between specialists are documented in the output, not hidden.
Anti-Drift Rules
- Do not let feature momentum substitute for user-value evidence.
- Name the current status quo before expanding scope.
- Do not expand scope beyond the feature under review.
- If team cannot reach consensus, state the disagreement and escalate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

