executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
generate-status-reportGenerate a project status report by reading existing artifacts (charter, backlog, sprint plan, WBS), calculating metrics, identifying blockers, and summarizing progress with RAG indicators for schedule, scope, budget, and quality. Use at the end of a sprint or reporting period, when stakeholders request a health update, before steering committee or governan…
Independent GitHub snapshot · Automated classification · Original documentation governs
析項目文、算進度、錄成阻次期,以 RAG 標健。
掃項目目錄取 PM 文:
讀可讀者。非皆存→依可用數據適應報告。
得:至少一文成讀,關鍵標已提。
敗:無文存→報不可生。先用 draft-project-charter 或 manage-backlog 造章或積件。
由可用數據算標:
敏捷標(BACKLOG.md / SPRINT-PLAN.md):
經典標(WBS.md):
## Metrics
| Metric | Value | Previous | Trend |
|--------|-------|----------|-------|
| Velocity | [N] pts | [N] pts | ↑/↓/→ |
| Sprint Completion | [N]% | [N]% | ↑/↓/→ |
| Backlog Remaining | [N] pts | [N] pts | ↓ (good) |
| Schedule Variance | [+/-N days] | [+/-N days] | |
得:算 3-5 標,具前期比。
敗:無史數據(首報)→略 Previous 與 Trend 欄。數據缺→於報腳標空白並予行動項以建跟蹤。
列活躍阻險:
## Blockers & Risks
| ID | Type | Description | Severity | Owner | Status | Action Required |
|----|------|------------|----------|-------|--------|----------------|
| R-001 | Risk | [Description] | High | [Name] | Open | [Action] |
| B-001 | Blocker | [Description] | Critical | [Name] | Active | [Action by date] |
| I-001 | Issue | [Description] | Medium | [Name] | Investigating | [Action] |
對章之險登記交叉引。標先前未辨之新險。
得:諸活躍阻與首險皆錄,有主有行動。
敗:無阻→顯陳「無活躍阻」,勿留空。阻無主→升至項目經理分配。
書二節:
## Accomplishments (This Period)
- [Completed item/milestone with evidence]
- [Completed item/milestone with evidence]
- [Completed item/milestone with evidence]
## Planned (Next Period)
- [Planned item/milestone with target]
- [Planned item/milestone with target]
- [Planned item/milestone with target]
得:3-5 成就具證,3-5 次期計項。
敗:無成就→報因(阻、重劃、隊不在)。次期計不明→列「計劃會議訂於 [日期]」為首項。
評四維健度:
| Dimension | Green | Amber | Red |
|---|---|---|---|
| Schedule | On track or ahead | 1-2 weeks behind | >2 weeks behind or milestone missed |
| Scope | No uncontrolled changes | Minor scope adjustments | Scope creep affecting deliverables |
| Budget | Within 5% of plan | 5-15% over plan | >15% over plan or untracked |
| Quality | Tests pass, criteria met | Minor quality issues | Critical defects or acceptance failures |
書全報:
# Status Report: [Project Name]
## Report Date: [YYYY-MM-DD]
## Reporting Period: [Start] to [End]
## Document ID: SR-[PROJECT]-[YYYY-MM-DD]
### Overall Health
| Dimension | Status | Notes |
|-----------|--------|-------|
| Schedule | 🟢/🟡/🔴 | [One-line explanation] |
| Scope | 🟢/🟡/🔴 | [One-line explanation] |
| Budget | 🟢/🟡/🔴 | [One-line explanation] |
| Quality | 🟢/🟡/🔴 | [One-line explanation] |
### Executive Summary
[2-3 sentences: overall status, key achievement, biggest risk]
### Metrics
[From Step 2]
### Accomplishments
[From Step 4]
### Blockers & Risks
[From Step 3]
### Planned Next Period
[From Step 4]
### Decisions Needed
- [Decision 1 — needed by date, from whom]
---
*Report prepared by: [Name/Agent]*
存為 STATUS-REPORT-[YYYY-MM-DD].md。
得:全狀報已存,含 RAG 標、標、敘述。
敗:數據不足以定 RAG→用 ⚪(灰)示「數據不足」並列次報所需收集。
draft-project-chartermanage-backlogplan-sprintcreate-work-breakdown-structureconduct-retrospective