跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

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 — a near-finish-line first draft, NOT a finished or market-validated product (~80% craft ceiling; grounding firewall; its go/kill calls are a signal). Do NOT use to drive each phase by hand (use the skills directly), when there's no real grounding (you'd be inventing demand), or when you need market validation (the human handoff).

nelsonwerd · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add nelsonwerd/idea-to-ship-skills --skill autopilot

技能说明


name: autopilot description: >- 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 — a near-finish-line first draft, NOT a finished or market-validated product (~80% craft ceiling; grounding firewall; its go/kill calls are a signal). Do NOT use to drive each phase by hand (use the skills directly), when there's no real grounding (you'd be inventing demand), or when you need market validation (the human handoff).

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:

  • You have a grounded niche (real lived pain or real data) and want a first-draft product + an honest validation ledger without hand-running each phase.

Do NOT use this for:

  • Driving each phase yourself — use ideate / deep-dive / prompt-pack / build-loop directly.
  • A concept with no real grounding — autopilot will not invent demand to fill the gap (see the firewall in Bounds).
  • Market validation — out of scope; that is the human/market handoff.
  • A settled code change (prompt-pack) or a soundness audit (deep-dive).

Routing tie-breaker: autopilot automates the manual tier. Reach for it to fly the pipeline end-to-end with eyes open on the bounds — not to replace human taste, finish, or market judgment.

What it produces — and its honest bounds (read this before you trust it)

Load-bearing, stated up front so no one reads an autonomous run as more than it is.

Produces: a grounded CONCEPT_BRIEF, a validated + sequenced build pack, a near-finish-line-AIMED first-draft product (designed + machine-validated as far as machines can check), and an honest ledger of what's checked vs. what only a human/market can verify.

The 3 eyes-open limits it does NOT escape:

  1. ~80% craft ceiling + a last-mile tail. "Near-finish-line" is the aim, not a guarantee; a correctness/security/taste tail remains for the human to finish.
  2. The grounding firewall. Real data to discover the problem and seed the build = yes. A synthetic persona's reaction to the proposed solution never counts as validation. autopilot injects real signal at the front; it does not manufacture demand.
  3. Judgment quality isn't cleanly measurable. Its go / iterate / kill calls are a signal a human weighs, never proof. "The system's judgment matches an expert" is non-gating (it's circular — it needs the market truth the system exists to replace).

Market validation is explicitly the human handoff. "Works + looks good + well-judged" ≠ "people want it." autopilot is a force-multiplier toward a finishable first draft — not a finished-product factory and not a market validator.

The pipeline it flies (compose, never copy)

Hard rule: invoke each skill and carry its file forward; never inline its content.

  1. ideate → a grounded CONCEPT_BRIEF.md — forced success-metric + kill-criterion, and (via its conditional-design forcing-function) a substantive design direction when feel is load-bearing.
  2. deep-dive → validates the brief's load-bearing claims with honest confidence + a ground-truth tally; its hand-back is folded into the brief (verdict, what's verified vs. still-a-bet).
  3. prompt-pack → sequences the validated/gated scope into self-contained build prompts; carries execute-discipline.
  4. Gate-impact pass → before each unit's build opens, enumerate the gates, frozen constraints, and conventions that unit's planned surface will trip, and clear them all in one pass. The mechanism lives in prompt-pack; autopilot's job is that the pass happens. Not optional — it is the phase gate between planning and building.
  5. build-loop → drives each shippable unit to near-finish-line craft on two co-equal tracks — the objective machine facts AND, when feel is load-bearing, the mandatory multi-pass visual design loop.

Phase-by-phase orchestration (what each invocation gets, what carries forward, where the gates are): references/pipeline-playbook.md — the gate-impact pass sits between its Phase 3 and Phase 4.

The autonomy contract

  • Run in character as the grounded persona. Answer every phase gate the founder can answer — the brain-dump, the selection rubric, the divergence ranking, the pressure-test verdict, the convergence lo
阅读完整来源 ↗