About auto
`auto` is a workflow skill that coordinates task understanding, definition, and execution. It invokes the next phase in the same turn after understanding or definition, and ends when execution finishes or escalates, or definition reports no manifest path.
Key features
- 01Chains understanding, definition, and execution
- 02Continues to the next phase in the same turn
- 03Supports flows with or without a project
- 04Stops with usage when no task can be inferred
Use cases
- 01Advancing a task through multiple workflow phases
- 02Running a task chain in a chat without a workspace
- 03Handling definition that returns no manifest path
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ doodledood/ manifest-dev --skill autoAfter installing, type/autoin Claude Code to confirm it loaded.
Details
From the project READMERead ../ticket-up/references/AUTHORITY.md before acting. Keep this assignment, its applicable
authority and retained decisions in every skill handoff; an isolated caller must receive them
explicitly, with the useful intent and evidence.
Run the flow for the task given or inferable from the conversation; with neither, halt with usage.
Where shared understanding is missing, invoke figure-out with the task and
--autonomous; invoke define with --autonomous; invoke do with the exact
Manifest path define reports. No path → stop and report.
figure-out and define each end by stopping and leaving the next step to their caller. You are that caller: figure-out's read and define's handoff are checkpoints that return control to this flow, so invoke the next step in the same turn rather than ending it or offering the step to the user. The run ends when do finishes or escalates, or when define reports no path.
The chain runs the same with or without a project — a chat with no workspace, a home or scratch folder. Each skill it invokes decides whether any project surface applies.
Do not set or print a continuation goal during understanding or definition. /do owns the completion backstop. Automatic continuation begins at execution; an interrupted earlier phase must be restarted by the caller.