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-prd-light.md
View on GitHub---
title: ""
template: prd-light
version: 1.1.0
description: "A short PRD with enough technical detail for a very simple project."
not_for: "Work with real stakes or several people building from it (`prd`); learning fast before committing (`prototype-plan`); one feature for a coding agent (`agent-spec`)."
facilitation_order: [vision, users-and-journeys, features-and-requirements, non-goals, technical-approach, success?, open-questions]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---
<!-- purpose: Requirements and enough technical direction to start building a very simple project from one document. -->
<!-- stance: Keep it light: drop a section that does not earn its place and never add one just because a full PRD has it. Technical choices are the user's, so ask only what changes the build. With no preference and nothing already built, suggest a starter project to build from, checked on the web for what is current. -->
<!-- inputs: What it is, who it is for and what is out; where it will be built and the platform if the sources do not say. -->
<!-- writing: About 1,250 words; a project that needs more is a `prd`. FR ids are global. Unlike a full PRD, technical decisions expensive to reverse belong here. -->
<!-- done when: Every FR can be checked, the scope edges are explicit, and a builder could start from this file alone. -->
<!-- next: When the product has screens, offer `bmad-ux` first. Then offer either breaking it into smaller tickets with Sofia (`bmad-agent-po`), or handing it to `bmad-build-auto` to build the whole thing as a POC. For the POC, wait for `status: final` and the user's yes, then invoke `bmad-build-auto` with this file's path; it stops on a dirty working tree or a branch that does not fit, so check both first and offer to commit this run or make a branch. -->
# {title}
## Table of Contents
## Vision
<!-- A short paragraph: what this is, who it is for and why it is worth building. -->
## Users and journeys
<!-- Who uses it, and a sentence for each journey that matters. -->
## Features and requirements
<!-- By feature, nested FR-N: "[Actor] can [capability] [under conditions]", each with one checkable result. -->
## Non-goals
<!-- What this will not do, with a one-line reason where it matters. Once the features are out, if the list is more than a first version needs, say so, suggest what could wait for a later version and why, and let the user decide. -->
## Technical approach
<!-- Where it is built, platform, stack and any starter project, then data and storage, integrations, hosting and any other decision expensive to reverse. Flag the rest for the builder instead of choosing. Enough to start, not an architecture. -->
## Success
<!-- optional. One sentence on how the user will know it worked. -->
## Open questions
<!-- Each with who answers it. -->
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 |