Product manager

Skill sairam0424/MindForge/.mindforge/skills/product-manager

MindForge: The Enterprise Agentic Framework for Claude Code & Antigravity. High-performance autonomous execution, wave-parallelism, and multi-tier governance for production-grade AI engineering.From the repository description

Install

npx -y skills add sairam0424/MindForge --skill product-manager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, 915 tokens by cl100k_base, as published. Nobody here has run it

Skill — Product Manager

When this skill activates

Any task involving product requirements, user story writing, backlog prioritization, feature scoring, sprint planning, PRD creation, or user journey mapping.

Mandatory actions when this skill is active

Before

Define the problem — Articulate the user problem with evidence (tickets, data, interviews). No solutions yet.
Identify personas — 1-3 specific personas with context, goals, and frustrations.
State success metrics — Define how to measure success BEFORE designing the solution.

During

PRD structure (6 mandatory sections)

Problem Statement — data-backed, who has it, how we know
User Personas — context, goal, frustration per persona
Requirements — functional (numbered, prioritized) + non-functional (perf, a11y)
Success Metrics — current baseline, target, measurement method per metric
Scope + Timeline — phases with explicit out-of-scope items
Risks + Mitigations — risk, probability, impact, mitigation plan

User story format

As a [persona], I want [action] so that [outcome/value].

Rules:
  - One story = one testable behavior
  - Always include "so that" (forces value articulation)
  - Completable in one sprint (split if larger)
  - Every story has acceptance criteria attached

Acceptance criteria (Given/When/Then)

Scenario: [descriptive name]
  Given [precondition/context]
  When [action taken]
  Then [observable outcome]
  And [additional assertions]

Cover: happy path, edge cases, error states, boundary conditions.

RICE scoring

Score = (Reach * Impact * Confidence) / Effort
  Reach: users affected per quarter
  Impact: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal
  Confidence: 100%=high, 80%=medium, 50%=low
  Effort: person-weeks

Show the math. Rank by score. Communicate rationale for top picks.

MoSCoW prioritization

Must Have: non-negotiable for launch (failure without these)
Should Have: expected, but launch survives without them
Could Have: nice-to-have if time permits
Won't Have: explicitly deferred (prevents scope creep)

Jobs-to-be-Done framework

Interview structure (45-60 min):
  1. First Thought — trigger that started the search
  2. Passive Looking — alternatives considered
  3. Active Looking — event that forced action NOW
  4. Decision — why this solution, what almost stopped them
  5. Satisfaction — does it deliver, what would cause switching

Output: "When [situation], I want to [motivation], so I can [outcome]."

User journey mapping

Stages: Awareness → Consideration → Setup → First Value → Expansion
Per stage: Actions, Touchpoints, Emotions, Pain Points, Opportunities, Metrics

Identify the critical drop-off points and design interventions for each.

After

Validate with users — Show PRD to 2-3 target users. Confirm problem resonates.
Engineering feasibility — Tech lead confirms effort estimates and constraints.
Stakeholder sign-off — Explicit agreement on v1 scope vs deferred.
Define done — What must be true (metrics hit, not just code deployed).

Self-check before task completion

Problem statement evidence-backed (data, quotes, ticket volume)
Personas specific with context, goals, and frustrations
Success metrics have baseline, target, and measurement method
Stories follow "As a... I want... So that..." with acceptance criteria
Backlog prioritized with visible math (RICE/MoSCoW/WSJF)
Scope states what is OUT as well as IN
User journey maps full experience from awareness to expansion
Engineering validated feasibility and effort

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product growth skills give in 915 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

articulate the user problem with evidence
identify one to three specific personas
structure the PRD with six mandatory sections
write user stories in the As-a I-want so-that format
attach acceptance criteria to every story
show the math for RICE prioritization

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.