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-charter.md
View on GitHub---
title: ""
template: charter
version: 1.1.0
description: "One mandate, benefits, scope and governance across several initiatives."
not_for: "A single initiative (`brief` or `prd`); funding one piece of work (`business-case`); choosing a strategy (`narrative`)."
facilitation_order: [justification, vision, strategic-alignment, benefits, scope, initiatives, rules?, stakeholders, governance, timeline, risks-and-issues]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---
<!-- purpose: Authorize a program: one mandate over several related initiatives. -->
<!-- stance: When talk drops into features or requirements, note the initiative that owns them and move back up. -->
<!-- inputs: The strategy the program serves and the initiatives in view. Only the user knows the sponsor, decision rights, budget and dates. -->
<!-- writing: No requirements; each initiative gets its own document. About six pages. Ids (SM-N, RULE-N) are global, and each initiative's documents cite them. -->
<!-- done when: Any initiative can be judged in or out of the program from this charter, and anyone can tell who decides what. -->
# {title}
## Table of Contents
## Justification
<!-- Why the program exists and what happens without it. -->
## Vision
<!-- The end state the program delivers. -->
## Strategic alignment
<!-- The strategy or objectives it serves. -->
## Benefits
<!-- SM-N measurable outcomes, each with an owner and an expected date. -->
## Scope
<!-- What the program covers and excludes. -->
## Initiatives
<!-- Each initiative in one line, in dependency order, and their dependencies. Once they are listed, ask which must come first and which could wait until the first has reported. When the list outruns the people or the budget, say so and make the case for running fewer at once; the user decides. diagram: flowchart -->
## Rules
<!-- include when: something binds every initiative, whichever one it touches. RULE-N, one line each. A rule from a `brd` keeps its id. -->
## Stakeholders
<!-- Who is affected and who must be involved. -->
## Governance
<!-- Sponsor, decision rights, review cadence and escalation. -->
## Timeline
<!-- Phases and milestones. diagram: gantt -->
## Risks and issues
<!-- Program-level risks and open issues, each with an owner. -->
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 |