pm-publish

Generate and publish Markdown product docs from a PM database.

Updated Oct 17, 2025
One-click install
npx skills add https://github.com/x85446/claudecodetricks --skill pm-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-publish
Source: https://github.com/x85446/claudecodetricks/tree/main/skills/pm-publish
Command: npx skills add https://github.com/x85446/claudecodetricks --skill pm-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PM teams struggle to maintain consistent, up-to-date product documentation across features, requirements, and full specs, often relying on manual assembly from multiple sources.

Core Features & Use Cases

  • Generates markdown docs (Features, Requirements, Full) from a centralized PM database.
  • Keeps an iterator glossary at the top of published docs to ensure consistent terminology.
  • Enables scalable publishing for releases, audits, and stakeholder updates.

Quick Start

Run the command /pm-publish with your target paths to generate and publish product documentation from the PM database.

Frequently Asked Questions about pm-publish

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

FAQPage Schema
How do I automatically generate markdown product documentation from a database?▼

You can automatically generate markdown product documentation from a centralized PM database by running a publish command that extracts features, requirements, and full specs into categorized sections. This ensures consistent, up-to-date product docs without manual assembly.

What is the best way to keep product specs and requirements documentation up to date?▼

Keeping product specs and requirements up to date is best achieved by automating markdown document generation directly from a centralized database source. This enforces consistent terminology through an iterator glossary and outputs categorized sections for stakeholder updates.

How do I publish product docs with consistent terminology across releases?▼

To publish product docs with consistent terminology, you can generate markdown files from a centralized database that automatically inserts an iterator glossary at the top. This enforces standardized naming and descriptions across all published features and requirements.

Can I generate categorized sections for features and requirements from a single source?▼

Yes, you can generate categorized markdown sections for Features, Requirements, and Full product documentation from a single centralized PM database. This enables scalable publishing for releases, audits, and stakeholder updates.

Do I need specific frontmatter formatting for markdown product documents?▼

Yes, specific frontmatter formatting is required for markdown product documents, specifically enforcing frontmatter name and description fields. This standardization supports invocation patterns and ensures consistent metadata across all generated documentation sections.