jpd-push

Push developed ideas to JPD as Jira issues with a human review gate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes developed ideas to JPD for stakeholder visibility with a human-review gate to prevent silent updates.

Core Features & Use Cases

  • First push creates a new Jira issue for the idea and enters the JPD workflow.
  • Re-push updates an existing Jira issue when the idea has a jira-key.
  • Payload construction uses project configuration from jira-config.md to ensure correct mapping and field population.

Quick Start

Use the /jpd-push command with your developing idea name to push it to JPD after selecting the target.

Frequently Asked Questions about jpd-push

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

FAQPage Schema
How do I push product ideas to Jira with a human review gate?

To push ideas to Jira with a human review gate, the system prepares a Jira payload and requires manual approval before creating or updating issues, ensuring stakeholder visibility without silent updates.

How does Jira handle re-pushing an existing idea versus a first push?

Jira re-pushes update an existing issue when a jira-key is detected, while first pushes create a new issue, automatically adjusting the Jira payload based on the presence of a jira-key.

What is the best way to map fields when creating Jira issues for idea management?

The best way to map fields when creating Jira issues is sourcing project configuration, static mappings, and domain objective options from a jira-config.md file to populate the payload correctly.

Do I need a configuration file to push ideas to Atlassian JPD workflows?

Yes, you need a jira-config.md file to push ideas to Atlassian JPD workflows, as it provides the necessary connection details, static mappings, and domain objective options for payload construction.

Why does pushing to JPD require a manual review process?

Pushing to JPD requires a manual review process to prevent silent updates, ensuring that stakeholders have visibility and explicit approval before an idea enters or updates within the Jira workflow.