| name | one-shot |
| description | Autonomously turn a one-line product concept into an audited, building, test-green codebase — the whole pre-launch lifecycle in one unattended run. Use when the user wants to go from idea to working code with minimal hand-holding: "build me a whole app", "one-shot a project", "take this concept to code", "spin up the entire thing end to end", "autonomous build / zero to code", or invokes /one-shot. It writes a research-backed PRD, picks a ~$0 stack, drafts and audits architecture contracts, derives and audits tickets, implements them wave-by-wave with review + CI gates, then audits and remediates the code to green — deferring every human-only decision (branding, pricing, accounts, deploy) to a DECISIONS.md ledger instead of stopping. Resumable; safe by default (never creates accounts, spends money, handles secrets, or deploys). One new project per run.
|
one-shot
Take a concept to working code, unattended. This file is the entry point and router; the engine and
each stage's procedure live in references/. Read references/00-orchestration.md — it is the
authoritative run loop — and follow it.
Entry
Invoked as /one-shot "<concept>" [target-dir], or whenever the user describes a whole project they
want built end-to-end.
- Get the concept. One line describing what to build. If the user gave a longer brief, distill
the one-line concept and keep the brief as context for the PRD stage.
- Resolve the target dir. Use the provided one, else a new subdirectory named from the concept
slug. If it already contains
.one-shot/run-state.json, this is a resume — skip Init and let
the engine re-enter at the first incomplete stage.
- Capture optional preferences (non-blocking). If the brief or a
.one-shot/preferences.md
states vendor/stack constraints — pinned vendors, region / data-residency, open-source bias,
budget ceiling, "avoid X" — record them for stage 2 (references/02-stack-infra.md), which
honors them. Absent → stage 2 selects on merit. Never block on their absence.
Stage 0 — Init
Once, at the start of a fresh run:
- Create the target dir and run
git init there.
- Create
<target>/.one-shot/ and copy assets/templates/run-state.json into it; fill in
concept and target_dir.
- Copy
assets/templates/DECISIONS.md to <target>/DECISIONS.md.
- Mark
init done in run-state.
(TICKETS.md, LOGBOOK.md, and the contract files are created by their stages, from the other
templates in assets/templates/.)
Run
Hand control to the engine: follow references/00-orchestration.md. It runs the loop — find the
first incomplete stage, dispatch it to a fresh subagent pointed at its reference, gate it, update
run-state, repeat — until all stages are done/flagged (then Finish) or one is blocked (halt
with a report).
Do not stop to ask the human whether to continue. The only stops are a fatal blocked stage or
completion. Decisions a human would normally make are deferred or blocked-and-queued per
references/08-decisions-ledger.md, never a reason to pause.
Reference map
| File | Role |
|---|
references/00-orchestration.md | the run loop, run-state, gate policy, dispatch table, finish report |
references/01-prd.md | stage 1 — research-backed PRD (sole owner of 01-product/*) |
references/02-stack-infra.md | stage 2 — ~$0 stack/infra + merit-based vendor selection + abstraction; ADRs |
references/03-contracts.md | stage 3 — architecture contracts + operational substrate |
references/04-contracts-audit.md | stage 3 gate — audit the contracts |
references/04b-design.md | stage 4 — design system + UX flows + aesthetic (conditional — UI only) |
references/05-tickets.md | stage 5 + the tickets-audit procedure (scopes: pre-code / delta / full) |
references/06-coding-run.md | stages 6 & 8 — wave implementation + per-wave review |
references/07-codebase-audit.md | stage 7 — 27-dimension code audit |
references/08-decisions-ledger.md | how decisions are deferred or blocked |
Safety (non-negotiable)
This skill runs unattended, so it is safe by default. It never creates accounts, logs in, handles
real secrets, spends money, purchases domains, deploys to production, sends real messages, or changes
access controls. Anything in that class is blocked and queued in DECISIONS.md, never attempted
(see references/08-decisions-ledger.md).
