/jira-pull
Pull latest changes from Jira (like git pull). Imports status, priority, sprint, and comments.
> /plugin marketplace add anton-abyzov/specweave > /plugin install sw@specweave
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/jira-pull
Context preview
What this command does when you run it.
Pull latest changes from Jira (like git pull). Imports status, priority, sprint, and comments.
Command definition
jira-pull.mddescription: Pull latest changes from Jira (like git pull). Imports status, priority, sprint, and comments.
Jira Pull Command
**Usage**: `sw-jira:pull [increment-id]`
**Purpose**: Pull latest changes from Jira to your local increment (like `git pull`)
---
Quick Start
# Pull for current/active increment
sw-jira:pull
# Pull for specific increment
sw-jira:pull 0005
---
What Gets Pulled
| Field | Behavior | |-------|----------| | **Status** | External ALWAYS wins (QA/stakeholder decisions) | | **Priority** | External wins (stakeholder prioritization) | | **Sprint** | Updated if changed in Jira | | **Comments** | New team comments imported to notes | | **Assignee** | Updated if changed | | **Story Points** | Imported if set |
---
Status Mapping
| Jira Status | SpecWeave Status | |-------------|------------------| | To Do | draft | | In Progress | in-progress | | Code Review | implemented | | In Review | implemented | | QA / Testing | in-qa | | Done / Closed | completed | | Blocked | blocked | | Cancelled | cancelled |
---
Command Behavior
When user runs this command:
1. Resolve Increment
const incrementId = args.incrementId || await findActiveIncrement();
const metadata = JSON.parse(await fs.readFile(
`.specweave/increments/${incrementId}/metadata.json`, 'utf-8'
));
const jiraIssueKey = metadata?.external_sync?.jira?.issueKey;
if (!jiraIssueKey) {
console.log(`Not linked to Jira. Link manually or use: sw-jira:sync ${incrementId}`);
return;
}2. Fetch and Apply
Use Skill tool: Skill({ skill: "sw-jira:jira-sync", args: "Pull changes from Jira for increment {increment-id}.
Issue: {jiraIssueKey}
Steps:
1. Fetch issue {jiraIssueKey} via Jira REST API
2. Compare Jira status vs local status
3. Apply conflict resolution (EXTERNAL WINS for status/priority)
4. Import new comments to increment notes
5. Update sprint/assignee in metadata
6. Display what changed"3. Display Changes
Pulled from Jira
Issue: PROJ-123
Project: My Project
Changes Applied:
Status: In Progress -> Done (mapped to: completed)
Priority: Medium -> High
Sprint: Sprint 23 -> Sprint 24
Comments: 3 new imported
Last synced: 2025-12-04 10:30:00
URL: https://mycompany.atlassian.net/browse/PROJ-123
---
Conflict Resolution
**CRITICAL**: External tool status ALWAYS wins.
| Scenario | Winner | Reason | |----------|--------|--------| | Status differs | **External** | QA/stakeholder decisions | | Priority differs | **External** | Stakeholder prioritization | | Sprint differs | **External** | Sprint planning decisions |
---
Examples
Example 1: Simple Pull
User: sw-jira:pull
Claude:
Pulling from Jira...
Increment: 0005-payment-integration
Issue: PROJ-123
Changes Applied:
Status: In Progress -> Done (completed)
Pull complete!
Example 2: Already Up to Date
User: sw-jira:pull 0005
Claude:
Pulling from Jira...
Increment: 0005-payment-integration
Issue: PROJ-123
Already up to date!
Last synced: 5 minutes ago
---
Related Commands
| Command | Purpose | |---------|---------| | `sw-jira:push` | Push local changes to Jira | | `sw-jira:sync` | Two-way sync (pull + push) | | `sw-jira:import-boards` | Import Jira boards |
Read more
description: Pull latest changes from Jira (like git pull). Imports status, priority, sprint, and comments.
Jira Pull Command
**Usage**: `sw-jira:pull [increment-id]`
**Purpose**: Pull latest changes from Jira to your local increment (like `git pull`)
---
Quick Start
# Pull for current/active increment sw-jira:pull # Pull for specific increment sw-jira:pull 0005
---
What Gets Pulled
| Field | Behavior | |-------|----------| | **Status** | External ALWAYS wins (QA/stakeholder decisions) | | **Priority** | External wins (stakeholder prioritization) | | **Sprint** | Updated if changed in Jira | | **Comments** | New team comments imported to notes | | **Assignee** | Updated if changed | | **Story Points** | Imported if set |
---
Status Mapping
| Jira Status | SpecWeave Status | |-------------|------------------| | To Do | draft | | In Progress | in-progress | | Code Review | implemented | | In Review | implemented | | QA / Testing | in-qa | | Done / Closed | completed | | Blocked | blocked | | Cancelled | cancelled |
---
Command Behavior
When user runs this command:
1. Resolve Increment
const incrementId = args.incrementId || await findActiveIncrement();
const metadata = JSON.parse(await fs.readFile(
`.specweave/increments/${incrementId}/metadata.json`, 'utf-8'
));
const jiraIssueKey = metadata?.external_sync?.jira?.issueKey;
if (!jiraIssueKey) {
console.log(`Not linked to Jira. Link manually or use: sw-jira:sync ${incrementId}`);
return;
}2. Fetch and Apply
Use Skill tool: Skill({ skill: "sw-jira:jira-sync", args: "Pull changes from Jira for increment {increment-id}.
Issue: {jiraIssueKey}
Steps:
1. Fetch issue {jiraIssueKey} via Jira REST API
2. Compare Jira status vs local status
3. Apply conflict resolution (EXTERNAL WINS for status/priority)
4. Import new comments to increment notes
5. Update sprint/assignee in metadata
6. Display what changed"3. Display Changes
Pulled from Jira Issue: PROJ-123 Project: My Project Changes Applied: Status: In Progress -> Done (mapped to: completed) Priority: Medium -> High Sprint: Sprint 23 -> Sprint 24 Comments: 3 new imported Last synced: 2025-12-04 10:30:00 URL: https://mycompany.atlassian.net/browse/PROJ-123
---
Conflict Resolution
**CRITICAL**: External tool status ALWAYS wins.
| Scenario | Winner | Reason | |----------|--------|--------| | Status differs | **External** | QA/stakeholder decisions | | Priority differs | **External** | Stakeholder prioritization | | Sprint differs | **External** | Sprint planning decisions |
---
Examples
Example 1: Simple Pull
User: sw-jira:pull Claude: Pulling from Jira... Increment: 0005-payment-integration Issue: PROJ-123 Changes Applied: Status: In Progress -> Done (completed) Pull complete!
Example 2: Already Up to Date
User: sw-jira:pull 0005 Claude: Pulling from Jira... Increment: 0005-payment-integration Issue: PROJ-123 Already up to date! Last synced: 5 minutes ago
---
Related Commands
| Command | Purpose | |---------|---------| | `sw-jira:push` | Push local changes to Jira | | `sw-jira:sync` | Two-way sync (pull + push) | | `sw-jira:import-boards` | Import Jira boards |
Spec-first AI development: describe a feature → AI creates spec + plan + tasks, builds autonomously, syncs to GitHub/JIRA. Domain-expert skills for PM, Architect, Frontend, QA learn your patterns permanently. Claude Code, Codex, Cursor, Copilot & more.
Repo: anton-abyzov/specweave
Other commands on specweave.
- /abandon
Abandon an incomplete increment (requirements changed, obsolete)
Open command - /ado-cleanup-duplicates
Clean up duplicate Azure DevOps work items for a Feature. Finds work items with duplicate titles and closes all except the first created item.
Open command - /ado-clone
Clone Azure DevOps repositories to local workspace. Use after init if cloning was skipped, or to add repos later.
Open command - /ado-close
Close Azure DevOps work item when increment complete
Open command - /ado-create
Create Azure DevOps work item from SpecWeave increment
Open command - /ado-import-areas
Import Azure DevOps area paths from a project and map them to SpecWeave projects. Creates 2-level directory structure with area path-based organization.
Open command

