pm-agile

Preamble

echo "🚀 敏捷管理方案制定工具已启动"

Write-time boundaries

When only discussing, do not write files; during startup checks, do not create directories. When the user requests saving artifacts, first confirm the current product, the exact output path, and the overwrite/append choice for existing files; after confirmation,only immediately before the actual Writecreate the parent directory of that output file. For full installation, see skills/_shared/artifact-policy.md, and installing this skill alone also follows this paragraph.

Cross-Agent interaction rules

When the process requires interaction with the user:

If the current environment supports AskUserQuestion, use AskUserQuestion (best experience).
If the current environment does not support AskUserQuestion, you must ask the same question via a normal chat message.
Ask only one question at a time.
After asking, you must stop the current turn and wait for the user's answer (STOP and WAIT).
Do not generate documents or write to docs before the user answers.
Existing docs files cannot substitute for the user's answer in this turn.

Execution flow

Step 1: Understand the team's current state

Use AskUserQuestion:

📊 Team current-state assessment

Please select the team's size:

A) Small team (2-5 people) B) Medium team (6-15 people) C) Large team (16-30 people) D) Multi-team collaboration (more than 30 people)

Continue asking:

🔄 Agile maturity assessment

The team's familiarity with agile development:

A) First attempt (needs detailed guidance) B) Some foundation (familiar with basic concepts) C) Experienced (can optimize independently)

Step 2: Design the iteration cadence

Use AskUserQuestion:

⏱️ Iteration cycle planning

Recommended iteration cycle:

A) 1 week (fast iteration, suitable for the startup phase) B) 2 weeks (standard cadence, suitable for most teams) C) 3 weeks (complex projects, needs more development time) D) 4 weeks (large projects, high coordination cost)

Continue asking:

📅 Iteration meeting planning

Which iteration meetings are needed:

A) Standard meetings (planning meeting, daily standup, review meeting, retrospective meeting) B) Streamlined meetings (only planning meeting and review meeting) C) Custom meeting process

Step 3: Plan the task board

Use AskUserQuestion:

📋 Task board type

Choose a suitable board mode:

A) To do - In progress - Done (basic board) B) To do - Development - Testing - Done (standard board) C) To do - Analysis - Development - Testing - Acceptance - Done (detailed board) D) Custom board process

Step 4: Design the progress tracking mechanism

Use AskUserQuestion:

📈 Progress tracking frequency

How frequently progress tracking is needed:

A) Daily (daily standup + board updates) B) Weekly (weekly report + weekly meeting) C) Per iteration (statistics only at the end of the iteration) D) Real-time (automated tools + dashboard)

Step 5: Generate the agile management plan

Use the Write tool to generate docs/04-风控管理/敏捷管理方案.md。

Subagent parallel acceleration (new in v2.0.0)

Use Agent tools to execute independent subtasks in parallel, greatly shortening the total execution time.

Parallelizable Subtasks

After the user information collection in steps 1-4 is completed, the following two tasks can be executed in parallel:

Subtask	Description
Iteration Cadence Derivation	Based on team size and agile maturity, derive the optimal iteration cycle and meeting frequency
Kanban and Tracking Design	Based on team preferences, design the task board column configuration and progress tracking mechanism

Trigger Method

Before generating the document in step 5, use the Agent tool to activate parallel execution of subtasks.

V1 vs V2 Comparison

Dimension	V1.1.0 (Serial)	V2.0.0 (Subagent Parallel)	Savings
Iteration Cadence Derivation	The user answers 4 rounds of questions one by one	Agent analyzes in parallel, completed in one step	About 3 rounds of interaction
Kanban and Tracking Design	Design the kanban and tracking sequentially	Agent outputs two plans in parallel	About 2 rounds of interaction
Total Interaction Rounds	About 8-10 rounds	About 4-5 rounds	Reduced by 50%+
Estimated Time	8-12 minutes	4-6 minutes	Saves about 5 minutes

Output File

Agile Management Plan → docs/04-风控管理/敏捷管理方案.md

Output Document Template

# 敏捷管理方案

## 一、团队概况

- **团队规模**: [从步骤1提取]
- **敏捷成熟度**: [从步骤1提取]
- **迭代周期**: [从步骤2提取]
- **生成时间**: [当前时间]

---

## 二、迭代节奏设计

### 2.1 迭代周期

**周期长度**: X周

**选择理由**: [说明为什么选择这个周期]

### 2.2 迭代会议安排

| 会议类型 | 频率 | 时长 | 参与者 | 目的 |
|---------|------|------|--------|------|
| 迭代计划会 | 迭代首日 | 2小时 | 全员 | 明确迭代目标与任务 |
| 每日站会 | 每日 | 15分钟 | 开发团队 | 同步进度与问题 |
| 迭代评审会 | 迭代末日 | 1小时 | 全员+stakeholder | 展示成果 |
| 迭代复盘会 | 迭代末日 | 1小时 | 全员 | 总结改进 |

---

## 三、任务看板设计

### 3.1 看板列设置

**看板类型**: [从步骤3提取]

**列定义**:
- **待办（To Do）**: 已确认但未开始的任务
- **开发中（In Progress）**: 正在开发的任务
- **测试中（Testing）**: 开发完成，等待测试
- **已完成（Done）**: 测试通过，可发布

### 3.2 任务卡片规范

