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-srs.md
View on GitHub---
title: ""
template: srs
version: 1.1.0
description: "Traceable, verifiable requirements for regulated or contracted work."
not_for: "Product work with no external check (`prd`); what the business requires, before system behavior (`brd`); one feature for a coding agent (`agent-spec`)."
facilitation_order: [introduction, definitions, references, overall-description, functional-requirements, interface-requirements?, quality-requirements, compliance-requirements?, design-constraints?, verification, open-questions, revision-history]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---
<!-- purpose: A requirements baseline an auditor, regulator or contracting party can verify delivery against. -->
<!-- stance: Stakes are regulated or contracted; push for a source on every requirement. One with no source is cut or becomes an open question, because a baseline can only hold what someone can answer for. -->
<!-- inputs: The governing regulations, standards and contract clauses, stakeholders and their needs, external interfaces, prior baselines. Only the user knows which obligations apply and who approves the baseline. -->
<!-- writing: Requirement sections are tables: id, one "shall" statement, source (a stakeholder need, BR-N, RULE-N, regulation clause or contract item), verification method (inspection, analysis, demonstration or test). Ids are never reused. Defined terms are used exactly as defined. -->
<!-- done when: Every requirement has an id, a source and a verification method; every cited regulation, clause and threshold comes from the user or a supplied document; every term is defined. -->
# {title}
## Table of Contents
## Introduction
<!-- Purpose, scope (what the system does and does not do), intended readers. -->
## Definitions
<!-- Terms, acronyms and abbreviations. -->
## References
<!-- Every regulation, standard, contract and document cited, with the version or date as supplied. -->
## Overall description
<!-- Context and boundaries, functions in summary, user classes, constraints, assumptions and dependencies. diagram: flowchart -->
## Functional requirements
<!-- What the system shall do. -->
## Interface requirements
<!-- include when: the system exchanges data with users, hardware, software or networks. -->
## Quality requirements
<!-- Performance, reliability, security, safety, usability, each with a measurable bound from the user or a source. -->
## Compliance requirements
<!-- include when: a regulation, standard or contract clause applies. Each traced to its clause. -->
## Design constraints
<!-- include when: a standard, platform or prior decision limits the design. -->
## Verification
<!-- How the baseline is verified: environments, evidence kept, who accepts it. -->
## Open questions
<!-- Each with what would resolve it. -->
## Revision history
<!-- Version, date, change, approver. -->
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 |