gsd-autonomous

Execute project phases autonomously through discuss-plan-execute cycles with state management.

60|23|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tomascortereal/claude-code-setup --skill gsd-autonomous-tomascortereal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/tomascortereal/claude-code-setup/tree/main/skills/gsd-autonomous
Command: npx skills add https://github.com/tomascortereal/claude-code-setup --skill gsd-autonomous-tomascortereal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for manual phase-by-phase oversight by autonomously executing all remaining project milestones, reducing project completion time and cognitive load.

Core Features & Use Cases

  • Autonomous Phase Execution: Runs all remaining project phases through a structured discuss→plan→execute workflow without manual intervention.
  • Flexible Phase Control: Supports starting from specific phases, stopping at designated milestones, or running single phases interactively.
  • State Management: Automatically updates project state files (STATE.md, ROADMAP.md) and generates phase artifacts (CONTEXT.md, PLANs, SUMMARYs).
  • Use Case: Ideal for long-term projects where you need to maintain momentum while only providing critical decision points at phase boundaries.

Quick Start

Use the gsd-autonomous skill to run all remaining phases of the current project.

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 phase execution across multiple milestones with minimal oversight?

Autonomous project phase execution uses a predefined discuss-plan-execute cycle to run milestones automatically, only stopping for user decision gates at critical junctures to reduce manual oversight. It manages state files and generates artifacts throughout.

What is the discuss-plan-execute workflow for milestone-based project management?

The discuss-plan-execute workflow is an automated cycle that handles phase discovery, generates phase artifacts like CONTEXT.md and PLANs, and updates project state files. It progresses through milestones autonomously while preserving user decision gates at phase boundaries.

Can I run a single project phase interactively instead of executing all remaining milestones?

Yes, flexible phase control supports starting from specific phases, stopping at designated milestones, or running single phases interactively. You can target individual milestones without executing the entire remaining project roadmap.

How do I maintain project state files when scaling long-term autonomous workflows?

Autonomous execution automatically updates project state files including STATE.md and ROADMAP.md while generating phase artifacts like CONTEXT.md, PLANs, and SUMMARYs. This ensures continuous state management across long-term project scaling.

When should I avoid autonomous milestone automation for project phases?

Autonomous milestone automation is not ideal for projects requiring continuous manual oversight or lacking clear phase boundaries. It suits milestone-based projects where decision gates at phase boundaries provide sufficient control over autonomous progression.

Do I need existing roadmap files to start autonomous phase execution?

Autonomous phase execution integrates with existing project state by reading and updating ROADMAP.md and STATE.md files. Having these project state files established ensures accurate phase discovery and milestone tracking during automated execution.