jmochel/gsd-milestone-summary

<cursor_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-milestone-summary or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Cursor tools when executing GSD workflows:

• Shell for running commands (terminal operations)
• StrReplace for editing existing files
• Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use Task(subagent_type="generalPurpose", ...)
• The model parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter>

<objective> Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.

Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions. Output: MILESTONE_SUMMARY written to .planning/reports/, presented inline, optional interactive Q&A. </objective>

<execution_context> @/home/jmochel/pers/viracocha/.cursor/get-shit-done/workflows/milestone-summary.md </execution_context>

<context> **Project files:** - `.planning/ROADMAP.md` - `.planning/PROJECT.md` - `.planning/STATE.md` - `.planning/RETROSPECTIVE.md` - `.planning/milestones/v{version}-ROADMAP.md` (if archived) - `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived) - `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)

User input:

• Version: {{GSD_ARGS}} (optional — defaults to current/latest milestone) </context>

<process> Read and execute the milestone-summary workflow from @/home/jmochel/pers/viracocha/.cursor/get-shit-done/workflows/milestone-summary.md end-to-end. </process>

<success_criteria>

• Milestone version resolved (from args, STATE.md, or archive scan)
• All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
• Summary document written to .planning/reports/MILESTONE_SUMMARY-v{version}.md
• All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
• Summary presented inline to user
• Interactive Q&A offered
• STATE.md updated </success_criteria>