每个任务卡片必须包含：
- 任务ID（如: TASK-001）
- 任务标题
- 负责人
- 预计工时
- 实际工时
- 优先级（P0/P1/P2/P3）
- 标签（如: 前端、后端、设计）

### 3.3 WIP限制

建议设置在制品限制（WIP Limit）:
- 每人同时在开发的任务数 ≤ 2
- 测试队列任务数 ≤ 开发人数

---

## 四、进度跟踪机制

### 4.1 跟踪方式

**跟踪频率**: [从步骤4提取]

**跟踪指标**:
- 迭代燃尽图（Burndown Chart）
- 任务完成率
- 阻塞问题数
- 团队速率（Velocity）

### 4.2 进度报告

**日报模板**:
```markdown
## 今日进展
- 完成任务：[任务列表]
- 进行中任务：[任务列表]
- 遇到问题：[问题描述]

## 明日计划
- 计划完成任务：[任务列表]

Iteration Report Template:

## 迭代概况
- 迭代目标达成情况
- 完成任务数 / 计划任务数
- 团队速率（故事点）

## 质量指标
- Bug数量
- 测试覆盖率
- 上线成功率

## 改进措施
- [下个迭代的改进点]

V. Roles and Responsibilities

Role	Responsibilities	Key Deliverables
Product Owner (PO)	Requirement prioritization, acceptance confirmation	Product Backlog, acceptance criteria
Scrum Master	Process advancement, problem solving	Iteration plan, risk report
Development Team	Task development, technical implementation	Code, technical documentation
Testing Team	Quality assurance, Bug verification	Test cases, test reports

VI. Risk Management

6.1 Common Risks

Frequent requirement changes → Establish a change review mechanism
Accumulation of technical debt → Reserve 20% of each iteration for debt repayment
Team collaboration issues → Regular retrospectives, continuous improvement

6.2 Risk Response Plan

Establish a risk kanban for real-time tracking:

Risk level (red/yellow/green)
Scope of impact
Response measures
Owner

VII. Tool Recommendations

7.1 Task Management Tools

Jira: Powerful, suitable for large teams
Trello: Lightweight kanban, suitable for small teams
Feishu/DingTalk: Domestic teams, integrated collaboration features
Linear: Modern tool, excellent experience

7.2 Collaboration Tools

Document Collaboration: Notion, Feishu Docs, Yuque
Communication and Collaboration: Slack, Feishu, DingTalk
Code Collaboration: Git + GitLab/GitHub

VIII. Implementation Recommendations

8.1 Launch Phase

Week 1: Determine iteration cadence, set up the kanban board
Week 2: First iteration, get familiar with the process
Week 3: First retrospective, adjust and optimize
Week 4: Stable operation, solidify the process

8.2 Continuous Improvement

At least 1 improvement measure per iteration
Quarterly process review, major adjustments
Stay flexible, avoid dogmatism

IX. Next-Step Recommendations

Recommended actions:

/pm-cross (develop a cross-department collaboration plan)
/pm-risk (identify project risks)
/pm-release (plan the launch approach)

Output Quality Comparison

✅ Good Example：

- 有数据引用：「根据 Q4 数据，留存率从 35% 降至 28%」
- 有验证来源：「数据来源：Google Analytics, 2025-12-01」
- 有明确建议：「建议将新手引导步骤从 5 步减少至 3 步」

❌ Bad Example：

- 模糊结论：「数据表明留存率有所下降」
- 无来源：「根据经验，这个功能很重要」
- 没有行动建议：「留存是个问题」

Common Pitfalls / Red Flags — STOP

Stop immediately and backtrack if any of the following occur:

Pitfall	Correct Approach
Drawing conclusions using "should", "probably", "seems"	Must be based on actual data and verification
Claiming completion without running checks	Verify first, then state
Skipping key steps due to time pressure	No exceptions; the tighter the time, the stricter you must be
The thought "this time it should be fine"	Re-verify every time

Output Quality Check / Verification Checklist

Prerequisite dependencies are met (input documents/data have been collected)
All core steps have been executed
Output document has been generated to docs/ directory
Every judgment is supported by data/evidence
2-3 follow-up skills have been recommended

⚠️ If any item fails → complete it before marking as done.

Project Status: Agile management plan has been developed Generation Time: [timestamp] Generation Tool: super-pm


---

## 推荐下一步

执行完成后，输出：

✅ 敏捷管理方案已生成！

🎯 建议下一步：
1. /pm-cross（制定跨部门协作方案）
2. /pm-risk（识别项目风险）
3. /pm-release（规划上线方案）

About this skill

Preamble

Write-time boundaries

Cross-Agent interaction rules

Execution flow

Step 1: Understand the team's current state

Step 2: Design the iteration cadence

Step 3: Plan the task board

Step 4: Design the progress tracking mechanism

Step 5: Generate the agile management plan

Subagent parallel acceleration (new in v2.0.0)

Parallelizable Subtasks

Trigger Method

V1 vs V2 Comparison

Output File

Output Document Template

V. Roles and Responsibilities

VI. Risk Management

6.1 Common Risks

6.2 Risk Response Plan

VII. Tool Recommendations

7.1 Task Management Tools

7.2 Collaboration Tools

VIII. Implementation Recommendations

8.1 Launch Phase

8.2 Continuous Improvement

IX. Next-Step Recommendations

Output Quality Comparison

Common Pitfalls / Red Flags — STOP

Output Quality Check / Verification Checklist