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-business-case.md
View on GitHub---
title: ""
template: business-case
version: 1.1.0
description: "Funding approval: cost, expected return, go or no-go."
not_for: "Whether the problem is worth pursuing (`opportunity`); one mandate over several initiatives (`charter`); requirements to build from (`prd`)."
facilitation_order: [sponsors, hypothesis, business-outcomes, leading-indicators, background?, scope, nonfunctional-requirements?, mvp-and-what-follows, cost, return, recommendation]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---
<!-- purpose: Get a go or no-go funding decision on a piece of work. -->
<!-- stance: A missing cost or return figure is an open question, whatever the stakes; never estimate it. -->
<!-- inputs: The sponsor, cost estimates, expected return and its basis: only the user or their finance partner has these. -->
<!-- writing: One page, two at most. -->
<!-- done when: A funder could decide go or no-go from this document alone, and every figure names its source. -->
# {title}
## Table of Contents
## Sponsors
<!-- Who funds the work and who owns it. -->
## Hypothesis
<!-- For whom, what need, what this is, the benefit, and the alternative it beats. -->
## Business outcomes
<!-- The measurable results expected if the hypothesis holds. -->
## Leading indicators
<!-- Early signals of whether the outcomes are on track. Ask what reading would make the sponsor stop funding it, and write that down. -->
## Background
<!-- optional. Context and analysis the decision rests on. -->
## Scope
<!-- What is in and what is out. -->
## Nonfunctional requirements
<!-- include when: performance, security, compliance or similar constraints change the cost or the risk. -->
## MVP and what follows
<!-- The smallest version that tests the hypothesis, and the features it may lead to. When the plan spends more than the hypothesis needs before anyone learns whether it holds, say so, name what could wait, and make the case for funding the test first. The user decides. -->
## Cost
<!-- MVP cost and total cost, each with its basis, and whether the work is built in house or bought. -->
## Return
<!-- The kind of return and its expected size, with its basis. -->
## Recommendation
<!-- Go or no-go, and the reason. -->
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 |