How does the skill determine the correct tone for a document?

It uses logic based on the card type: Executive tone for Initiatives, Planning tone for Epics, and precise Engineering tone for Stories.

Why are tables and dashes restricted in the formatting?

The methodology prioritizes clean, readable prose and bullet points to ensure documentation is easily digestible and professionally formatted across different project management tools.

What is the Jira hierarchy used by this skill?

The skill enforces a three-level hierarchy: Initiatives for high-level scoping and leadership review, Epics for team-level feature containers, and Stories for atomic engineering tasks.

Does this skill perform file operations or API calls?

This skill provides the reasoning and methodology guidance; all actual file operations and data handling are delegated to the forge-lib CLI component.

PM Methodology & Jira Planning

Name: PM Methodology & Jira Planning
Author: jeremybrice

byjeremybrice

0•

Collaboration Tools

Enforces structured product management hierarchies and professional documentation standards directly within your AI coding workflow.

The PM Methodology skill streamlines the transition from high-level business ideas to implementable engineering tasks by enforcing a strict hierarchy of Initiatives, Epics, and Stories. It guides Claude to adopt the appropriate professional tone for different stakeholders—from executive-level summaries to detailed engineering specs—while maintaining rigorous formatting standards for Jira and project management tools. This ensures that every piece of documentation is consistent, clear, and ready for integration via the Product Forge suite.

Key Features

01Strict documentation formatting to ensure readability and professional standards

020 GitHub stars

03Standardized Jira hierarchy (Initiative, Epic, Story) management

04Automated card type detection based on user intent signals

05Seamless integration with the forge-lib data layer for file operations

06Context-aware tone selection for business and engineering audiences

Use Cases

01Breaking down project epics into actionable developer stories

02Defining high-level business initiatives for leadership review

03Standardizing technical documentation style across a distributed team

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jeremybrice/the-forge pm-methodology

For use in Claude.ai and ChatGPT

Key Features

01Strict documentation formatting to ensure readability and professional standards

020 GitHub stars

03Standardized Jira hierarchy (Initiative, Epic, Story) management

04Automated card type detection based on user intent signals

05Seamless integration with the forge-lib data layer for file operations

06Context-aware tone selection for business and engineering audiences

Use Cases

01Breaking down project epics into actionable developer stories

02Defining high-level business initiatives for leadership review

03Standardizing technical documentation style across a distributed team

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jeremybrice/the-forge pm-methodology

For use in Claude.ai and ChatGPT