`atlassian` — guides
Choose the workflow for tracker intake, story improvement, team status, publishing, flow metrics, or adoption reporting.
These guides help you read Jira and Confluence, improve stories, and measure delivery from your agent.
Which mode are you in?
Section titled “Which mode are you in?”Repo-first projection: Product shaping happens in docs/product/, and Jira is a shallow copy for reporting. Intents and slices go out, and status never comes back. Apply the projection contract by hand.
Tracker-authoritative: Jira holds the team’s real backlog. The workflows read work from Jira and write reviewed story updates back after you approve.
Do not mix the modes: requirements edited in two places diverge silently.
Start here
Section titled “Start here”- Measure delivery — Get cycle time, lead time, and throughput from Jira.
How-to guides
Section titled “How-to guides”- Work with Jira from a conversation — Do common Jira tasks without writing JQL.
- Review your team’s Jira backlog from start to finish — Review the backlog and approve story updates.
- How the Atlassian pack works — How the workflows fit together.
- Authenticate Jira and Confluence with an SSO web session — Sign in through your SSO web session.
- Crawl and publish Confluence — Mirror a space to Markdown, or publish back.
- Read Epic outcomes beside delivery in Jira — See what each Epic delivered.
- Report AI adoption as a delivery lead — Report AI adoption with its caveats.
- Atlassian skills reference — What each skill reads, writes, and asks you to approve.
Explanation
Section titled “Explanation”- Measuring AI adoption with flow metrics — What flow comparisons can and cannot show.