Prompt file imported from PauloHYBEX/Nexus-TCMS (.windsurf/workflows/milestone-summary.md). Fill in {{VERSION}} before use. Copyright stays with the author.

Milestone Summary

Name: milestone-summary
Author: PauloHYBEX

Generate a comprehensive, human-friendly project summary from completed milestone artifacts. Designed for team onboarding — a new contributor can read the output and understand the entire project.

Usage: milestone-summary or milestone-summary [version]

Step 1: Resolve Version

If a version was provided, use it. Otherwise:

Check .planning/STATE.md for current milestone version
Check .planning/milestones/ for the latest archived version
If nothing found: "No milestone found. Run /new-project or /new-milestone first."

Step 2: Locate Artifacts

Archived milestone (.planning/milestones/v{VERSION}-ROADMAP.md exists):

ROADMAP_PATH=".planning/milestones/v{{VERSION}}-ROADMAP.md"
REQUIREMENTS_PATH=".planning/milestones/v{{VERSION}}-REQUIREMENTS.md"

Current/in-progress milestone (no archive yet):

ROADMAP_PATH=".planning/ROADMAP.md"
REQUIREMENTS_PATH=".planning/REQUIREMENTS.md"

Always available:

PROJECT_PATH=".planning/PROJECT.md"
STATE_PATH=".planning/STATE.md"

Read all files that exist. Missing files are fine — the summary adapts.

Step 3: Discover Phase Artifacts

For each phase directory in .planning/phases/:

