plugins/gsd/skills/autonomous/SKILL.md
Run all remaining phases autonomously — discuss→plan→execute per phase
npx skillsauth add davepoon/buildwithclaude gsd:autonomousInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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> @${CLAUDE_PLUGIN_ROOT}/workflows/autonomous.md @${CLAUDE_PLUGIN_ROOT}/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>
tools
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
data-ai
Use at the start of any conversation about a startup idea, product validation, founder strategy, or work inside a `startup/` workspace. Establishes file conventions, voice-input handling, subagent dispatch rules, and how to update each artifact safely. Activate before invoking any other startup-superpowers skill.
tools
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.
development
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.