Verified:GitHub

gsd-autonomous

Automate remaining milestone phases via discuss, plan, and execute cycles.

Updated May 21, 2026

Search Tags:#workflow automation #agent orchestration #phase planning #autonomous execution #project state management #milestone workflow

Ready to run

npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-autonomous-jedmamosto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-autonomous
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-autonomous-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the overhead of coordinating multi-phase work by letting an agent run the remaining milestone phases end-to-end, pausing only when user decisions are required.

Core Features & Use Cases

Phase discovery & routing: Uses ROADMAP.md and milestone state to determine which phases remain.
Discuss → plan → execute per phase: Runs each phase with explicit gating and progress tracking.
Controlled pausing for decisions: Stops for grey-area acceptance, blockers, or validation requests while continuing elsewhere autonomously.
Stateful progress artifacts: Updates .planning/STATE.md and .planning/ROADMAP.md and records per-phase outputs (CONTEXT.md, PLANs, SUMMARYs).

Quick Start

Run the skill to execute all incomplete milestone phases: gsd-autonomous --interactive.

Frequently Asked Questions about gsd-autonomous

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

FAQPage Schema

How do I automate remaining project phases in a milestone workflow?▼

Autonomous phase execution uses ROADMAP.md and milestone state to discover incomplete phases, then runs discuss, plan, and execute cycles per phase with deterministic decision gates, pausing only for user input on blockers or grey-area acceptance.

What is the best way to manage project state when running autonomous phase execution?▼

Autonomous phase execution manages project state by updating .planning/STATE.md and .planning/ROADMAP.md, recording per-phase outputs like CONTEXT.md, PLANs, and SUMMARYs to maintain stateful progress artifacts throughout the milestone workflow.

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

Autonomous milestone execution requires a phase-based ROADMAP.md and existing milestone state, because the Skill locates init workflow context from these planning artifacts to route and complete remaining phases deterministically.

Can I pause autonomous execution when a project phase hits a blocker?▼

Autonomous execution supports controlled pausing for decisions by stopping at grey-area acceptance, blockers, or validation requests, holding the milestone workflow state until the user provides the required input to continue.

How does agent orchestration handle phase planning and execution cycles?▼

Agent orchestration handles phase planning by invoking Skill() for each phase command, applying deterministic execution with explicit gating and progress tracking across discuss, plan, and execute cycles before performing a final milestone audit and cleanup.