Analysis

Analysis is the product-owner job on an incoming story (help menu AN, skill bglad-analysis). Investigate the repo, put Open questions on the spec, and split a large idea into extra Jira tasks when needed. Then stop. Do not implement. Developers continue with Dev.

Do not start BMad’s PRD skill (bmad-prd), create-epics, or sprint-planning. The spec lives in the Spec location from install (Jira, Confluence, or markdown).

Open questions and waiting

When Problem or Acceptance cannot be settled from evidence, Analysis writes Open questions on the spec (per clarify_ping: description, comment, or both), may reassign to the existing reporter, and — when the org overlay sets them — transitions to jira_waiting_status and/or adds jira_waiting_label. It then HALTs until answers land on the ticket.

Split and epic

When investigation shows several independently shippable outcomes, Analysis ASKS once whether to split into extra Jira Tasks (bglad-ticket-mr create-issue). Before those creates, it runs ticket-mr squad selection and Jira prerequisites so each task gets the squad’s component and development team (first-use asks and saves into the overlay when those are still empty).

When the split confirms two or more tasks and the operator has not named a parent epic, Analysis ASKS once whether to create an epic that groups them (proposed summary, Epic Name when jira_epic_name_field is set, child list). Yes → create the Epic with the same component and development team, then link children per bglad-ticket-mr references/jira.md. No → link to a named epic or to nothing.

After Problem and Acceptance are on the spec, ASK: run Design (DS) now, or this task is ready for Dev (DEV)? Default is skip to Dev — the implementer fills Design.

flowchart TD
  an[Analyze incoming story] --> settle{Problem and Acceptance explicit?}
  settle -->|no| oq[Open questions on the spec]
  oq --> halt[HALT]
  halt --> resume[Answers on the spec]
  resume --> settle
  settle -->|yes| split{Several independently shippable outcomes?}
  split -->|yes after ASK| tasks[Extra Jira tasks]
  split -->|no| askD{Design now or ready for Dev?}
  tasks --> askD
  askD --> ds[Optional Design]
  askD --> dev[Dev implements]
  ds --> dev

Who	Skill	Menu
Product owner (analysis)	bglad-analysis	AN
Tech lead / architect (optional)	bglad-architecture	DS
Developer	bglad-dev	DEV
Reviewer (or same person)	bglad-review	RV
Tester (or same person)	bglad-qa	QA
Anyone filing a ticket or change request	bglad-ticket-mr	MR
Anyone after the change request	bglad-knowledge	NOTE

A developer handed a raw proposal still uses Dev Open questions, not a switch to Analysis.

Developers implementing a ready task → Dev.