Skip to content

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

bmad-agent-analyst

Unverified

Mary, the Business Analyst. Use when the user asks for Mary, the analyst or the business analyst, wants market or competitive research, or needs help analyzing or working through an analysis.

FileKindSize
SKILL.mdskill md4.6 KB
assets/brief-view.htmlother4.4 KB
assets/prfaq-view.htmlother5.0 KB
assets/rubric-prfaq.mdmarkdown902 B
assets/template-brd.mdmarkdown3.4 KB
assets/template-brief.mdmarkdown4.0 KB
assets/template-prfaq.mdmarkdown6.8 KB
bmod.tomlconfig214 B
customize.tomlconfig3.9 KB
evals/triggers.jsonconfig2.3 KB

assets/template-brief.md

View on GitHub
---
title: ""
template: brief
version: 1.1.0
description: "Why to build a product, or pitching it, in a page or two."
not_for: "Committed work that needs requirements (`prd`); a formal funding decision on cost and return (`business-case`); testing a problem before any solution exists (`opportunity`)."
paced: true
facilitation_order: [problem, solution, what-makes-it-different, who-it-serves, success-criteria, scope, the-ask?, vision?, executive-summary]
guidance: guidance-planning
rubric: rubric-planning
view: brief-view.html
html_view: always
status: draft
created: ""
updated: ""
---

<!-- purpose: Say why to build something and what it is, or pitch it. -->

<!-- stance: Push hardest on the problem and on what makes it different, where briefs most often overclaim. Ask for the strongest evidence that someone actually wants this, and the smallest version someone would pay for. Take a position on each answer and say what evidence would change it. Before drafting, list the premises as numbered statements for the user to agree or disagree with. The brief serves the product's story: add a section the product needs. -->

<!-- inputs: Only the user knows who it is for and why now. -->

<!-- writing: One to two pages. Never invent a moat, market size, quote or metric. -->

<!-- done when: Someone who reads only the executive summary can say what this is, who it is for, and why it matters now. -->

# {title}

## Table of Contents

## Executive summary
<!-- Distill what the other sections settled into two or three paragraphs of narrative, compelling enough to stand alone: what this is, the problem it solves, why it matters and why now. Draft it yourself, then ask the user whether a sponsor who reads nothing else would know what to do. Done when it says nothing the sections do not hold. -->

## Problem
<!-- Push hardest here, where briefs most often overclaim. Who feels the pain, how they cope today, and what the status quo costs them, with real scenarios, real frustrations and real consequences. Ask for the strongest evidence that someone actually has this problem; a problem the user assumes, rather than has seen, is said to be one. Done when the user can name someone who has it and what it costs them. -->

## Solution
<!-- What gets built, the form it takes (app, web tool, service), and how it solves the problem, as experience and outcome rather than implementation. Pull the user back from features and technology to what changes for the person in the problem. Done when each part of the solution answers a part of the problem. -->

## What makes it different
<!-- Push hard here too. Why this over the alternatives, including doing nothing; the real advantage, even when it is only speed or focus. Name the alternatives yourself when the user has not, and ask why a customer would switch. Done when the advantage would survive a customer saying "I already use something for that". -->

## Who it serves
<!-- Primary users, vivid but brief: who they are, what they need and what success looks like for them; secondary users when they matter. "Everyone" and "small businesses" are not users; ask for the first person who would use it. Done when the user could find that person. -->

## Success criteria
<!-- Measurable signs it is working, for users and for the business. Ask what number would make the user stop, not only what would make them celebrate. Done when each criterion could be checked. -->

## Scope
<!-- What the first version includes and what it leaves out: a tight boundary, not a feature list. Ask for the smallest version someone would pay for or switch to. When the list outruns what a first version needs, say so, suggest what could wait and why, and let the user decide. Done when the boundary is one the user would hold. -->

## The ask
<!-- include when: the brief pitches a sponsor. What the money or time buys, what is still unknown, the running cost, and when the sponsor can stop. -->

## Vision
<!-- optional. Where this goes in two or three years if it works, inspiring but grounded. -->
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