Cds autonomous
Skill Enakoneschniy/claude-dev-stack/vendor/cds-workflow/skills/cds-autonomous
One command to set up a complete AI-powered development workflow with Claude Code. Persistent memory, session management, 35+ CLI tools.
npx -y skills add Enakoneschniy/claude-dev-stack --skill cds-autonomousAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run all remaining phases autonomously — discuss→plan→execute per phase
SKILL.md
1.9 KB, as published. Nobody here has run it
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/cds-workflow/workflows/autonomous.md @$HOME/.claude/cds-workflow/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>