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-agent-spec.md
View on GitHub---
title: ""
template: agent-spec
version: 1.1.0
description: "One feature handed to a coding agent, with tests and acceptance."
not_for: "Work a story or epic ticket already specifies; several features or a product (`prd`)."
facilitation_order: [problem, user-stories, edge-cases, requirements, key-entities?, success-criteria, out-of-scope, assumptions, implementation-context?, open-questions?]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---
<!-- purpose: A feature spec a coding agent can build and test from with no other context. -->
<!-- stance: Draft first from the conversation and the codebase, then ask only what changes scope, security or what the user experiences, each with a recommended answer; read the code for the rest. When the stories outgrow one feature, say so and offer to split the spec. -->
<!-- inputs: The requested behavior, who uses it, the codebase's conventions and terms, constraints and boundaries. Only the user knows priority and what is out. -->
<!-- writing: Behavior, not implementation: no file paths or code, except a fragment that pins a decision more exactly than prose (a schema, a state machine). Success criteria are measurable without knowing the implementation. -->
<!-- done when: Every story has an independent test and Given/When/Then acceptance; edge cases cover what the agent would otherwise guess wrong; nothing about scope is left for the agent to guess. -->
# {title}
## Table of Contents
## Problem
<!-- Who is affected and what they cannot do now. -->
## User stories
<!-- Ordered by priority, P1 first. Each: the story, why this priority, an independent test showing it delivers value alone, and Given/When/Then acceptance scenarios. -->
## Edge cases
<!-- The boundaries, invalid input and failures where a wrong guess would build the wrong thing, and what the system does in each. Leave out what the codebase's conventions already settle. -->
## Requirements
<!-- FR-N, each "The system MUST ..." or "Users MUST be able to ...". -->
## Key entities
<!-- include when: the feature stores or moves data. What each represents and how they relate, without schema detail. diagram: er -->
## Success criteria
<!-- SC-N measurable outcomes. -->
## Out of scope
<!-- What the agent must not build or change. -->
## Assumptions
<!-- Defaults chosen where the input was silent, and existing systems the feature depends on. -->
## Implementation context
<!-- optional. Decisions already made, modules and interfaces touched, and the highest seam where the tests run. -->
## Open questions
<!-- include when: anything remains open. Each blocks handoff until answered. -->
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 |