just-auto

Solid

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.

AI & Automation 69 stars 10 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

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

Skill Content

Run the full flow for the given task — stated as an argument or inferable from the conversation; with neither, halt with usage. Before starting, arm the completion backstop. If an active goal's completion condition already covers this task's outcome, continue under it. Otherwise, if the harness provides a goal-setting, continuation, or durable-completion-condition capability, set this goal, with `<task>` replaced by a one-line statement of the task: "For the task <task>: shared understanding is reached — where figure-out runs, a full-anatomy Read checkpoint is completed before define runs: every load-bearing branch pressed, independent re-derivation run or explicitly unavailable, the rival set no longer moving; a missing or weak Read checkpoint is a defect to repair before define, not a terminal failure after gates pass — a Manifest is written from it, every Acceptance Criterion and Global Invariant in that Manifest holds with evidence from the artifacts they name, and completion has been reported. The Manifest, once written, is canonical and read-only. Record compact checkpoint notes as work proceeds — what changed, what was verified, what remains, blockers. Record the Manifest's path in a checkpoint note as soon as it is written. Stop only when blocked on something a person must resolve." If it provides none, print that goal in copy-pasteable form for the user's own continuation mechanism and proceed. Then: if the conversation lacks shared understanding of the task, first...

Details

Author
doodledood
Repository
doodledood/manifest-dev
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

auto

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.

69 Updated today
doodledood
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;

16 Updated yesterday
mikeprasad
AI & Automation Listed

auto

Begin or resume the Full-Auto controller, which sequences a signed outcome to a checked deliverable

0 Updated today
khalilmaaouni