gsd-autonomous

Automate milestone phases by discussing, planning, and executing with ROADMAP.md.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-autonomous-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-autonomous
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-autonomous-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end milestone execution by driving discuss → plan → execute cycles for all remaining phases, minimizing manual toil while pausing only for user decisions on blockers or validations.

Core Features & Use Cases

  • Autonomous phase execution: For each milestone phase, automatically discuss, plan, and execute, generating phase artifacts (CONTEXT.md, PLANS, SUMMARIES) and updating ROADMAP.md.
  • Progress tracking & cleanup: Maintains .planning/STATE.md and .planning/ROADMAP.md throughout, then performs milestone audit, completion, and cleanup automatically.
  • Flexible intervention points: Pauses only when the user needs to decide on blockers or validations, ensuring governance without ad-hoc runtime decisions.

Quick Start

Start the autonomous milestone workflow from the current ROADMAP state.

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 workflow phases end-to-end with minimal manual input?

Automating project workflow phases requires a system that drives discuss, plan, and execute cycles for all remaining milestone phases. This Skill autonomously progresses through each phase, generating artifacts like CONTEXT.md and PLANS while pausing only for blocker or validation decisions.

What is the best way to track milestone progress and maintain planning state files?

Tracking milestone progress is handled by continuously maintaining .planning/STATE.md and .planning/ROADMAP.md files throughout the autonomous execution. After all phases complete, the workflow automatically performs a milestone audit, completion checks, and final cleanup of these artifacts.

How does autonomous phase execution discover and iterate on remaining project milestones?

Autonomous phase execution discovers remaining milestones by leveraging ROADMAP.md for phase identification and Skill() invocations for task execution. It iteratively refines project workflows by generating phase-specific SUMMARIES and updating the roadmap after each cycle.

Can I use this autonomous milestone workflow if my project lacks a ROADMAP.md file?

Using this autonomous milestone workflow requires an existing ROADMAP.md file to properly discover and progress through phases. The Skill relies on this roadmap structure to identify remaining milestones and automatically update phase progression during execution.

When should I expect the autonomous workflow to pause and require human intervention?

The autonomous workflow pauses only when user decisions are needed for blockers or validations during milestone execution. This ensures necessary governance over the planning and execution cycles without requiring ad-hoc runtime decisions for standard phase progression.