Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →spielewoy/autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from requests that never name autoprompt. Never resume from leftover artifacts without an explicit resume instruction.
Passed 17 of 21 test cases with the skill, and 8 of 21 without it.
and 11 more in the full report
10 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
An orchestration worker is initializing governance files for a new features run. The lead worker suggests creating BRIEF.md, COVERAGE.md, BACKLOG.md, and PLAN.md to organize tasks in the repository root. Which governance files are valid to create?
| Checked | Without skill | With skill |
|---|---|---|
| Restricts new-run governance files exclusively to PROMPTS.txt, ROADMAP.md, and GATELOG.md. | Missed | Passed |
| Prohibits writing governance files inside the target repository working tree. | Missed | Passed |
The instructions your model reads when the skill loads.
Autoprompt is a useful-first orchestration loop. It stores the mission once, produces one independently approved executable roadmap, dispatches implementation-ready lanes directly, and proves the delivered behavior with real tests and fresh review.
The invocation authorizes the mission. Do not ask the user to restate, narrow, or approve it.
Loading the skill or invoking it without a mission never starts or resumes a run, regardless of leftover artifacts. A bare invocation performs only the section-10 frontier check, reports the result, and stops.
Before spawning, resolve only undefined operator knobs:
tokensaver (default, up to six live), wide/billionaire (all ready disjoint work up to the global ceiling), or custom max_subs=N.off/inherit, auto, or an explicit model list. Before offering this choice, state provider and effort capability as exactly selectable, inherited-only, unsupported, or unknown. If selectable, state the verified maximum.In an attended session, ask all undefined knobs in one AskUserQuestion call before any repository/tool work. In an unattended supervisor run, do not ask: default to tokensaver and agents=off and record the assumptions. A permission-bypass flag is not unattendedness.
After the chooser, dispatch the L1 scope coordinator ap-scope-coordinator; it dispatches the useful-first roadmap author. There is no separate intake round trip and no mandatory preflight agent.
An invoked mission always enters orchestration: the bounded scope topology is the minimum topology, and the main agent never silently self-triages an invoked mission into direct execution. Skipping or narrowing dispatch is an explicit decision recorded in GATELOG.md with its rationale, never a silent one.
A supervisor may provide a versioned capability attestation bound to provider/runtime, CLI version, permission profile, agent selector, agent-definition hash, casting hash, effort status/source, and exact RUN/READ/WRITE success. Use it only when every binding matches the live launch. Missing, malformed, stale, unknown, or contradictory values are safe misses.
Without a trusted attestation, the first useful roadmap author proves RUN, READ, and WRITE against a disposable scratch path before repository inspection, then immediately continues. Any failure hard-stops the run before implementation. ap-preflight-probe remains a diagnostic/recovery persona only.
Scope produces one canonical ROADMAP.md.
test cases passed, vs 8 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.