pdm-charter

Decompose Maya epics into stories and create linked GitHub issues.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/refluster/ai-native-article --skill pdm-charter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdm-charter
Source: https://github.com/refluster/ai-native-article/tree/main/workforce/skills/pdm-charter
Command: npx skills add https://github.com/refluster/ai-native-article --skill pdm-charter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the conversion of Mayan epics into detailed stories suitable for operator approval and tracking as GitHub issues.

Core Features & Use Cases

  • Epic to Story Decomposition: Reads accepted epics and proposes a story breakdown.
  • Operator Approval Process: Facilitates the review and approval of proposed stories.
  • GitHub Integration: Creates linked GitHub issues and enables further development and tracking.

Quick Start

Trigger the decomposition of the epic found at 'workforce/docs/epics/epic-011-foo.md'.

Frequently Asked Questions about pdm-charter

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

FAQPage Schema
How do I automate epic decomposition into stories for GitHub tracking?

You can streamline epic decomposition by reading accepted Maya epics, proposing detailed story breakdowns, and creating linked GitHub issues for operator approval.

What is the operator approval process for story breakdown?

The operator approval process facilitates the review of proposed stories generated from Maya epics before they are created as linked GitHub issues for tracking.

Does this workflow automation create linked GitHub issues from Maya epics?

Yes, workflow automation creates linked GitHub issues from accepted Maya epics by decomposing them into detailed stories and linking them back to the epic source.

How do I start epic decomposition using a markdown file path?

Start epic decomposition by triggering the workflow with the direct path to your accepted epic markdown file, such as 'workforce/docs/epics/epic-011-foo.md'.

Can I use this for story breakdown if my epics are not accepted in Maya?

No, story breakdown operates strictly within the workflow of accepted epics in Maya, meaning epics must be accepted before decomposition and GitHub issue creation can proceed.