playbooks

home / skills / anton-abyzov / specweave / jira-multi-project-mapper

jira-multi-project-mapper skill

/plugins/specweave-jira/skills/jira-multi-project-mapper

This skill maps SpecWeave specs to multiple JIRA projects with intelligent detection and bidirectional sync across teams.

This is most likely a fork of the sw-jira-multi-project-mapper skill from openclaw
npx playbooks add skill anton-abyzov/specweave --skill jira-multi-project-mapper

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
386 B
---
name: jira-multi-project-mapper
description: Expert in mapping SpecWeave specs to multiple JIRA projects with intelligent project detection and cross-project coordination. Use when syncing to multiple JIRA projects (project-per-team, component-based), or managing bidirectional sync across team boundaries.
allowed-tools: Read, Write, Edit, Bash, Glob
model: opus
context: fork
---

Overview

This skill maps SpecWeave specifications to multiple JIRA projects with intelligent project detection and automated cross-project coordination. It is designed for teams that run project-per-team or component-based JIRA setups and need reliable, repeatable syncs. The skill reduces manual ticket routing and preserves traceability across team boundaries.

How this skill works

The mapper scans SpecWeave specs and metadata to determine the appropriate JIRA project(s) for each item, using rules based on components, teams, labels, and custom fields. It creates, updates, and correlates issues across projects, handling bidirectional syncs and conflict resolution policies. The tool reports mapping decisions and generates audit trails for cross-project dependencies.

When to use it

  • You maintain multiple JIRA projects (project-per-team or component-based) and need automated spec-to-ticket routing.
  • You need bidirectional sync between SpecWeave specs and issues across team boundaries.
  • You want to preserve relationships and traceability for specs that span multiple teams or components.
  • You need to enforce consistent field mappings, labels, and workflows across several JIRA projects.
  • You are automating release coordination that requires correlated tickets in different project backlogs.

Best practices

  • Define clear mapping rules using components, team tags, or a dedicated project-detection field in specs.
  • Standardize custom fields and workflows across target JIRA projects to simplify mapping and reduce edge cases.
  • Run dry-runs or preview mode to validate mappings and detect conflicts before making changes in JIRA.
  • Use audit logs and trace IDs in both specs and issues to keep cross-project relations transparent.
  • Limit bidirectional sync to well-scoped fields and use conflict resolution policies (e.g., source-of-truth priorities).

Example use cases

  • Route feature specs to team-specific JIRA projects automatically based on a 'team' tag in SpecWeave.
  • Create correlated stories in a platform project and service projects when a spec affects both layers.
  • Maintain synchronized acceptance criteria and test links by mapping test specs to QA and engineering projects.
  • Coordinate cross-team releases by creating linked epics and tracking dependencies across multiple JIRA backlogs.
  • Migrate a monolith spec repository into a multi-project JIRA layout while preserving historical traceability.

FAQ

How does project detection decide between multiple candidate projects?

Detection uses a priority order: explicit project field in the spec, team/component tags, then fallback rules. You can customize priority and add rule-based overrides.

Can I preview changes before syncing to JIRA?

Yes. The skill supports a dry-run/preview mode that reports proposed creations, updates, and links without modifying JIRA.