m3taz-ahmed/aizee / skills/bmad-agent-pm
bmad-agent-pm
UnverifiedJohn, the Product Manager. Use when the user asks for John, the PM or the product manager, wants a planning document written, updated or reviewed.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| assets/pitch-view.html | other | 4.5 KB |
| assets/template-agent-spec.md | markdown | 2.6 KB |
| assets/template-business-case.md | markdown | 2.2 KB |
| assets/template-charter.md | markdown | 2.3 KB |
| assets/template-experiment.md | markdown | 3.3 KB |
| assets/template-launch.md | markdown | 2.1 KB |
| assets/template-narrative.md | markdown | 2.0 KB |
| assets/template-opportunity.md | markdown | 4.0 KB |
| assets/template-pitch.md | markdown | 2.7 KB |
| assets/template-prd-light.md | markdown | 2.8 KB |
| assets/template-prd.md | markdown | 10.2 KB |
| assets/template-prototype-plan.md | markdown | 4.5 KB |
| assets/template-srs.md | markdown | 2.8 KB |
| bmod.toml | config | 259 B |
| customize.toml | config | 3.0 KB |
| evals/triggers.json | config | 4.2 KB |
assets/template-opportunity.md
View on GitHub---
title: ""
template: opportunity
version: 1.1.0
description: "Whether a problem is worth pursuing, before any solution."
not_for: "A chosen solution that needs a case for building it (`brief`); a funding decision with costs (`business-case`)."
paced: true
facilitation_order: [problem, who-has-it, how-big, alternatives, why-us, why-now, getting-to-market?, success-measures, critical-success-factors, recommendation]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---
<!-- purpose: Decide whether a problem is worth pursuing before anyone commits to a solution. -->
<!-- stance: Keep the talk on the problem. When the user describes a solution, park it and ask what problem it solves. Ask what people do today to solve it, even badly, and what that costs them; who would be upset if the fix disappeared tomorrow, rather than merely interested; and name the person who needs it most. Take a position on each answer and say what evidence would change it. Treat a no-go as a good outcome. -->
<!-- inputs: Evidence the problem exists (support tickets, research, usage data, lost deals). Only the user knows the business objective it serves and why this team should take it. -->
<!-- writing: Every number and piece of evidence names its source; an estimate is tagged `[ASSUMPTION: ...]`. -->
<!-- done when: The recommendation follows from the sections above it, and a reader could disagree with it on the evidence stated. -->
# {title}
## Table of Contents
## Problem
<!-- The problem in the customer's terms, with evidence it exists. You are a researcher who has seen only the evidence: a solution offered here is parked for later and the user is asked what problem it solves. Ask for the support ticket, the lost deal, the interview quote; a problem the user believes in but has not seen is said to be one. Done when the problem is stated without any solution in it. -->
## Who has it
<!-- The customers or users who feel it, specific enough to find them. Ask who needs it most, and who would be upset if a fix disappeared tomorrow rather than merely interested. Done when the user could name and reach one of them. -->
## How big
<!-- How many have it and what it is worth. You are an analyst who wants a source for every number: work it out from what the user knows, show the arithmetic, and tag each estimate. Done when a reader could check each number. -->
## Alternatives
<!-- How they cope today and what competitors offer. Take the customer's side: what they do now, even badly, and what it costs them. Research competitors now rather than from memory. Done when it is clear why the alternatives are not enough, or that they are. -->
## Why us
<!-- What this team or company has that makes it the one to solve it. You are a skeptical executive: "we're passionate about it" and "we can build it" do not count; ask what others could not easily copy. Done when the advantage names something specific. -->
## Why now
<!-- What changed that makes this the moment, or why it can wait. Ask what is different this year from last; "it can wait" is a good answer when it is true. Done when the timing rests on a change the user can point to. -->
## Getting to market
<!-- include when: the solution would be sold or released to external customers. How it reaches them. -->
## Success measures
<!-- How we would know it worked, including any revenue measure. Ask what result would show it did not work, too. Done when each measure could be checked. -->
## Critical success factors
<!-- What must be true or be built for this to succeed. Ask which of them is not true today; that one is the risk. Done when each factor is something someone could check or build. -->
## Recommendation
<!-- Go or no-go, and the reason. Step back and weigh the sections above; take a position yourself, say it to the user first, and say what evidence would change it. A no-go is a good outcome. Done when the recommendation follows from the evidence above and a reader could disagree with it on that evidence. -->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |