gsd-autonomous

Automates milestone execution across phases with discuss, plan and execute steps.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-autonomous-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-autonomous
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-autonomous-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute all remaining milestone phases autonomously by cycling through discuss → plan → execute, pausing only for user decisions on blockers or validation requests.

Core Features & Use Cases

  • End-to-end autonomous milestone workflow across multiple phases with per-phase artifacts.
  • Automatic generation of planning artifacts and phase summaries to support auditing and cleanup.
  • Seamless integration with ROADMAP.md for phase discovery and with Skill() phase invocations.

Quick Start

Initiate the autonomous milestone workflow to execute all remaining phases from discuss to cleanup.

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 end-to-end?

Autonomous milestone execution cycles through discuss, plan, and execute steps for all remaining phases automatically. It pauses only for user validation decisions or blocker handling, updating planning artifacts and generating phase summaries throughout the workflow.

How does autonomous workflow phase discovery work with ROADMAP.md?

Autonomous workflow phase discovery requires a ROADMAP.md file to identify remaining project phases. The workflow invokes Skill() for each phase, producing CONTEXT.md, PLANs, and SUMMARYs to support milestone auditing and final cleanup steps.

Do I need to manually resolve blockers during autonomous milestone execution?

Blocker handling during autonomous milestone execution pauses the workflow for user decisions rather than resolving them automatically. Once you address the blocker or validation request, the end-to-end execution resumes automatically through the remaining discuss, plan, and execute cycles.

What planning artifacts are generated during end-to-end milestone execution?

End-to-end milestone execution generates CONTEXT.md, PLANs, and SUMMARYs as per-phase artifacts. These planning artifacts support milestone auditing, track validation decisions, and facilitate cleanup steps upon phase completion.

Can I use this autonomous milestone workflow without any external dependencies?

The autonomous milestone workflow operates without external dependencies, relying solely on ROADMAP.md for phase discovery and Skill() phase invocations. You only need to provide the roadmap file to initiate the discuss, plan, and execute cycles.

What is the best way to handle milestone auditing and cleanup after autonomous execution?

Milestone auditing and cleanup after autonomous execution rely on the generated SUMMARYs and planning artifacts. The workflow performs audit, complete, and cleanup steps automatically once all phases finish the discuss, plan, and execute cycles.