auto

Solid

End-to-end autonomous execution: figure-out → define → do, chained without manual approval gates. Use when you want to define and execute without intervention during planning, when the user asks for autonomous or end-to-end work, says just build it, or asks to tend or babysit a PR.

AI & Automation 73 stars 10 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Chain `figure-out --autonomous` (when the transcript lacks shared understanding) → `define --autonomous` → `do` on a single task. The `--autonomous` flag on figure-out makes the model self-answer with recommended answers instead of waiting on the user (see `figure-out/references/autonomous.md`). Surface define's Summary for Approval for visibility but don't wait — treat as approved and proceed to /do. **Task text** comes from `$ARGUMENTS`; if empty, infer from conversation context (summarize the discussed task into a concrete description). Fresh session with no context and no args → halt: `No task description provided and no conversation context to infer from. Usage: /auto <task description> | /auto --babysit <pr-url>`. **Verification policy.** Parse only top-level option uses of `--verification` and `--verifier-model` as `/auto` flags; quoted or topic mentions remain task text. Omitted `--verification` means `per-gate`. After resolving that default, load the matching sibling `/do` reference under `../do/references/` and apply its policy validation before `/define`; the reference, not `/auto`, owns mode-specific model support and evidence provenance. Remove parsed flags from the task before `/define`, and forward them only to `/do`. Never write either option into the Manifest. Carry the selected mode, model provenance, and the reference's required evidence/provenance wording in the full-chain completion contract. **Babysit mode** (`--babysit <pr-url>`) skips fresh synthesi...

Details

Author
doodledood
Repository
doodledood/manifest-dev
Created
7 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

just-auto

Goal-based autonomous chain: figures out the task, encodes a Manifest, and pursues it end-to-end with full autonomy and minimal process. Use when the user asks to just build it, just auto it, run end-to-end goal-based, or go from idea to done without approval gates.

73 Updated 3 days ago
doodledood
AI & Automation Listed

auto

Autonomous unattended mode.

68 Updated yesterday
lemoncrow-lab
AI & Automation Listed

auto

Drive an autonomous execution arc end-to-end — compose brainstorm→spec→/prospect→plan→/prospect→TDD→/retrospect under the Rule 35 posture, decide objectively-validatable forks yourself, and stop only on a load-bearing fork or an ungranted approval. Modes: `arc` (default), `execute <plan|spec|ticket-id>` (skip ideation), `plan` (stop at a prospected plan, no code), `config` (guided per-run knob picker). Stackable, one word per axis: `full` (authority — all except push) · `attended`|`unattended` (presence) · `continue`|`stop` (duration) · plus `tickets` and `self-restart`. A bare invocation opens the `config` picker instead of guessing a goal. An explicit grant of autonomous latitude that overrides the standing `autonomy` config for the arc and never writes it. Use when the user hands off a goal, plan, ticket, or SESSION.md with latitude to execute WITHOUT per-step approval — 'combined go', 'run overnight', 'just build it', 'do as much as you can'. ENTRY POINT for a multi-step arc, NOT a single concrete change;

17 Updated today
mikeprasad