justin/pm-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: sync all skill updates and new skills into plugin bundles

Browse Source 
- Synced 97 existing skill SKILL.md files from skills/ to their plugin bundle copies
- Added 7 new skills to plugin bundles:
  - seo-content-brief, media-pitch -> pm-gtm
  - tax-planning-checklist -> pm-finance
  - change-management-plan -> pm-hr
  - sales-forecasting-model -> pm-sales
  - workshop-facilitation-guide -> pm-operations
  - teaching-lesson-plan -> pm-cross

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
mohitagw15856
2026-04-20 21:00:00 +01:00
parent d7f6c2cd05
commit 513e1d3ce7
67 changed files with 1851 additions and 507 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/pm-essentials/skills/prd-template/SKILL.md
+20 -1
View File
@@ -1,12 +1,22 @@
---
name: prd-template
description: Product Requirements Document creation following proven PM template structure. Use when the user asks to create, write, draft, or help with a PRD, product requirements document, product spec, feature specification, or product documentation for a new feature or product.
description: "Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics."
---
# PRD Template Skill
This skill helps create professional Product Requirements Documents following industry best practices.
## Required Inputs
Ask the user for these if not provided:
- **Feature or product name**
- **Problem being solved** (from the user's perspective)
- **Target user** (role, context, what they're trying to accomplish)
- **Success metrics** (how will you know it worked?)
- **Scope** (MVP vs full vision — what's in and out of scope)
- **Key stakeholders** (who needs to review and approve)
## Template Structure
Every PRD should include these sections in order:
@@ -91,6 +101,15 @@ Format: "As a [user type], I want to [action] so that [benefit]"
- Skip the "why"
- Forget about accessibility
## Quality Checks
- [ ] Problem statement is written from the user's perspective (not the company's)
- [ ] Success metrics are specific and measurable
- [ ] User stories include acceptance criteria
- [ ] Requirements are testable (not vague)
- [ ] Open questions are listed explicitly
- [ ] Implementation plan distinguishes MVP from future phases
## Example PRD Opening
```