Workflow Manifest
The workflow manifest (_bmad/atlassian/data/workflow-manifest.csv) is the phase-sequenced catalog of all BMAtlassian workflows. The orchestrator and help system use this to determine workflow ordering and detect project progress.
Phase 0 -- Setup
| Code |
Name |
Command |
Required |
Agent |
Description |
| TD |
Transition Discovery |
bmad-atlassian-transition-discovery |
Yes |
-- |
Discover Jira transition IDs and board ID for your project |
| GD |
Git Discovery |
bmad-atlassian-git-discovery |
No |
-- |
Discover Git/GitHub settings and configure integration |
Phase 1 -- Analysis
| Code |
Name |
Command |
Required |
Agent |
Description |
| BP |
Brainstorm Project |
bmad-atlassian-brainstorming |
No |
Analyst |
Generate diverse ideas through interactive brainstorming |
| MR |
Market Research |
bmad-atlassian-market-research |
No |
Analyst |
Market analysis, competitive landscape, customer needs |
| DR |
Domain Research |
bmad-atlassian-domain-research |
No |
Analyst |
Industry domain deep dive and terminology |
| TR |
Technical Research |
bmad-atlassian-technical-research |
No |
Analyst |
Technical feasibility and implementation approaches |
| CB |
Create Brief |
bmad-atlassian-create-brief |
No |
Analyst |
Guided experience to nail down your product idea |
Phase 2 -- Planning
| Code |
Name |
Command |
Required |
Agent |
Description |
| CP |
Create PRD |
bmad-atlassian-create-prd |
Yes |
PM |
Expert-led facilitation to produce your PRD |
| EP |
Edit PRD |
bmad-atlassian-edit-prd |
No |
PM |
Update existing PRD based on feedback |
| VP |
Validate PRD |
bmad-atlassian-validate-prd |
No |
PM |
Validate PRD quality, completeness and cohesion |
| CU |
Create UX Design |
bmad-atlassian-create-ux-design |
No |
UX Designer |
UX design specifications |
Phase 3 -- Solutioning
| Code |
Name |
Command |
Required |
Agent |
Description |
| CA |
Create Architecture |
bmad-atlassian-create-architecture |
Yes |
Architect |
Guided workflow to document technical decisions |
| CE |
Create Epics and Stories |
bmad-atlassian-create-epics-stories |
Yes |
PM |
Create Jira Epics and Stories from the PRD |
| IR |
Implementation Readiness |
bmad-atlassian-implementation-readiness |
Yes |
Architect |
Validate cohesion across PRD, architecture, and stories |
Phase 4 -- Implementation
| Code |
Name |
Command |
Required |
Agent |
Description |
| SP |
Sprint Planning |
bmad-atlassian-sprint-planning |
Yes |
SM |
Create sprint and sequence stories |
| CS |
Create Story |
bmad-atlassian-create-story |
Yes |
SM |
Prepare story with full dev context and subtasks |
| DS |
Dev Story |
bmad-atlassian-dev-story |
Yes |
Dev |
Implement the next story with Jira tracking |
| CR |
Code Review |
bmad-atlassian-code-review |
No |
QA |
Adversarial code review |
| QA |
QA Testing |
bmad-atlassian-qa-testing |
No |
QA |
Generate tests for reviewed stories |
| ER |
Retrospective |
bmad-atlassian-retrospective |
No |
SM |
Review completed epic |
Anytime Workflows
These workflows can be invoked at any point, independent of the phase sequence:
| Code |
Name |
Command |
Agent |
Description |
| QS |
Quick Spec |
bmad-atlassian-quick-spec |
Quick Flow |
One-off tech spec as a Jira Story |
| QD |
Quick Dev |
bmad-atlassian-quick-dev |
Quick Flow |
Implement a quick-spec story directly |
| CC |
Course Correction |
bmad-atlassian-correct-course |
SM |
Navigate mid-implementation changes |
| GPC |
Generate Project Context |
bmad-atlassian-generate-project-context |
Analyst |
Scan codebase for LLM-optimized context |
| DP |
Document Project |
bmad-atlassian-document-project |
Tech Writer |
Scan project and produce documentation |
| PMD |
Party Mode |
bmad-atlassian-party-mode |
-- |
Multi-agent discussion on any topic |
| AR |
Adversarial Review |
bmad-atlassian-adversarial-review |
-- |
Cynical review of any document |
| EPR |
Editorial Review Prose |
bmad-atlassian-editorial-prose |
-- |
Review prose clarity and tone |
| ES |
Editorial Review Structure |
bmad-atlassian-editorial-structure |
-- |
Review document organization |
| ECH |
Edge Case Hunter |
bmad-atlassian-edge-case-hunter |
-- |
Find unhandled edge cases in code |
| WD |
Write Document |
bmad-atlassian-write-document |
Tech Writer |
Multi-turn authoring of technical documentation |
| MG |
Mermaid Generate |
bmad-atlassian-mermaid-generate |
Tech Writer |
Create Mermaid-compliant diagrams |
| VD |
Validate Documentation |
bmad-atlassian-validate-doc |
Tech Writer |
Review document quality and standards |
| EC |
Explain Concept |
bmad-atlassian-explain-concept |
Tech Writer |
Technical explanations with examples |
| PD |
Project Dashboard |
bmad-atlassian-project-dashboard |
-- |
Project status dashboard on Confluence |
| ORC |
Orchestrate |
bmad-atlassian-orchestrate |
-- |
Auto-pilot: polls Jira and dispatches agents |
| BH |
Help |
bmad-help |
-- |
Get help and find your next step |
Detection Methods
The help system and orchestrator detect workflow completion using:
| Method |
How It Works |
config_check |
Check if a config value is populated in module.yaml |
confluence_label |
Search Confluence for pages with a specific label |
jira_issue_type |
Search Jira for issues of a specific type |
jira_sprint |
Check for an active sprint |
jira_status |
Search for issues in a specific status |
jira_label |
Search for issues with a specific label |