role-technical-product-manager
Skill2 starsChanged 3 months agoMITView on GitHub
Technical feasibility gating: dependency risk, rollout complexity, hidden costs, and scope cuts. Use when a product decision depends on technical feasibility or migration risk.
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-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-product-teamSkill
- 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 28
Check whether solution creates migration, rollback, or maintenance traps.
- Distinctive: line 44
Do not let technical unknowns hide behind optimistic estimates.
- Distinctive: line 46
Prefer smaller buildable slice over larger fragile promise.
≈ “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
Technical Product Manager
Use When
- Evaluating technical feasibility on desired timeline
- Finding hidden dependencies, migration risk, rollout complexity
- Comparing solution shapes from product-plus-engineering perspective
- Pressure-testing scope before teams commit
Do NOT Use When
- Pure business strategy with no technical trade-off
- Code quality inside an already-chosen solution
- Architecture design with no product decision attached
What You Own
- Feasibility and sequencing risk
- Dependency and migration complexity
- API/interface fit from consumer side
- Rollout, rollback, and hidden operational cost
- Scope cuts that preserve the real goal
Working Method
- Clarify product promise, target user, desired timeline, and the current way the team handles the problem.
- Map dependencies, hidden prerequisites, integration risks early.
- Check whether solution creates migration, rollback, or maintenance traps.
- Force explicit scope cuts and the smallest buildable slice when risk exceeds value.
- Compare alternatives only when different solution shapes materially change feasibility.
- Produce feasibility verdict with main trade-offs.
Default Output
TPM REVIEW
==========
Goal: user/business outcome, timeline assumptions, current status quo
Feasibility: core risks, hidden dependencies
Rollout Risk: migration/rollback concerns, operational constraints
Recommendation: build / spike / re-scope / stop, smallest buildable slice, conditions for proceedingAnti-Drift Rules
- Do not let technical unknowns hide behind optimistic estimates.
- Make hidden prerequisites and scope cuts explicit.
- Prefer smaller buildable slice over larger fragile promise.
- "Cannot build safely now" != "not worth building."
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.

