milestone-review

Name: milestone-review
Author: tranhieutt

69stars41forks

How to install milestone-review?

tranhieutt/software_development_department/milestone-review

$npx -y skills add tranhieutt/software_development_department --skill milestone-review

Installs into the current project.

Summary

Conducts a structured milestone review analyzing delivered features, metrics, blockers, and readiness for the next phase. Use when completing a milestone or when the user mentions milestone review or phase gate.

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Read the milestone definition from `production/milestones/`.
4
5	2. Read all sprint reports for sprints within this milestone from
6	`production/sprints/`.
7
8	3. Scan the codebase for TODO, FIXME, HACK markers that indicate
9	incomplete work.
10
11	4. Check the risk register at `production/risk-register/`.
12
13	5. Generate the milestone review:
14
15	```markdown
16	# Milestone Review: [Milestone Name]
17
18	## Overview
19	- Target Date: [Date]
20	- Current Date: [Today]
21	- Days Remaining: [N]
22	- Sprints Completed: [X/Y]
23
24	## Feature Completeness
25
26	### Fully Complete
27	\| Feature \| Acceptance Criteria \| Test Status \|
28	\|---------\|-------------------\|-------------\|
29
30	### Partially Complete
31	\| Feature \| % Done \| Remaining Work \| Risk to Milestone \|
32	\|---------\|--------\|---------------\|------------------\|
33
34	### Not Started
35	\| Feature \| Priority \| Can Cut? \| Impact of Cutting \|
36	\|---------\|----------\|----------\|------------------\|
37
38	## Quality Metrics
39	- Open S1 Bugs: [N] -- [List]
40	- Open S2 Bugs: [N]
41	- Open S3 Bugs: [N]
42	- Test Coverage: [X%]
43	- Performance: [Within budget? Details]
44
45	## Code Health
46	- TODO count: [N across codebase]
47	- FIXME count: [N]
48	- HACK count: [N]
49	- Technical debt items: [List critical ones]
50
51	## Risk Assessment
52	\| Risk \| Status \| Impact if Realized \| Mitigation Status \|
53	\|------\|--------\|-------------------\|------------------\|
54
55	## Velocity Analysis
56	- Planned vs Completed (across all sprints): [X/Y tasks = Z%]
57	- Trend: [Improving / Stable / Declining]
58	- Adjusted estimate for remaining work: [Days needed at current velocity]
59
60	## Scope Recommendations
61	### Protect (Must ship with milestone)
62	- [Feature and why]
63
64	### At Risk (May need to cut or simplify)
65	- [Feature and risk]
66
67	### Cut Candidates (Can defer without compromising milestone)
68	- [Feature and impact of cutting]
69
70	## Go/No-Go Assessment
71
72	Recommendation: [GO / CONDITIONAL GO / NO-GO]
73
74	Conditions (if conditional):
75	- [Condition 1 that must be met]
76	- [Condition 2 that must be met]
77
78	Rationale: [Explanation of the recommendation]
79
80	## Action Items
81	\| # \| Action \| Owner \| Deadline \|
82	\|---\|--------\|-------\|----------\|
83	```
84
85	## Protocol
86
87	- Question: Reads milestone name or `current` from argument
88	- Options: Skip
89	- Decision: Skip — Go/No-Go is a recommendation, not a gate
90	- Draft: Full review shown in conversation before saving
91	- Approval: "May I write to `production/milestones/[milestone]-review.md`?"
92
93	## Output
94
95	Deliver exactly:
96
97	- Feature completeness score (X/Y features done)
98	- Quality metrics: test pass rate, known bug count by severity
99	- Top 3 risks with probability and impact
100	- Recommendation: `GO` / `CONDITIONAL GO` / `NO-GO` with rationale
101	- Action items table — numbered, with owner and deadline

People who liked this also viewed

6 picks

Type

milestone-review

69stars41forks

View on GitHub

How to install milestone-review?

tranhieutt/software_development_department/milestone-review

$npx -y skills add tranhieutt/software_development_department --skill milestone-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Read the milestone definition from `production/milestones/`.
4
5	2. Read all sprint reports for sprints within this milestone from
6	`production/sprints/`.
7
8	3. Scan the codebase for TODO, FIXME, HACK markers that indicate
9	incomplete work.
10
11	4. Check the risk register at `production/risk-register/`.
12
13	5. Generate the milestone review:
14
15	```markdown
16	# Milestone Review: [Milestone Name]
17
18	## Overview
19	- Target Date: [Date]
20	- Current Date: [Today]
21	- Days Remaining: [N]
22	- Sprints Completed: [X/Y]
23
24	## Feature Completeness
25
26	### Fully Complete
27	\| Feature \| Acceptance Criteria \| Test Status \|
28	\|---------\|-------------------\|-------------\|
29
30	### Partially Complete
31	\| Feature \| % Done \| Remaining Work \| Risk to Milestone \|
32	\|---------\|--------\|---------------\|------------------\|
33
34	### Not Started
35	\| Feature \| Priority \| Can Cut? \| Impact of Cutting \|
36	\|---------\|----------\|----------\|------------------\|
37
38	## Quality Metrics
39	- Open S1 Bugs: [N] -- [List]
40	- Open S2 Bugs: [N]
41	- Open S3 Bugs: [N]
42	- Test Coverage: [X%]
43	- Performance: [Within budget? Details]
44
45	## Code Health
46	- TODO count: [N across codebase]
47	- FIXME count: [N]
48	- HACK count: [N]
49	- Technical debt items: [List critical ones]
50
51	## Risk Assessment
52	\| Risk \| Status \| Impact if Realized \| Mitigation Status \|
53	\|------\|--------\|-------------------\|------------------\|
54
55	## Velocity Analysis
56	- Planned vs Completed (across all sprints): [X/Y tasks = Z%]
57	- Trend: [Improving / Stable / Declining]
58	- Adjusted estimate for remaining work: [Days needed at current velocity]
59
60	## Scope Recommendations
61	### Protect (Must ship with milestone)
62	- [Feature and why]
63
64	### At Risk (May need to cut or simplify)
65	- [Feature and risk]
66
67	### Cut Candidates (Can defer without compromising milestone)
68	- [Feature and impact of cutting]
69
70	## Go/No-Go Assessment
71
72	Recommendation: [GO / CONDITIONAL GO / NO-GO]
73
74	Conditions (if conditional):
75	- [Condition 1 that must be met]
76	- [Condition 2 that must be met]
77
78	Rationale: [Explanation of the recommendation]
79
80	## Action Items
81	\| # \| Action \| Owner \| Deadline \|
82	\|---\|--------\|-------\|----------\|
83	```
84
85	## Protocol
86
87	- Question: Reads milestone name or `current` from argument
88	- Options: Skip
89	- Decision: Skip — Go/No-Go is a recommendation, not a gate
90	- Draft: Full review shown in conversation before saving
91	- Approval: "May I write to `production/milestones/[milestone]-review.md`?"
92
93	## Output
94
95	Deliver exactly:
96
97	- Feature completeness score (X/Y features done)
98	- Quality metrics: test pass rate, known bug count by severity
99	- Top 3 risks with probability and impact
100	- Recommendation: `GO` / `CONDITIONAL GO` / `NO-GO` with rationale
101	- Action items table — numbered, with owner and deadline

People who liked this also viewed

6 picks

Type