Complete learning loop phases or close milestones with handoff recording.
npx skills add https://github.com/gyuha/super-gsd --skill sg-complete
Please help me install this Agent Skill. Skill: sg-complete Source: https://github.com/gyuha/super-gsd/tree/main/skills/sg-complete Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-complete
It prevents fragile, manual handoffs when finishing work in the GSD → Superpowers → sg-retro loop by reliably completing the requested phase or closing the current/target milestone while archiving lessons and recording handoff state.
vX.Y (milestone versions) from bare phase numbers to avoid accidentally passing an incorrect value to gsd-complete-milestone.Use case: You finish planning and retro work for a milestone and want the system to archive the resulting lessons, update the orchestration ledger, and close the milestone without you manually running the right sequence of commands.
Run /super-gsd:sg-complete v1.4 to archive lessons and close milestone v1.4 via the gsd-complete-milestone handoff.
High-intent search queries and answers about installing and using this skill.
To close a milestone without losing context, you route the milestone version to a completion workflow that archives lessons, appends a HANDOFF row to the orchestration ledger, and delegates to milestone closure. This ensures context and lessons persist across cycles.
Phase completion in workflow orchestration works by routing a bare phase number to a dedicated phase completion handler. This ensures the phase-owned reconciliation runs exactly once, preventing fragile manual handoffs when finishing planning work.
The best way to archive lessons learned after a retrospective is to trigger milestone closure with a version argument. The system archives the resulting lessons and records handoff state automatically before finishing the milestone.
To prevent incorrect arguments during phase completion, the system uses stage-safe argument parsing to distinguish bare phase numbers from milestone versions. This strict argument-shape routing avoids accidentally passing an incorrect value to the wrong workflow.
No, you do not need to manually resolve milestone versions from STATE.md to close a milestone. For the no-argument case, the system automatically resolves the current milestone version from STATE.md before proceeding with the handoff.
Yes, you can complete both specific phases and current milestones using the same command. The system applies strict argument-shape routing to differentiate between bare phase numbers and milestone versions, directing each to the appropriate completion workflow.
jedmamostoAutomate remaining milestone phases via discuss, plan, and execute cycles.
onelee85Plan and initialize a new milestone cycle by updating planning files and routing to requirements.
gyuhaDetect super-gsd workflow sessions and route to the next action.
Eric-Pacheco95Synthesize project lessons into themes and candidate steering rules.