pm-skills
Project management workflows — planning, tracking, and coordination for software and product teams. Use when the user wants to create a project plan, write a PRD, create tickets, define sprint goals, write a RACI matrix, run a retrospective, or manage project scope. Trigger phrases include "project plan", "project management", "sprint planning", "PRD", "product requirements", "roadmap", "milestone", "retro", "standup", "RACI", "risk register", "project timeline".
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pm-skills
- description
- Project management workflows — planning, tracking, and coordination for software and product teams. Use when the user wants to create a project plan, write a PRD, create tickets, define sprint goals, write a RACI matrix, run a retrospective, or manage project scope. Trigger phrases include "project plan", "project management", "sprint planning", "PRD", "product requirements", "roadmap", "milestone", "retro", "standup", "RACI", "risk register", "project timeline".
03 SKILL.md 正文
PM Skills
Project management workflows for software and product teams.
Document Templates
Product Requirements Document (PRD)
# PRD: [Feature Name]
## Overview
One-paragraph summary of what we're building and why.
## Problem Statement
What user problem or business need does this solve?
Why does it matter now?
## Goals & Success Metrics
| Goal | Metric | Target |
|------|--------|--------|
| ... | ... | ... |
## Non-Goals
What is explicitly out of scope for this version.
## User Stories
- As a [user type], I want to [action] so that [outcome].
## Functional Requirements
1. The system must...
2. Users can...
## Non-Functional Requirements
- Performance: ...
- Security: ...
- Accessibility: ...
## Technical Considerations
Known constraints, dependencies, or architectural notes.
## Open Questions
- [ ] Decision needed by [date]: ...
## Timeline
| Milestone | Date |
|-----------|------|
| Design complete | ... |
| Engineering complete | ... |
| QA complete | ... |
| Launch | ... |
Sprint Planning Template
## Sprint [N] — [Dates]
**Goal**: [One sentence describing the sprint's primary objective]
### Committed Work
| Ticket | Title | Points | Owner |
|--------|-------|--------|-------|
| ... | ... | ... | ... |
**Total Points**: X
### Definition of Done
- [ ] Code reviewed and merged
- [ ] Tests written and passing
- [ ] Deployed to staging
- [ ] QA sign-off
RACI Matrix
## RACI: [Project Name]
| Task | PM | Eng Lead | Designer | Stakeholder |
|------|----|----------|----------|-------------|
| Requirements | R/A | C | C | I |
| Design | I | C | R/A | I |
| Implementation | I | R/A | I | I |
| QA | A | R | I | I |
| Launch | A | R | R | I |
R = Responsible, A = Accountable, C = Consulted, I = Informed
Risk Register
## Risk Register
| Risk | Likelihood | Impact | Mitigation | Owner |
|------|------------|--------|------------|-------|
| API dependency delayed | Medium | High | Stub API early | Eng Lead |
| Scope creep | High | Medium | Weekly scope review | PM |
Sprint Ceremonies
Daily Standup (async or sync)
Format:
- Yesterday: What did I complete?
- Today: What will I work on?
- Blockers: What is blocking me?
Retrospective
Start / Stop / Continue:
- Start doing: [what should we add?]
- Stop doing: [what isn't working?]
- Continue doing: [what's working well?]
4Ls:
- Liked: What went well?
- Learned: What did we learn?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Estimation
Story points (Fibonacci): 1, 2, 3, 5, 8, 13, 21
| Points | Description |
|---|---|
| 1 | Trivial, < 1 hour |
| 2 | Small, half-day |
| 3 | Clear, ~1 day |
| 5 | Medium complexity, 2–3 days |
| 8 | Large, needs breakdown |
| 13+ | Too big — split it |
Project Status Report
## [Project] — Status Update [Date]
**Status**: 🟢 On Track / 🟡 At Risk / 🔴 Off Track
**Summary**: [2–3 sentences on progress]
**Completed this week**: ...
**Planned next week**: ...
**Risks / Blockers**: ...
**Decisions needed**: ...
04 同仓库更多 Skills
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use when the user asks to build a complex web artifact, scaffold a React artifact project, bundle a single-file artifact, or generate shadcn/ui-based interactive UI components.
theme-factory
Generate production-ready UI themes and token systems for CSS, Tailwind, and shadcn/ui. Use when users ask to apply a theme, theme an existing app, change colors and fonts, map dark/light mode tokens, or turn a palette into semantic variables. Trigger phrases include "apply a theme", "theme this app", "change the colors", and "re-theme this UI". Do not use for brand identity extraction, logo work, or full UI redesigns; use brand-guidelines or frontend-design instead.
frontend-design
Design and implement distinctive, production-grade frontend interfaces for web pages, components, and apps. Use when users ask for UI design, layout polish, landing pages, dashboards, React components, HTML/CSS styling, or visual redesign. Trigger phrases include "design this UI", "build a landing page", "make this look better", "frontend component", "dashboard UI", and "polish the interface".
excalidraw
Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, or generate excalidraw files.
brand-guidelines
Extract, normalize, and apply a brand system across UI, docs, and assets. Use when users ask for a brand kit, style guide, design tokens, tone rules, or brand-consistent output. Trigger phrases include "brand guidelines", "brand identity", "brand kit", "style guide", "brand colors", "brand fonts", "design tokens", and "make this on-brand".
doc-coauthoring
Collaborative document editing workflows for merging changes, resolving comments, managing versions, and coordinating review cycles. Use when the user asks to coauthor, merge edits, handle tracked changes, resolve review comments, or run a multi-author doc review process. Trigger phrases include "coauthor", "document collaboration", "merge edits", "track changes", "document review", and "resolve comments".