agentleFS
sp1esp1e/claude-skills/gsd-autonomous/SKILL.md

gsd-autonomous

Skill1 starsChanged 31 days agoMITView on GitHub

Run all remaining phases autonomously — discuss→plan→execute per phase

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md
<objective> Execute all remaining milestone phases autonomously. For each phase: discuss → plan → execute. Pauses only for user decisions (grey area acceptance, blockers, validation requests).

Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.

Creates/Updates:

  • .planning/STATE.md — updated after each phase
  • .planning/ROADMAP.md — progress updated after each phase
  • Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase

After: Milestone is complete and cleaned up. </objective>

<execution_context> @$HOME/.claude/get-shit-done/workflows/autonomous.md @$HOME/.claude/get-shit-done/references/ui-brand.md </execution_context>

<context> Optional flags: - `--from N` — start from phase N instead of the first incomplete phase. - `--to N` — stop after phase N completes (halt instead of advancing to next phase). - `--only N` — execute only phase N (single-phase mode). - `--interactive` — run discuss inline with questions (not auto-answered), then dispatch plan→execute as background agents. Keeps the main context lean while preserving user input on decisions.

Project context, phase list, and state are resolved inside the workflow using init commands (gsd-sdk query init.milestone-op, gsd-sdk query roadmap.analyze). No upfront context loading needed. </context>

<process> Execute end-to-end. Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display). </process>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.