cross-domain

Query Jira issues for cross-domain signals and generate a research artifact.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/lexijamesesq/Incubator --skill cross-domain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-domain
Source: https://github.com/lexijamesesq/Incubator/tree/main/claude/skills/cross-domain
Command: npx skills add https://github.com/lexijamesesq/Incubator --skill cross-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface cross-domain signals from the Jira Product Discovery (JPD) project to help product leaders identify overlap, dependencies, and shared opportunities across teams, enabling faster coordination and better roadmap decisions.

Core Features & Use Cases

  • Surface cross-domain signals from Jira Product Discovery data to inform alignment and collaboration decisions.
  • Retrieve signals across multiple statuses (Experimentation, GTM, Opportunity Identification, Done, Backlog) with partitioned queries to ensure full coverage.
  • Classify signals into Direct overlap, Enabler/dependency, or Convergence, and derive domain labels to aid interpretation.
  • Generate a research artifact documenting identified signals and convergence opportunities for cross-team planning.

Quick Start

Pass the idea name as ARGUMENTS to the cross-domain skill to surface signals and generate the cross-domain research artifact.

Frequently Asked Questions about cross-domain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify cross-domain overlap in Jira Product Discovery ideas?

Identifying cross-domain overlap in Jira Product Discovery involves querying Jira issues across phase-partitioned statuses to surface ideas sharing functionality across product domains. It classifies signals into direct overlap, enabler/dependency, or convergence categories for review.

What are cross-domain signals in product strategy alignment?

Cross-domain signals are indicators of overlap, dependencies, or shared opportunities across different product teams. Surfacing these signals from project data helps product leaders coordinate faster and make informed roadmap decisions by revealing functional convergence.

How do I retrieve Jira issues across all workflow statuses for backlog review?

Retrieving Jira issues across all workflow statuses requires phase-partitioned queries to ensure complete coverage. By querying Experimentation, GTM, Opportunity Identification, Done, and Backlock phases, you capture all relevant signals without missing inactive tickets.

Can I use phase-partitioned MCP queries to find dependencies in Jira backlogs?

Yes, you can use phase-partitioned MCP queries to find dependencies in Jira backlogs. This approach queries specific workflow phases individually to ensure no overlapping functionalities or enabler dependencies are missed during signal retrieval.

What happens if Jira data cannot be fetched during cross-domain signal retrieval?

If Jira data cannot be fetched during cross-domain signal retrieval, the system employs graceful degradation to prevent total failure. It processes available data and returns partial results to maintain workflow continuity despite connectivity issues.

How do I generate a research artifact for cross-team roadmap planning?

To generate a research artifact for cross-team roadmap planning, classify retrieved cross-domain signals with domain labels and signal types. This produces a written document detailing identified convergence opportunities for Phase 3 review.