project-management by miles990/claude-software-skills
npx skills add https://github.com/miles990/claude-software-skills --skill project-management软件项目管理方法论、问题跟踪系统和团队协作实践。
┌─────────────────────────────────────────────────────────────────┐
│ Scrum Framework │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Product Sprint Sprint Sprint │
│ Backlog → Planning → Execution → Review/Retro │
│ │ │ │
│ ▼ ▼ │
│ Sprint Daily Standup │
│ Backlog (15 min) │
│ │
│ Roles: │
│ • Product Owner: Backlog priority, stakeholder voice │
│ • Scrum Master: Process facilitation, impediment removal │
│ • Development Team: Self-organizing, cross-functional │
│ │
│ Artifacts: │
│ • Product Backlog: Prioritized feature list │
│ • Sprint Backlog: Committed sprint work │
│ • Increment: Potentially shippable product │
│ │
│ Events: │
│ • Sprint Planning: What & How for sprint │
│ • Daily Standup: Sync & impediments │
│ • Sprint Review: Demo to stakeholders │
│ • Sprint Retrospective: Process improvement │
└─────────────────────────────────────────────────────────────────┘
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
┌──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│ Backlog │ To Do │ In Progress │ Review │ Done │
│ │ (WIP: 5) │ (WIP: 3) │ (WIP: 2) │ │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │
│ │ Feature │ │ │ Bug fix │ │ │ API │ │ │ Login │ │ │ Auth │ │
│ │ Request │ │ │ #123 │ │ │ endpoint │ │ │ page │ │ │ module │ │
│ └──────────┘ │ └──────────┘ │ │ @alice │ │ │ @bob │ │ └──────────┘ │
│ ┌──────────┐ │ ┌──────────┐ │ └──────────┘ │ └──────────┘ │ ┌──────────┐ │
│ │ Tech │ │ │ Refactor │ │ ┌──────────┐ │ │ │ Database │ │
│ │ Debt │ │ │ auth │ │ │ Tests │ │ │ │ migration│ │
│ └──────────┘ │ └──────────┘ │ │ @charlie │ │ │ └──────────┘ │
│ │ │ └──────────┘ │ │ │
└──────────────┴──────────────┴──────────────┴──────────────┴──────────────┘
关键原则:
• 可视化工作
• 限制在制品数量
• 管理流程
• 明确策略
• 实施反馈循环
• 协作改进
# 用户故事格式
作为一个 [用户类型]
我想要 [目标/期望]
以便 [收益/价值]
# 示例
作为一个注册用户
我想要通过电子邮件重置我的密码
以便在我忘记密码时可以重新获得账户访问权限
# 验收标准(Given-When-Then 格式)
前提 我在登录页面
当 我点击“忘记密码”
并且 我输入我注册的邮箱
并且 我点击“发送重置链接”
那么 我应该收到一封包含密码重置链接的电子邮件
并且 该链接应在 24 小时后过期
# INVEST 标准
□ 独立的 - 可以独立开发
□ 可协商的 - 细节可以讨论
□ 有价值的 - 提供用户/业务价值
□ 可估算的 - 可以估算规模
□ 小的 - 能在一个冲刺内完成
□ 可测试的 - 有明确的验收标准
# 斐波那契数列
1 - 微不足道 (< 1 小时)
2 - 简单 (几小时)
3 - 直接明了 (半天)
5 - 中等复杂度 (1-2 天)
8 - 复杂 (3-5 天)
13 - 非常复杂 (1周以上)
21 - 史诗级 (需要拆分!)
# 计划扑克
1. 产品负责人介绍故事
2. 团队讨论并提出问题
3. 每个成员秘密选择估算值
4. 所有人同时展示估算值
5. 讨论差异较大的估算
6. 如果需要,重新投票
7. 达成共识
# 速率计算
冲刺 1: 完成 32 点
冲刺 2: 完成 28 点
冲刺 3: 完成 35 点
平均速率: 31.7 点/冲刺
# 问题模板:错误报告
---
name: Bug Report
about: Report a bug to help us improve
labels: bug, needs-triage
---
## 描述
对错误的清晰描述。
## 重现步骤
1. 前往 '...'
2. 点击 '...'
3. 向下滚动到 '...'
4. 看到错误
## 预期行为
应该发生什么。
## 实际行为
实际发生了什么。
## 环境
- 操作系统: [例如,macOS 14.0]
- 浏览器: [例如,Chrome 120]
- 版本: [例如,2.1.0]
## 截图
如果适用,添加截图。
## 额外上下文
任何其他相关信息。
# 问题模板:功能请求
---
name: Feature Request
about: Suggest a new feature
labels: enhancement
---
## 问题陈述
这解决了什么问题?
## 建议的解决方案
这应该如何工作?
## 考虑过的替代方案
你考虑过的其他方法。
## 额外上下文
原型图、示例或参考资料。
# 项目配置
fields:
- name: Status
type: single_select
options:
- Backlog
- Ready
- In Progress
- In Review
- Done
- name: Priority
type: single_select
options:
- 🔴 High
- 🟡 Medium
- 🟢 Low
- name: Sprint
type: iteration
duration: 2 weeks
- name: Estimate
type: number
- name: Team
type: single_select
options:
- Frontend
- Backend
- DevOps
views:
- name: Kanban Board
type: board
group_by: Status
- name: Sprint Backlog
type: table
filter: Sprint = @current
sort: Priority
- name: Roadmap
type: roadmap
date_field: Target Date
# Linear 项目结构
teams:
- name: Engineering
key: ENG
workflows:
- Backlog → Todo → In Progress → In Review → Done
cycles:
- duration: 2 weeks
- auto_archive: true
labels:
- bug
- feature
- improvement
- tech-debt
priorities:
- Urgent
- High
- Medium
- Low
- No Priority
# Linear CLI 使用
linear issue create --title "Add OAuth support" --team ENG --priority high
linear issue list --team ENG --state "In Progress"
linear cycle current
## 冲刺计划会议议程 (2-4 小时)
### 第一部分:做什么 (1-2 小时)
1. 回顾冲刺目标
2. 产品负责人展示优先级排序的待办事项列表
3. 团队提出澄清性问题
4. 选择故事作为冲刺承诺
### 第二部分:怎么做 (1-2 小时)
1. 将故事分解为任务
2. 识别依赖关系
3. 分配初始负责人
4. 验证容量与承诺的匹配度
## 冲刺目标模板
"在本冲刺结束时,用户将能够 [具体能力],
从而实现 [业务价值]。"
## 容量规划
团队规模: 5 名开发人员
冲刺长度: 2 周 (10 个工作日)
会议/仪式: 相当于 1 天
休假/节假日: 2 天
缓冲 (错误、支持): 10%
可用容量: (5 × 10 - 5 - 2) × 0.9 = 38.7 人天
历史速率: ~35 故事点
## 完成的定义
### 代码完成
- [ ] 根据验收标准实现功能
- [ ] 编写单元测试 (>80% 覆盖率)
- [ ] 集成测试通过
- [ ] 无代码检查错误或警告
- [ ] 代码已自审
### 评审完成
- [ ] 代码评审获得 2 名以上团队成员批准
- [ ] 无未解决的阻塞性评论
- [ ] 已审查安全注意事项
### 测试完成
- [ ] QA 测试通过
- [ ] 边缘情况已测试
- [ ] 性能可接受
- [ ] 跨浏览器测试 (如果适用)
### 文档完成
- [ ] 代码已注释 (JSDoc/注释)
- [ ] API 文档已更新
- [ ] README 已更新 (如果需要)
- [ ] 已添加变更日志条目
### 准备部署
- [ ] 功能标志已配置 (如果需要)
- [ ] 数据库迁移已测试
- [ ] 监控/警报已配置
- [ ] 已合并到主分支
## 愤怒/悲伤/高兴
┌─────────────────┬─────────────────┬─────────────────┐
│ 愤怒 😠 │ 悲伤 😢 │ 高兴 😊 │
├─────────────────┼─────────────────┼─────────────────┤
│ 持续的范围变更 │ 错过了冲刺目标 │ 优秀的团队协作 │
│ │ │ │
│ 不清晰的需求 │ 技术债务在增长 │ 发布了主要功能 │
└─────────────────┴─────────────────┴─────────────────┘
## 开始/停止/继续
┌─────────────────┬─────────────────┬─────────────────┐
│ 开始 🟢 │ 停止 🔴 │ 继续 🔵 │
├─────────────────┼─────────────────┼─────────────────┤
│ 结对编程 │ 冗长的会议 │ 每日站会 │
│ │ │ │
│ 冲刺演示 │ 范围蔓延 │ 代码评审 │
│ │ │ │
│ 文档化 │ 最后一刻的变更 │ 知识共享 │
└─────────────────┴─────────────────┴─────────────────┘
## 4 Ls: 喜欢、学到、缺乏、渴望
## 帆船: 风 (助力)、锚 (阻碍)、礁石 (风险)
## 冲刺 23 回顾会议行动项
| 行动 | 负责人 | 截止日期 | 状态 |
|--------|-------|-----|--------|
| 设置自动化端到端测试 | @alice | 冲刺 24 | 🟡 进行中 |
| 编写 API 端点文档 | @bob | 冲刺 24 | ⬜ 未开始 |
| 安排架构评审 | @carol | 下周 | ✅ 已完成 |
## 要跟踪的指标
- 冲刺燃尽图一致性
- 缺陷逃逸率
- 部署频率
- 变更前置时间
## DORA 指标
1. 部署频率: 代码部署到生产环境的频率
2. 变更前置时间: 从提交到生产环境的时间
3. 变更失败率: 导致故障的部署百分比
4. 恢复时间: 从故障中恢复所需时间
## 冲刺指标
- 速率: 每个冲刺完成的故事点
- 冲刺燃尽图: 随时间推移剩余的工作量
- 逃逸缺陷: 发布后发现的错误
- 计划与交付对比: 承诺准确性
## 团队健康度
- 团队满意度调查
- 人员流动率
- 知识分享会议
- 技术债务比率
每周安装数
73
代码仓库
GitHub 星标数
7
首次出现
2026年1月24日
安全审计
安装于
gemini-cli69
codex68
opencode67
github-copilot65
amp63
kimi-cli63
Software project management methodologies, issue tracking systems, and team collaboration practices.
┌─────────────────────────────────────────────────────────────────┐
│ Scrum Framework │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Product Sprint Sprint Sprint │
│ Backlog → Planning → Execution → Review/Retro │
│ │ │ │
│ ▼ ▼ │
│ Sprint Daily Standup │
│ Backlog (15 min) │
│ │
│ Roles: │
│ • Product Owner: Backlog priority, stakeholder voice │
│ • Scrum Master: Process facilitation, impediment removal │
│ • Development Team: Self-organizing, cross-functional │
│ │
│ Artifacts: │
│ • Product Backlog: Prioritized feature list │
│ • Sprint Backlog: Committed sprint work │
│ • Increment: Potentially shippable product │
│ │
│ Events: │
│ • Sprint Planning: What & How for sprint │
│ • Daily Standup: Sync & impediments │
│ • Sprint Review: Demo to stakeholders │
│ • Sprint Retrospective: Process improvement │
└─────────────────────────────────────────────────────────────────┘
┌──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│ Backlog │ To Do │ In Progress │ Review │ Done │
│ │ (WIP: 5) │ (WIP: 3) │ (WIP: 2) │ │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │
│ │ Feature │ │ │ Bug fix │ │ │ API │ │ │ Login │ │ │ Auth │ │
│ │ Request │ │ │ #123 │ │ │ endpoint │ │ │ page │ │ │ module │ │
│ └──────────┘ │ └──────────┘ │ │ @alice │ │ │ @bob │ │ └──────────┘ │
│ ┌──────────┐ │ ┌──────────┐ │ └──────────┘ │ └──────────┘ │ ┌──────────┐ │
│ │ Tech │ │ │ Refactor │ │ ┌──────────┐ │ │ │ Database │ │
│ │ Debt │ │ │ auth │ │ │ Tests │ │ │ │ migration│ │
│ └──────────┘ │ └──────────┘ │ │ @charlie │ │ │ └──────────┘ │
│ │ │ └──────────┘ │ │ │
└──────────────┴──────────────┴──────────────┴──────────────┴──────────────┘
Key Principles:
• Visualize work
• Limit Work In Progress (WIP)
• Manage flow
• Make policies explicit
• Implement feedback loops
• Improve collaboratively
# User Story Format
As a [type of user]
I want [goal/desire]
So that [benefit/value]
# Example
As a registered user
I want to reset my password via email
So that I can regain access to my account if I forget my password
# Acceptance Criteria (Given-When-Then)
Given I am on the login page
When I click "Forgot Password"
And I enter my registered email
And I click "Send Reset Link"
Then I should receive an email with a password reset link
And the link should expire after 24 hours
# INVEST Criteria
□ Independent - Can be developed separately
□ Negotiable - Details can be discussed
□ Valuable - Delivers user/business value
□ Estimable - Can be sized
□ Small - Fits in a sprint
□ Testable - Has clear acceptance criteria
# Fibonacci Scale
1 - Trivial (< 1 hour)
2 - Simple (few hours)
3 - Straightforward (half day)
5 - Medium complexity (1-2 days)
8 - Complex (3-5 days)
13 - Very complex (1+ week)
21 - Epic (break it down!)
# Planning Poker
1. Product Owner presents story
2. Team discusses & asks questions
3. Each member secretly selects estimate
4. All reveal simultaneously
5. Discuss outliers
6. Re-vote if needed
7. Reach consensus
# Velocity Calculation
Sprint 1: 32 points completed
Sprint 2: 28 points completed
Sprint 3: 35 points completed
Average Velocity: 31.7 points/sprint
# Issue Template: Bug Report
---
name: Bug Report
about: Report a bug to help us improve
labels: bug, needs-triage
---
## Description
A clear description of the bug.
## Steps to Reproduce
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error
## Expected Behavior
What should happen.
## Actual Behavior
What actually happens.
## Environment
- OS: [e.g., macOS 14.0]
- Browser: [e.g., Chrome 120]
- Version: [e.g., 2.1.0]
## Screenshots
If applicable, add screenshots.
## Additional Context
Any other relevant information.
# Issue Template: Feature Request
---
name: Feature Request
about: Suggest a new feature
labels: enhancement
---
## Problem Statement
What problem does this solve?
## Proposed Solution
How should this work?
## Alternatives Considered
Other approaches you've thought about.
## Additional Context
Mockups, examples, or references.
# Project configuration
fields:
- name: Status
type: single_select
options:
- Backlog
- Ready
- In Progress
- In Review
- Done
- name: Priority
type: single_select
options:
- 🔴 High
- 🟡 Medium
- 🟢 Low
- name: Sprint
type: iteration
duration: 2 weeks
- name: Estimate
type: number
- name: Team
type: single_select
options:
- Frontend
- Backend
- DevOps
views:
- name: Kanban Board
type: board
group_by: Status
- name: Sprint Backlog
type: table
filter: Sprint = @current
sort: Priority
- name: Roadmap
type: roadmap
date_field: Target Date
# Linear project structure
teams:
- name: Engineering
key: ENG
workflows:
- Backlog → Todo → In Progress → In Review → Done
cycles:
- duration: 2 weeks
- auto_archive: true
labels:
- bug
- feature
- improvement
- tech-debt
priorities:
- Urgent
- High
- Medium
- Low
- No Priority
# Linear CLI usage
linear issue create --title "Add OAuth support" --team ENG --priority high
linear issue list --team ENG --state "In Progress"
linear cycle current
## Sprint Planning Agenda (2-4 hours)
### Part 1: What (1-2 hours)
1. Review sprint goal
2. Product Owner presents prioritized backlog
3. Team asks clarifying questions
4. Select stories for sprint commitment
### Part 2: How (1-2 hours)
1. Break stories into tasks
2. Identify dependencies
3. Assign initial owners
4. Validate capacity vs commitment
## Sprint Goal Template
"By the end of this sprint, users will be able to [specific capability],
enabling [business value]."
## Capacity Planning
Team Size: 5 developers
Sprint Length: 2 weeks (10 working days)
Meetings/Ceremonies: 1 day equivalent
PTO/Holidays: 2 days
Buffer (bugs, support): 10%
Available Capacity: (5 × 10 - 5 - 2) × 0.9 = 38.7 person-days
Historical Velocity: ~35 story points
## Definition of Done (DoD)
### Code Complete
- [ ] Feature implemented per acceptance criteria
- [ ] Unit tests written (>80% coverage)
- [ ] Integration tests passing
- [ ] No linting errors or warnings
- [ ] Self-reviewed code
### Review Complete
- [ ] Code review approved by 2+ team members
- [ ] No blocking comments unresolved
- [ ] Security considerations reviewed
### Testing Complete
- [ ] QA testing passed
- [ ] Edge cases tested
- [ ] Performance acceptable
- [ ] Cross-browser testing (if applicable)
### Documentation Complete
- [ ] Code documented (JSDoc/comments)
- [ ] API documentation updated
- [ ] README updated if needed
- [ ] Changelog entry added
### Deployment Ready
- [ ] Feature flag configured (if needed)
- [ ] Database migrations tested
- [ ] Monitoring/alerts configured
- [ ] Merged to main branch
## Mad/Sad/Glad
┌─────────────────┬─────────────────┬─────────────────┐
│ Mad 😠 │ Sad 😢 │ Glad 😊 │
├─────────────────┼─────────────────┼─────────────────┤
│ Constant scope │ Missed sprint │ Great team │
│ changes │ goal │ collaboration │
│ │ │ │
│ Unclear │ Technical debt │ Shipped major │
│ requirements │ growing │ feature │
└─────────────────┴─────────────────┴─────────────────┘
## Start/Stop/Continue
┌─────────────────┬─────────────────┬─────────────────┐
│ Start 🟢 │ Stop 🔴 │ Continue 🔵 │
├─────────────────┼─────────────────┼─────────────────┤
│ Pair programming│ Long meetings │ Daily standups │
│ │ │ │
│ Sprint demos │ Scope creep │ Code reviews │
│ │ │ │
│ Documentation │ Last-minute │ Knowledge │
│ │ changes │ sharing │
└─────────────────┴─────────────────┴─────────────────┘
## 4 Ls: Liked, Learned, Lacked, Longed For
## Sailboat: Wind (helps), Anchors (slows), Rocks (risks)
## Sprint 23 Retrospective Action Items
| Action | Owner | Due | Status |
|--------|-------|-----|--------|
| Set up automated E2E tests | @alice | Sprint 24 | 🟡 In Progress |
| Document API endpoints | @bob | Sprint 24 | ⬜ Not Started |
| Schedule architecture review | @carol | Next week | ✅ Done |
## Metrics to Track
- Sprint burndown consistency
- Bug escape rate
- Deployment frequency
- Lead time for changes
## DORA Metrics
1. Deployment Frequency: How often code deploys to production
2. Lead Time for Changes: Commit to production time
3. Change Failure Rate: % of deployments causing failures
4. Time to Restore: How long to recover from failures
## Sprint Metrics
- Velocity: Story points completed per sprint
- Sprint Burndown: Work remaining over time
- Escaped Defects: Bugs found after release
- Planned vs Delivered: Commitment accuracy
## Team Health
- Team satisfaction surveys
- Turnover rate
- Knowledge sharing sessions
- Technical debt ratio
Weekly Installs
73
Repository
GitHub Stars
7
First Seen
Jan 24, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
gemini-cli69
codex68
opencode67
github-copilot65
amp63
kimi-cli63
BMAD工作流编排与SSD结构化系统设计 - 多代理AI开发流程自动化
10,600 周安装
Python日志记录最佳实践:Loguru配置、JSONL结构化日志与跨平台日志轮转指南
207 周安装
Vue 2 开发指南 - Options API、组件、Vuex、Vue Router 完整教程
207 周安装
Android数据层与离线优先架构:仓库模式、Room持久化、Retrofit网络请求详解
208 周安装
Umbraco Kinds 扩展配置:简化 CMS 扩展开发,实现标准化与代码复用
72 周安装
依赖图审计器 - 自动化代码架构分析与边界规则验证工具
208 周安装
浏览器调试指南:使用Chrome DevTools解决JavaScript错误、布局和性能问题
210 周安装