First Project Setup¶

After installation and MCP server setup, configure your project.

Step 1: Edit module.yaml¶

Open _bmad/atlassian/module.yaml and set these values:

Variable	Description	Example
`project_name`	Your project name	`"My SaaS App"`
`user_name`	Your name	`"Jacob"`
`jira_project_key`	Jira project key	`"MYAPP"`
`confluence_space_key`	Confluence space key	`"MYAPP"`
`default_assignee`	Email for auto-assigning stories	`"you@example.com"`

Other settings have sensible defaults. See the Configuration Reference for the full list.

Step 2: Discover Jira Transitions¶

Run the transition discovery workflow to auto-detect your Jira board ID and status transition IDs:

/bmad-atlassian-transition-discovery

This queries your Jira project for available transitions and populates the status_transitions section in module.yaml. You only need to run this once (or again if your Jira workflow changes).

Step 2.5: Git Integration (Optional)¶

If you want BMAD agents to create branches, commits, and PRs automatically:

/bmad-atlassian-git-discovery

This detects your git repo, GitHub remote, and gh CLI, then configures the git_* settings in module.yaml. See the Git/GitHub Integration Guide for details.

Step 3: Start Building¶

Run the help command to get context-aware guidance:

/bmad-help

This inspects your Jira and Confluence for existing artefacts and recommends the appropriate next workflow based on your project's current state.

Fresh project?

If starting from scratch, /bmad-help will guide you to create a Product Brief first. For quick one-off features, try /bmad-atlassian-quick-spec instead.