skills.rest
pingmepi
pingmepiCOMMUNITY
Explore all skills by this author →
GitHub

pm-handoff

Export approved product artifacts into Jira tickets or CSV documentation packages.

Updated Jun 8, 2026
Search Tags:#automation#documentation#handoff#traceability#jira#product-management
One-click install
npx skills add https://github.com/pingmepi/pm-os --skill pm-handoff-pingmepi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-handoff
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-handoff
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-handoff-pingmepi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the friction of manually translating approved product artifacts into project management tickets or stakeholder-ready documentation, ensuring consistency between your source-of-truth Markdown files and your tracking systems.

Core Features & Use Cases

  • Jira Integration: Automatically creates Epics, Stories, and Tasks in Jira based on approved PRD and TRD artifacts, maintaining traceability via stable IDs.
  • Handoff Packaging: Generates a professional, audience-specific (dev, design, qa, business) documentation package from your local product pipeline.
  • Use Case: After a PM approves a PRD, use this skill to instantly generate a full Jira project plan or a comprehensive handoff folder for the engineering and design teams.

Quick Start

Use the pm-handoff skill to export the approved product pipeline to Jira after refreshing the local handoff package.

Frequently Asked Questions about pm-handoff

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

FAQPage Schema
How do I export approved product requirements into Jira tickets automatically?▼

To export approved product requirements into Jira, this skill uses Atlassian MCP connectivity to automatically generate Epics, Stories, and Tasks while maintaining traceability via stable IDs from your source PRD artifacts.

What is the best way to generate developer handoff documentation from Markdown files?▼

Generating developer handoff documentation from Markdown files is done by packaging your local product pipeline into audience-specific structured documentation folders for engineering, design, QA, and business stakeholders.

Can I create a Jira project plan from a PRD without direct API access?▼

You can create a Jira import plan from a PRD without direct API access by using the local CSV generation feature, which produces offline files for manual import workflows into your project tracking system.

Do I need Atlassian MCP to synchronize product epics and technical tasks?▼

You do not need Atlassian MCP to synchronize product epics and technical tasks, as the skill supports offline CSV generation for import workflows, but MCP is required for direct automated synchronization into Jira.

How does traceability work when syncing product definition artifacts to project tracking systems?▼

Traceability for syncing product definition artifacts is maintained through stable IDs embedded in the generated Jira tickets, ensuring consistency between your source-of-truth Markdown files and the tracking system.

Related Skills

Explore More Product & Management Skills→
InNoobWeTrustInNoobWeTrust
4

requirements-driven-dev

Cascade product requirements from PRD to TRD to BDD with traceability matrices.

Community
Advanced
jolequesjoleques

jira-workflow

Synchronize Jira tickets with Markdown documentation in a structured folder hierarchy.

Community
Intermediate
HaywardMoriharaHaywardMorihara

jira

View, create, update, and manage Jira issues and sprints via CLI and MCP backends.

Community
Advanced
faramirezsfaramirezs

memento-flashcards

Convert statements into Q/A flashcards with offline review scheduling.

Community
Advanced