Menu
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
| name | atlassian-jira-sync |
| description | Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues. |
Check Jira for assigned issues and sync with local task management.
Call jira_search with JQL:
assignee = currentUser() AND status != Done ORDER BY priority DESC
Check Tasks/ for existing files with Jira references:
jira_key in YAML frontmatterJira Issues (8 active):
**Blockers/Critical**
- PROJ-123: Production bug in auth [In Progress]
**High Priority**
- PROJ-124: API rate limiting [To Do]
- PROJ-125: Update deployment docs [In Review]
**Normal**
- PROJ-126: Refactor logging [Backlog]
3 issues not yet in local Tasks. Create them?
| Option | Description |
|---|---|
| Create all | Add all new issues as local tasks |
| Select specific | Choose which to sync |
| Skip | Continue without syncing |
For each issue to sync, create task file:
---
title: [Issue summary]
category: technical
priority: [Map from Jira priority]
status: n
jira_key: PROJ-XXX
---
| Jira | Personal OS |
|---|---|
| Blocker | P0 |
| Critical | P0 |
| High | P1 |
| Medium | P2 |
| Low | P3 |
User: "What should I work on today?"
Agent:
jira_key in frontmatter for bidirectional syncUse this skill when the task directly matches the workflow described above.
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.
Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.
Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.
Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.
Generate rigorous stakeholder challenge questions for proposal or meeting preparation.
Analyze competitors using Porter's four-component model - drivers, assumptions, strategy, capabilities.