autopilot
Run the idea-to-ship pipeline AUTONOMOUSLY, in character as a grounded founder-persona — composing ideate → deep-dive → prompt-pack → build-loop to take a real, grounded niche to a near-finish-line-AIMED first-draft product plus an honest ledger of what only a human or the market can finish. ALWAYS invoke when the user says any of "run autopilot", "build this idea→ship autonomously", "spin up a grounded founder and build it", "fly the whole pipeline end to end", or "autonomous first-draft from a concept". It composes the existing skills, never reimplementing them, and states its honest bounds
npx skills add nelsonwerd/idea-to-ship-skills --skill autopilot --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Autopilot — autonomous idea→ship orchestrator `autopilot` flies the **idea-to-ship pipeline end to end, autonomously**, in character as a *grounded* founder-persona — productizing the "paste one kickoff and the pipeline runs itself" pattern. It takes a real, grounded niche and hands back a **near-finish-line-AIMED first-draft product + an honest validation ledger**. It is an **orchestrator: it composes the existing skills and never reimplements them.** It invokes `ideate`, `deep-dive`, `prompt-pack`, and `build-loop`, carries each one's file output into the next, and adds only the connective tissue — the autonomy contract, the corrected gate, the kill-ledger, and an honest hand-off. If you find yourself pasting a sub-skill's procedure into this run, stop: invoke the skill instead. It states its limits in its own text (below) because the whole point is an honest first draft, not an oversold "finished product." ## When to use this **Strong triggers — invoke without asking:** - "Run autopilot" / "fly the whole pipeline" / "take this idea→ship autonomously" - "Spin up a grounded founder-persona and build it" / "autonomous first-draft from this concept/niche" **Softer triggers:** - Yo
- When to use this
- What it produces — and its honest bounds (read this before you trust it)
- The pipeline it flies (compose, never copy)
- The autonomy contract
- Execute-discipline (inherited from prompt-pack) — never fake a gate
- The corrected gate (proceed / park)
- The kill-ledger (LOCKED)
- The kickoff (emitted each run)
- Context / handoff safety-net
- Model tiering (spend reasoning where judgment lives)
- Pitfalls to avoid
- Scale heuristics
What does the autopilot skill do?
Run the idea-to-ship pipeline AUTONOMOUSLY, in character as a grounded founder-persona — composing ideate → deep-dive → prompt-pack → build-loop to take a real, grounded niche to a near-finish-line-AIMED first-draft product plus an honest ledger of what only a human or the market can finish. ALWAYS invoke when the user says any of "run autopilot", "build this idea→ship autonomously", "spin up a grounded founder and build it", "fly the whole pipeline end to end", or "autonomous first-draft from a concept". It composes the existing skills, never reimplementing them, and states its honest bounds
How do I install it?
Run `npx skills add nelsonwerd/idea-to-ship-skills --skill autopilot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nelsonwerd/idea-to-ship-skills, a repository with 78 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.