Start a new GSD milestone and recommend the next not-started phase.
npx skills add https://github.com/gyuha/super-gsd --skill sg-new
Please help me install this Agent Skill. Skill: sg-new Source: https://github.com/gyuha/super-gsd/tree/main/skills/sg-new Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-new
It prevents fragile handoffs by starting the next milestone in the super-gsd loop and immediately telling you which phase to run next, instead of leaving you to manually choose the right GSD command and lose continuity.
gsd-new-milestone to initialize the new planning cycle.sg-plan for that phase so you keep GSD → Superpowers → sg-retro connected.Run the sg-new skill after you finish a milestone to automatically start the next milestone and receive the recommended sg-plan step.
High-intent search queries and answers about installing and using this skill.
Automating milestone transitions requires a workflow orchestration step that invokes the new milestone setup and derives the next phase from existing planning state files. This prevents context loss by automatically recommending the next not-started phase instead of manual command selection.
Context handoff in planning workflow automation is the process of passing milestone state and roadmap data between sequential phases. It uses state files like STATE.md and ROADMAP.md to determine the correct next step, ensuring continuity across the GSD cycle without re-running or skipping parts.
To start a new milestone and auto-recommend the next planning phase, invoke a milestone initialization command once with forwarded arguments. The system then reads the generated planning state and roadmap to emit a recommendation for the first not-started phase, keeping the workflow connected.
Yes, milestone kickoff works with existing ROADMAP.md planning files by reading them after milestone initialization to detect the first not-started phase. This pipeline-safe handoff uses the planning state to determine the correct next step and avoid broken context.
Planning workflows lose continuity between milestones when manual command selection causes fragile handoffs. Without an orchestration step that reads the current planning state and roadmap to recommend the next phase, the GSD cycle disconnects and context is lost.
You should not use automated milestone transitions when no valid not-started phase exists in your planning state files, or when you are not operating within a GSD workflow loop. The automation requires STATE.md and ROADMAP.md to derive and emit the next phase recommendation.
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.
gyuhaDetermine the current orchestration stage and route to the next sg-* command from STATE.md and HANDOFF.md files.
Pear-CommerceIdentify and execute the next logical step in GSD project workflows.