jmochel/gsd-audit-milestone

<cursor_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-audit-milestone 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> Verify milestone achieved its definition of done. Check requirements coverage, cross-phase integration, and end-to-end flows.

This command IS the orchestrator. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring. </objective>

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

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

Core planning files are resolved in-workflow (init milestone-op) and loaded only as needed.

Completed Work: Glob: .planning/phases//-SUMMARY.md Glob: .planning/phases//-VERIFICATION.md </context>

<process> Execute the audit-milestone workflow from @/home/jmochel/pers/viracocha/.cursor/get-shit-done/workflows/audit-milestone.md end-to-end. Preserve all workflow gates (scope determination, verification reading, integration check, requirements coverage, routing). </process>