agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-technical-product-manager/SKILL.md

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.

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
  1. Distinctive:

    Check whether solution creates migration, rollback, or maintenance traps.

    line 28
  2. Distinctive:

    Do not let technical unknowns hide behind optimistic estimates.

    line 44
  3. Distinctive:

    Prefer smaller buildable slice over larger fragile promise.

    line 46

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Clarify product promise, target user, desired timeline, and the current way the team handles the problem.
  2. Map dependencies, hidden prerequisites, integration risks early.
  3. Check whether solution creates migration, rollback, or maintenance traps.
  4. Force explicit scope cuts and the smallest buildable slice when risk exceeds value.
  5. Compare alternatives only when different solution shapes materially change feasibility.
  6. 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 proceeding

Anti-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."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.