gsd-autonomous

Execute remaining milestone phases with discuss, plan, and execute cycles.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-autonomous-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-autonomous
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-autonomous-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many projects stall on repetitive per-phase work because teams must manually run discuss, plan, and execute cycles and update planning artifacts after each phase. This Skill eliminates that friction by automating end-to-end phase execution while preserving decision gates and user prompts for critical choices.

Core Features & Use Cases

  • End-to-end autonomous execution of every remaining milestone phase with discuss → plan → execute progression.
  • Progress tracking and state updates that write to .planning/STATE.md and .planning/ROADMAP.md and generate per-phase CONTEXT, PLAN, and SUMMARY artifacts.
  • Flexible controls including start/stop/only flags and an interactive mode that pauses for user decisions while running planning and execution as background agents.
  • Use Case: Resume a paused milestone and autonomously complete all remaining phases while keeping audit trails and performing milestone cleanup at the end.

Quick Start

Run the gsd-autonomous skill to autonomously execute all remaining milestone phases, updating ROADMAP.md and .planning/STATE.md and pausing only for required user decisions.

Frequently Asked Questions about gsd-autonomous

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project milestone phase execution from start to finish?

Yes, you can pause for interactive decisions during autonomous phase execution by enabling interactive mode. This mode runs planning and execution as background agents while pausing the workflow only when critical user input is required, keeping the milestone moving without losing decision gates.

How does autonomous phase execution track project state and progress?

Autonomous phase execution tracks project state by reading phase definitions from ROADMAP.md and continuously updating .planning/STATE.md and .planning/ROADMAP.md. It also generates per-phase CONTEXT, PLAN, and SUMMARY artifacts to maintain a complete audit trail of the workflow progression.

Can I control which milestone phases run when resuming an autonomous workflow?

Yes, you can control which milestone phases run using flexible start, stop, and only flags. These controls let you specify a phase range or target individual phases when resuming a paused milestone, allowing you to skip completed work and execute only the remaining required phases.

Do I need a ROADMAP.md file to run autonomous multi-phase project workflows?

Yes, you need a ROADMAP.md file to run autonomous multi-phase project workflows because the Skill performs ROADMAP.md discovery to identify phase definitions and milestones. Without this file, the workflow cannot determine the required phases or track progress in the .planning directory.

What is the best way to handle blockers during automated project phase execution?

The best way to handle blockers during automated project phase execution is to use the built-in blocker handling mechanism, which detects issues during the discuss, plan, and execute cycles and pauses the workflow, optionally using interactive mode to prompt the user for resolution decisions.