← Back to Product & Project

Plan and manage a sprint with Jira or Linear

Compare product-team workflows by backlog handling, issue creation, capacity, status updates, permissions, and auditability.

Last meaningful review July 20, 2026

The job

You have a backlog or requirements and need to plan and maintain a development sprint in Jira, Linear, or a similar issue tracker.

Includedbacklog refinement and sprint planning · issue creation, prioritization, estimation, and status updates · Jira, Linear, MCP, or API workflows

Not this pageorganization-wide agile transformation · automatic product strategy · GitHub issue triage outside a sprint context

30-second route

01

You need a multi-step, auditable Jira delivery loop with routing, live snapshots, and verification.

It supplies a Jira-connected PM router and verification-governed delivery loop.

Editorial confidence: high
Consider Pm Skills
02

You already have a sprint plan and need to create, query, update, comment on, or transition Jira issues.

It directly documents MCP and REST workflows for Jira issue and sprint operations.

Editorial confidence: high
Consider Jira Integration
03

You need to choose a realistic sprint commitment from history, assess health, or prepare retrospective evidence.

It provides executable velocity, health, and retrospective analytics with explicit data-quality limits.

Editorial confidence: high
Consider Scrum Master
04

You need live Linear issue writes rather than Jira operations or exported-data analysis.

The selected skills evidence Jira delivery, direct Jira operations, or export-based Scrum analytics; none is evidenced here as a general live Linear sprint operator.

Editorial confidence: high
Adapt a Linear-specific workflow.

Before you install

Install all three when you need both planning evidence and Jira execution; use them as complementary options rather than a single chained workflow by default.

Pm Skills adds governed orchestration, Jira Integration supplies direct Jira API/MCP operations, and Scrum Master supplies export-based sprint analytics. Each has explicit source evidence for a distinct portion of the task.

Read the intervention guide →

Source-led comparison

What changes the choice

Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.

Source notes

Inspect evidence and candidate limits 3 candidates

Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.

What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.

01

Pm Skills

Source ↗

Use it forA governed Jira delivery loop that routes sprint, velocity, and Jira-workflow requests to a focused sub-skill.

Avoid ifYou only need straightforward issue creation or status updates and do not need routing or delivery-loop controls.

Actioninstall

EditsNone.

SetupConfigure the bundled Atlassian MCP/OAuth connection before live Jira work.

Inspect workflow and compatibility details

ContextRoutes one PM request at a time, can pull Jira data through its bundled Atlassian MCP, bridge snapshots into sprint analytics, and applies verification gates.

OutputA routed sub-skill artifact plus a short digest; delivery-loop mode records plan, state, gate verdicts, and close handoff.

ControlDeterministic router with explicit verification gates, human owner/reviewer requirements, and approval-required treatment for risky writes.

Invocationpython3 scripts/pm_goal_router.py --text "<the goal>" --output json

Install scopeskill-local

Agent fitStrong for teams wanting an auditable, controlled sprint-management workflow rather than isolated issue operations.

Watch outIt is an orchestrator, not a replacement for its sub-skills; it deliberately routes one lane at a time.

Source-visible capabilitiesJira snapshot to sprint forecastPulls Jira data via MCP, bridges it to sprint schema, and invokes velocity analysis with optional Monte Carlo forecasting.explicit sourceSprint/Jira routingRoutes sprint velocity and Jira workflow requests to scrum-master or jira-expert lanes.explicit source
CompatibilityCodex CLIdeclarednot runtime-testedAtlassian Remote MCPdeclarednot runtime-tested
Public signal490 /SkillsMP source-specificbest-overalljira-delivery-loopauditableexplicit source
02

Jira Integration

Source ↗

Use it forDirect Jira sprint operations: search and retrieve issues, create or update work, list sprint issues, comment, and transition statuses.

Avoid ifYou need capacity forecasting, retrospective analysis, or a broader sprint-coaching workflow.

Actioninstall

EditsNone.

SetupUse the recommended mcp-atlassian server with Python 3.10+ and uvx, or provide JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN for REST access.

Inspect workflow and compatibility details

ContextSupports MCP-based Jira access or direct Jira REST API calls, with explicit issue-operation tools and secure credential guidance.

OutputJira records and updates; the ticket-analysis workflow supplies a structured requirements and acceptance-criteria report.

ControlOperational API workflow; check available transitions before changing status and keep credentials outside source control.

Invocationuvx mcp-atlassian==0.21.0

Install scopeskill-local

Agent fitBest for an agent that needs to turn a prepared sprint plan into Jira tickets and maintain their status.

Watch outIt documents Jira issue operations, not a full capacity-planning or velocity-analysis method.

Source-visible capabilitiesIssue and sprint operationsSearches with JQL; creates, updates, comments on, transitions, links, and lists issues in a sprint.explicit sourceSecure connection choicesOffers recommended MCP access and a direct REST fallback using environment-held credentials.explicit source
Compatibilitymcp-atlassian MCP serverdeclarednot runtime-testedJira REST API v3declarednot runtime-tested
Public signal494 /SkillsMP source-specificdirect-jira-operationstop-500mcp-or-restexplicit source
03

Scrum Master

Source ↗

Use it forEvidence-based sprint planning, backlog grooming, commitment sizing, and health/retrospective analysis from Jira or similar sprint exports.

Avoid ifYou need the skill itself to create or transition Jira issues live.

Actioninstall

EditsMap Jira or similar-tool sprint exports to the documented JSON schema before running analysis.

SetupPrepare JSON in the supplied sprint-data schema; velocity analysis requires at least three sprints, with six or more recommended for stronger Monte Carlo results.

Inspect workflow and compatibility details

ContextProvides Python workflows for velocity forecasting, sprint-health scoring, and retrospective tracking, then uses those results to set a planning commitment ceiling.

OutputVelocity trends and confidence intervals, health grades with interventions, and retrospective action/theme findings.

ControlData-gated analysis that stops or reports gaps when history or fields are insufficient.

Invocationpython velocity_analyzer.py sprint_data.json --format text

Install scopeskill-local

Agent fitBest for a Scrum team that needs planning evidence and capacity/health calibration alongside a separate Jira-writing tool.

Watch outIt analyzes exported Jira or similar-tool data rather than directly managing Jira tickets.

Source-visible capabilitiesProbabilistic capacity forecastRuns rolling velocity analysis and Monte Carlo forecasts at 50/70/85/95% confidence intervals.explicit sourcePlanning and sprint-health workflowUses the 70% confidence interval as the commitment ceiling and scores reliability, scope stability, blockers, ceremonies, completion, and predictability.explicit source
CompatibilityJira or similar sprint-data exportsdeclarednot runtime-testedPythonappears compatiblenot runtime-tested
Public signal1882 /SkillsMP source-specificsprint-planningcapacity-forecastinganalyticsexplicit source

Still comparing?

Tell us the job, not just the skill names.

Request a task guide
Did this decision map help?