coco-research/gsd-autonomous
Run all remaining phases autonomously — discuss→plan→execute per phase
npx skills add https://github.com/coco-research/coco --skill gsd-autonomous
<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 phaseAfter: 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-tools.cjs init milestone-op, gsd-tools.cjs roadmap analyze). No upfront context loading needed.
</context>
<process>
Execute the autonomous workflow from @$HOME/.claude/get-shit-done/workflows/autonomous.md end-to-end.
Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display).
</process>
Take coco-research/gsd-autonomous from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.