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-launch.md

View on GitHub
---
title: ""
template: launch
version: 1.1.0
description: "Coordinating a built feature's release across teams."
not_for: "Deciding what to build (`brief` or `prd`); a launch talk or slides (`pitch-deck`)."
facilitation_order: [roles, objective, background?, audience, success-metrics, competition?, messaging, pricing?, channels-and-activities, readiness, go-or-no-go-criteria]
guidance: guidance-planning
rubric: rubric-planning
status: draft
created: ""
updated: ""
---

<!-- purpose: Coordinate the release of a built feature across product, marketing, sales and support. -->

<!-- stance: Settle who drives and who approves, and the go or no-go criteria, before planning activities. Ask what each team needs to be ready. -->

<!-- inputs: What is shipping, for whom, and the target date. Only the user knows owners, dates, pricing and channels. -->

<!-- writing: Messaging uses the customer's words, not internal names. -->

<!-- done when: Every team can find its tasks, owner and date, and the go or no-go criteria are written down. -->

# {title}

## Table of Contents

## Roles
<!-- Driver, approver, contributors and informed. -->

## Objective
<!-- What the launch must achieve and the target date. -->

## Background
<!-- optional. What was built and why, for teams new to it. -->

## Audience
<!-- Who the launch is for. -->

## Success metrics
<!-- How the launch will be judged, and when. -->

## Competition
<!-- include when: customers compare this with a competitor. How it compares and how to answer. -->

## Messaging
<!-- What we say, per audience. -->

## Pricing
<!-- include when: the launch changes what customers pay or which plan includes it. -->

## Channels and activities
<!-- Each activity with its channel, owner and date. Once they are listed, weigh them against what is shipping: a small change may need only a note and a support brief. Say which could go and let the user decide. diagram: gantt -->

## Readiness
<!-- Support, documentation, sales enablement and rollback, each with an owner. -->

## Go or no-go criteria
<!-- What must be true on launch day, and who calls it. -->
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