gsd-autonomous

Automate milestone phase completion by running discuss-to-execute workflows sequentially.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-autonomous-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-autonomous
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-autonomous-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates the back-and-forth of completing milestone phases by running the discuss→plan→execute loop autonomously until the milestone is done, only stopping when a user decision is required.

Core Features & Use Cases

  • Phase autonomy across the milestone: Automatically discovers remaining phases and runs each phase through discuss → plan → execute.
  • Workflow gating and pause points: Preserves approval/validation decision points (e.g., grey-area acceptance, blockers, validation requests).
  • Progress and artifacts tracking: Updates .planning/STATE.md and .planning/ROADMAP.md and writes per-phase artifacts like CONTEXT, PLANs, and SUMMARYs to keep the run auditable.

Quick Start

Run gsd-autonomous from the first incomplete phase of your current milestone to complete it through all remaining phases.

Frequently Asked Questions about gsd-autonomous

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

FAQPage Schema
How do I automate milestone execution across multiple project phases?

Workflow orchestration pauses milestone execution for approval gates when encountering blockers, grey-area acceptance criteria, or validation requests, resuming only after the required user decision is provided.

Can I preserve approval gates during autonomous project phase execution?

Autonomous phase execution pauses for approval gates when encountering blockers, grey-area acceptance criteria, or validation requests, resuming only after the required user decision is provided.

How does autonomous workflow orchestration track planning state and artifacts?

Workflow orchestration tracks planning state by updating `.planning/STATE.md` and `.planning/ROADMAP.md` files, while writing per-phase artifacts like CONTEXT, PLANs, and SUMMARYs to keep the run auditable.

What's the best way to discover and complete remaining roadmap phases hands-off?

Workflow orchestration tracks planning state by updating `.planning/STATE.md` and `.planning/ROADMAP.md` files, while writing per-phase artifacts like CONTEXT, PLANs, and SUMMARYs to keep the run auditable.

Do I need a ROADMAP.md file to run autonomous milestone workflows?

You need a ROADMAP.md file to run autonomous milestone workflows because phase discovery depends on reading this roadmap to identify incomplete phases and execute them in sequence.