Skip to content

m3taz-ahmed/aizee / skills/bmad-agent-pm

bmad-agent-pm

Unverified

John, the Product Manager. Use when the user asks for John, the PM or the product manager, wants a planning document written, updated or reviewed.

assets/template-narrative.md

View on GitHub
---
title: ""
template: narrative
version: 1.1.0
description: "A written argument for leadership to decide a strategy or annual plan."
not_for: "One product idea (`brief`); funding one piece of work (`business-case`); program governance (`charter`)."
facilitation_order: [introduction-and-ask, goals, tenets, state-of-the-business, lessons-learned, strategic-priorities, resource-request?, faq, appendix?]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---

<!-- purpose: Bring leadership to a decision on a strategy or annual plan through a written argument. -->

<!-- stance: Push for the argument and the data behind each claim. Before drafting, list the premises as numbered statements for the user to agree or disagree with. Ask what the readers will object to, and answer it in the FAQ. -->

<!-- inputs: Current results against the last plan and what was learned. Only the user knows the ask, the goals and the tenets their leadership holds. -->

<!-- writing: The body is prose with no bullets, six pages at most; tables and detail go to the appendix. -->

<!-- done when: A reader who has never seen the plan can state the ask, the goals, and why these priorities over others, from the body alone. -->

# {title}

## Table of Contents

## Introduction and ask
<!-- What the document covers and the decision it asks the readers to make. -->

## Goals
<!-- What the plan commits to achieve, measurably. -->

## Tenets
<!-- The beliefs that settle trade-offs when goals conflict. -->

## State of the business
<!-- Where things stand, with the numbers. -->

## Lessons learned
<!-- What worked, what did not, and what it changes. -->

## Strategic priorities
<!-- The few bets for the period and why each follows from the above. -->

## Resource request
<!-- include when: the ask includes people or budget. What is needed and what it buys. -->

## FAQ
<!-- The hard questions readers will ask, answered. -->

## Appendix
<!-- optional. Data tables and detail the body cites. -->
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall