gsd-autonomous

Automate milestone phases with discuss, plan, and execute cycles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates manual, repetitive coordination of milestone phases by autonomously running discuss → plan → execute cycles, tracking progress, and updating project state so teams can focus on decisions and reviews instead of orchestration.

Core Features & Use Cases

  • End-to-end Phase Orchestration: Discover phases from ROADMAP.md and run each phase through discussion, planning, execution, and summary steps.
  • Stateful Progress Tracking: Update .planning/STATE.md and ROADMAP.md after each phase and emit phase artifacts such as CONTEXT.md, PLAN, and SUMMARY.
  • Blocker Handling & Approvals: Pause for user decisions on grey-area choices, surface blockers for remediation, and resume after validation.
  • Use Case: Fully automate completing a release milestone that requires multiple cross-functional phase steps, gating on approvals and producing audit artifacts.

Quick Start

Invoke the gsd-autonomous skill to autonomously run all remaining milestone phases, optionally starting at a specific phase using the --from N flag.

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 phases in a project that uses ROADMAP.md?

You can automate milestone phases by invoking an autonomous workflow that runs discuss, plan, and execute cycles for each phase defined in ROADMAP.md. It updates project state and emits phase artifacts like CONTEXT.md and SUMMARY until the milestone is complete.

What is autonomous milestone orchestration and how does it handle blockers?

Autonomous milestone orchestration automatically sequences phase execution from discovery to summary. When it encounters grey-area choices or blockers, it pauses execution to surface the issue for user decisions and resumes only after validation or approval gates are passed.

Can I start automated phase execution from a specific milestone step?

Yes, you can start automated phase execution from a specific step by using the --from N flag. This allows you to skip already completed phases and resume the discuss, plan, and execute cycles from phase N onwards.

Does autonomous milestone execution require specific workflow files?

Yes, autonomous milestone execution requires projects to use ROADMAP.md and gsd-tools workflows for milestone orchestration. It relies on these to track state in .planning/STATE.md and create phase artifacts during execution.

What state files and artifacts are generated during automated milestone completion?

Automated milestone completion updates .planning/STATE.md and ROADMAP.md after each phase. It also generates phase-specific artifacts including CONTEXT.md, PLAN, and SUMMARY files to provide audit trails and track orchestration progress.

When should I avoid using autonomous milestone orchestration?

You should avoid autonomous milestone orchestration if your project does not use ROADMAP.md or gsd-tools workflows, as the execution logic depends on these files to discover phases, track state, and update progress throughout the milestone lifecycle.