ls .planning/phases/*/

For each phase, read:

CONTEXT.md — what was decided
SUMMARY.md files — what was built
VERIFICATION.md — quality status
UAT.md — test results
LEARNINGS.md — extracted learnings (if exists)
SECURITY.md — security status (if exists)

Step 4: Generate Summary

Write .planning/MILESTONE-SUMMARY-v{VERSION}.md:

# Milestone {VERSION}: {Name} — Summary

**Generated:** [date]
**Status:** [complete / in-progress]

---

## Project Overview

[From PROJECT.md — 3-5 sentences describing what the project is and why it exists]

## Milestone Goal

[From ROADMAP.md — what this milestone set out to deliver]

## What Was Built

### Phase 1: [Name]
**Goal:** [from ROADMAP.md]
**Status:** [complete/partial]
**Key deliverables:**
- [from SUMMARY.md files — what was actually built]

**Decisions made:**
- [from CONTEXT.md — key implementation choices]

### Phase 2: [Name]
[...]

## Architecture

[Synthesized from AGENTS.md project structure, phase summaries, and any ARCHITECTURE.md]

## Key Decisions

[Aggregated from DECISIONS.md and phase CONTEXT.md files — the top 5-10 decisions that shaped the project]

## Lessons Learned

[Aggregated from LEARNINGS.md files if they exist, or synthesized from SUMMARYs]

## Current State

- **Last phase completed:** [N]
- **Open items:** [from STATE.md blockers]
- **Test status:** [from UAT/VERIFICATION files]
- **Security status:** [from SECURITY files if they exist]

## How to Get Started

[Practical instructions: how to clone, install deps, run the dev server, run tests]

---

*Generated by learnship milestone-summary*

Step 5: Commit and Present

git add ".planning/MILESTONE-SUMMARY-v{{VERSION}}.md"
git commit -m "docs: milestone {{VERSION}} summary"

learnship > MILESTONE SUMMARY COMPLETE

Milestone {VERSION}: {Name}
Phases covered: [N]
Decisions documented: [N]
Lessons captured: [N]

Report: .planning/MILESTONE-SUMMARY-v{VERSION}.md

Share this with new team members or stakeholders for a complete project overview.

Learning Checkpoint

Read learning_mode from .planning/config.json.

If auto:

Learning moment: Summarizing a milestone is a natural point for comprehensive reflection:

@agentic-learning reflect — What was the most significant thing you learned across this entire milestone? What would you do differently if starting over? Milestone-level reflection reveals patterns invisible at the phase level.

If manual: Add quietly: "Tip: @agentic-learning reflect for milestone-level learning consolidation."

# Milestone Summary Generate a comprehensive, human-friendly project summary from completed milestone artifacts. Designed for team onboarding — a new contributor can read the output and understand the entire project. **Usage:** `milestone-summary` or `milestone-summary [version]` ## Step 1: Resolve Version If a version was provided, use it. Otherwise: 1. Check `.planning/STATE.md` for current milestone version 2. Check `.planning/milestones/` for the latest archived version 3. If nothing found: "No milestone found. Run `/new-project` or `/new-milestone` first." ## Step 2: Locate Artifacts **Archived milestone** (`.planning/milestones/v{VERSION}-ROADMAP.md` exists): ``` ROADMAP_PATH=".planning/milestones/v{{VERSION}}-ROADMAP.md" REQUIREMENTS_PATH=".planning/milestones/v{{VERSION}}-REQUIREMENTS.md" ``` **Current/in-progress milestone** (no archive yet): ``` ROADMAP_PATH=".planning/ROADMAP.md" REQUIREMENTS_PATH=".planning/REQUIREMENTS.md" ``` **Always available:** ``` PROJECT_PATH=".planning/PROJECT.md" STATE_PATH=".planning/STATE.md" ``` Read all files that exist. Missing files are fine — the summary adapts. ## Step 3: Discover Phase Artifacts For each phase directory in `.planning/phases/`: ```bash ls .planning/phases/*/ ``` For each phase, read: - CONTEXT.md — what was decided - SUMMARY.md files — what was built - VERIFICATION.md — quality status - UAT.md — test results - LEARNINGS.md — extracted learnings (if exists) - SECURITY.md — security status (if exists) ## Step 4: Generate Summary Write `.planning/MILESTONE-SUMMARY-v{VERSION}.md`: ```markdown # Milestone {VERSION}: {Name} — Summary **Generated:** [date] **Status:** [complete / in-progress] --- ## Project Overview [From PROJECT.md — 3-5 sentences describing what the project is and why it exists] ## Milestone Goal [From ROADMAP.md — what this milestone set out to deliver] ## What Was Built ### Phase 1: [Name] **Goal:** [from ROADMAP.md] **Status:** [complete/partial] **Key deliverables:** - [from SUMMARY.md files — what was actually built] **Decisions made:** - [from CONTEXT.md — key implementation choices] ### Phase 2: [Name] [...] ## Architecture [Synthesized from AGENTS.md project structure, phase summaries, and any ARCHITECTURE.md] ## Key Decisions [Aggregated from DECISIONS.md and phase CONTEXT.md files — the top 5-10 decisions that shaped the project] ## Lessons Learned [Aggregated from LEARNINGS.md files if they exist, or synthesized from SUMMARYs] ## Current State - **Last phase completed:** [N] - **Open items:** [from STATE.md blockers] - **Test status:** [from UAT/VERIFICATION files] - **Security status:** [from SECURITY files if they exist] ## How to Get Started [Practical instructions: how to clone, install deps, run the dev server, run tests] --- *Generated by learnship milestone-summary* ``` ## Step 5: Commit and Present ```bash git add ".planning/MILESTONE-SUMMARY-v{{VERSION}}.md" git commit -m "docs: milestone {{VERSION}} summary" ``` ``` learnship > MILESTONE SUMMARY COMPLETE Milestone {VERSION}: {Name} Phases covered: [N] Decisions documented: [N] Lessons captured: [N] Report: .planning/MILESTONE-SUMMARY-v{VERSION}.md Share this with new team members or stakeholders for a complete project overview. ``` --- ## Learning Checkpoint Read `learning_mode` from `.planning/config.json`. **If `auto`:** > **Learning moment:** Summarizing a milestone is a natural point for comprehensive reflection: > > `@agentic-learning reflect` — What was the most significant thing you learned across this entire milestone? What would you do differently if starting over? Milestone-level reflection reveals patterns invisible at the phase level. **If `manual`:** Add quietly: *"Tip: `@agentic-learning reflect` for milestone-level learning consolidation."*

