gsd-autonomous

Execute remaining milestone phases through discuss, plan, and execute sequences.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-autonomous-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-autonomous
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-autonomous
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-autonomous-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the burden of manually driving a multi-phase milestone workflow by coordinating discuss → plan → execute for each remaining phase until completion.

Core Features & Use Cases

  • Autonomous phase pipeline: Runs the remaining milestone phases by performing discuss, then generating a plan, then executing that plan per phase.
  • User-decision gates: Pauses only for grey-area approvals, blocker confirmations, or explicit validation requests so you stay in control where it matters.
  • Milestone progress bookkeeping: Creates and updates planning state files and per-phase artifacts so you can audit what happened and resume later.

Quick Start

Run gsd-autonomous to execute all remaining phases for your current milestone autonomously using interactive gates only when necessary.

Frequently Asked Questions about gsd-autonomous

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

FAQPage Schema
How do I automate completion of remaining milestone phases in a project workflow?

Automating remaining milestone phases involves running a sequence of discuss, plan, and execute steps for each phase. This workflow orchestration targets phase discovery, gated approvals, and blocker-aware execution to produce audit-ready artifacts.

How does workflow orchestration handle user decisions during DAG execution?

Workflow orchestration pauses DAG execution only for grey-area approvals, blocker confirmations, or explicit validation requests. This gated approach ensures you maintain control over critical decisions while the autonomous phase pipeline runs.

What is the best way to maintain an audit trail for multi-phase milestone execution?

Maintaining an audit trail for milestone execution requires updating state management files like STATE.md and ROADMAP.md, and generating per-phase CONTEXT, PLAN, and SUMMARY artifacts to track progress and ensure continuity for later resumption.

Do I need existing planning files to resume a milestone autonomously?

Yes, resuming milestone execution autonomously requires existing planning files. The workflow reads .planning/STATE.md and .planning/ROADMAP.md to discover remaining phases, generate plans, and execute them in sequence to completion.

When should I not use autonomous execution for project milestones?

You should avoid autonomous milestone execution when a phase requires continuous manual intervention outside of gated approvals. If your workflow lacks clear phase boundaries or state management files, blocker-aware execution cannot operate effectively.