{ "prompt": "# Milestone Summary\n\nGenerate a comprehensive, human-friendly project summary from completed milestone artifacts. Designed for team onboarding — a new contributor can read the output and understand the entire project.\n\n**Usage:** `milestone-summary` or `milestone-summary [version]`\n\n## Step 1: Resolve Version\n\nIf a version was provided, use it. Otherwise:\n1. Check `.planning/STATE.md` for current milestone version\n2. Check `.planning/milestones/` for the latest archived version\n3. If nothing found: \"No milestone found. Run `/new-project` or `/new-milestone` first.\"\n\n## Step 2: Locate Artifacts\n\n**Archived milestone** (`.planning/milestones/v{VERSION}-ROADMAP.md` exists):\n```\nROADMAP_PATH=\".planning/milestones/v{{VERSION}}-ROADMAP.md\"\nREQUIREMENTS_PATH=\".planning/milestones/v{{VERSION}}-REQUIREMENTS.md\"\n```\n\n**Current/in-progress milestone** (no archive yet):\n```\nROADMAP_PATH=\".planning/ROADMAP.md\"\nREQUIREMENTS_PATH=\".planning/REQUIREMENTS.md\"\n```\n\n**Always available:**\n```\nPROJECT_PATH=\".planning/PROJECT.md\"\nSTATE_PATH=\".planning/STATE.md\"\n```\n\nRead all files that exist. Missing files are fine — the summary adapts.\n\n## Step 3: Discover Phase Artifacts\n\nFor each phase directory in `.planning/phases/`:\n\n```bash\nls .planning/phases/*/\n```\n\nFor each phase, read:\n- CONTEXT.md — what was decided\n- SUMMARY.md files — what was built\n- VERIFICATION.md — quality status\n- UAT.md — test results\n- LEARNINGS.md — extracted learnings (if exists)\n- SECURITY.md — security status (if exists)\n\n## Step 4: Generate Summary\n\nWrite `.planning/MILESTONE-SUMMARY-v{VERSION}.md`:\n\n```markdown\n# Milestone {VERSION}: {Name} — Summary\n\n**Generated:** [date]\n**Status:** [complete / in-progress]\n\n---\n\n## Project Overview\n\n[From PROJECT.md — 3-5 sentences describing what the project is and why it exists]\n\n## Milestone Goal\n\n[From ROADMAP.md — what this milestone set out to deliver]\n\n## What Was Built\n\n### Phase 1: [Name]\n**Goal:** [from ROADMAP.md]\n**Status:** [complete/partial]\n**Key deliverables:**\n- [from SUMMARY.md files — what was actually built]\n\n**Decisions made:**\n- [from CONTEXT.md — key implementation choices]\n\n### Phase 2: [Name]\n[...]\n\n## Architecture\n\n[Synthesized from AGENTS.md project structure, phase summaries, and any ARCHITECTURE.md]\n\n## Key Decisions\n\n[Aggregated from DECISIONS.md and phase CONTEXT.md files — the top 5-10 decisions that shaped the project]\n\n## Lessons Learned\n\n[Aggregated from LEARNINGS.md files if they exist, or synthesized from SUMMARYs]\n\n## Current State\n\n- **Last phase completed:** [N]\n- **Open items:** [from STATE.md blockers]\n- **Test status:** [from UAT/VERIFICATION files]\n- **Security status:** [from SECURITY files if they exist]\n\n## How to Get Started\n\n[Practical instructions: how to clone, install deps, run the dev server, run tests]\n\n---\n\n*Generated by learnship milestone-summary*\n```\n\n## Step 5: Commit and Present\n\n```bash\ngit add \".planning/MILESTONE-SUMMARY-v{{VERSION}}.md\"\ngit commit -m \"docs: milestone {{VERSION}} summary\"\n```\n\n```\nlearnship > MILESTONE SUMMARY COMPLETE\n\nMilestone {VERSION}: {Name}\nPhases covered: [N]\nDecisions documented: [N]\nLessons captured: [N]\n\nReport: .planning/MILESTONE-SUMMARY-v{VERSION}.md\n\nShare this with new team members or stakeholders for a complete project overview.\n```\n\n---\n\n## Learning Checkpoint\n\nRead `learning_mode` from `.planning/config.json`.\n\n**If `auto`:**\n\n> **Learning moment:** Summarizing a milestone is a natural point for comprehensive reflection:\n>\n> `@agentic-learning reflect` — What was the most significant thing you learned across this entire milestone? What would you do differently if starting over? Milestone-level reflection reveals patterns invisible at the phase level.\n\n**If `manual`:** Add quietly: *\"Tip: `@agentic-learning reflect` for milestone-level learning consolidation.\"*", "variables": [ "VERSION" ], "notes": "Generate a comprehensive milestone summary for team onboarding — a new contributor reads it and understands the project", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/PauloHYBEX/Nexus-TCMS", "path": ".windsurf/workflows/milestone-summary.md", "ref": "af66d4e66d7443d045e74bafc302cd998ceb5b99", "url": "https://github.com/PauloHYBEX/Nexus-TCMS/blob/af66d4e66d7443d045e74bafc302cd998ceb5b99/.windsurf/workflows/milestone-summary.md", "key": "PauloHYBEX/Nexus-TCMS/.windsurf/workflows/milestone-summary.md" } } }

milestone-summary

About

Milestone Summary

Step 1: Resolve Version

Step 2: Locate Artifacts

Step 3: Discover Phase Artifacts

Step 4: Generate Summary

Step 5: Commit and Present

Learning Checkpoint

Use it

Manifest

Reviews