autobuild

Name: autobuild
Author: asteroid-belt

48stars2forks

How to install autobuild?

asteroid-belt/skulto/autobuild

$npx -y skills add asteroid-belt/skulto --skill autobuild

Installs into the current project.

Summary

Autonomous single-shot plan execution. Runs entire superplan implementation plans without stopping, using sub-agents for each phase. Phases write state to filesystem for resume capability. Sequential phases run in order, parallel phases (1a, 1b) run concurrently. User never needs

Files · 1

View on GitHub

SKILL.md

1	# Autobuild: Autonomous Plan Execution Engine
2
3	Execute entire implementation plans in a single pass with zero user intervention. Each phase runs in its own sub-agent, writing state to the filesystem. Context never exhausts because sub-agents are isolated.
4
5	## Overview
6
7	Autobuild is an autonomous execution engine for superplan implementation plans. Unlike `superbuild` which stops after each phase for user confirmation, autobuild runs everything to completion.
8
9	Key Differences from superbuild:
10
11	\| Aspect \| superbuild \| autobuild \|
12	\|--------\|------------\|-----------\|
13	\| Execution \| Phase-by-phase with stops \| Continuous until complete \|
14	\| User intervention \| Required after each phase \| None (fully autonomous) \|
15	\| Context management \| Manual compaction \| Sub-agents isolate context \|
16	\| State persistence \| In conversation \| Filesystem (.autobuild/) \|
17	\| Resume capability \| Manual \| Automatic from state files \|
18
19	---
20
21	## Reference Index - MUST READ When Needed
22
23	References contain detailed templates and patterns. Read BEFORE you need them.
24
25	\| When \| Reference \| What You Get \|
26	\|------\|-----------\|--------------\|
27	\| Step 1: Initialize \| [STATE-FILES.md](references/STATE-FILES.md) \| State file format, directory structure \|
28	\| Step 3: Execute phases \| [PHASE-EXECUTION.md](references/PHASE-EXECUTION.md) \| Phase ordering, parallel detection, retry logic \|
29	\| Step 3: Launch sub-agents \| [SUBAGENT-PROMPTS.md](references/SUBAGENT-PROMPTS.md) \| Exact prompts for phase sub-agents \|
30	\| Step 4: Verify and commit \| [VERIFICATION.md](references/VERIFICATION.md) \| Fresh verification, commit handling \|
31	\| Step 5: Handle failures \| [FAILURE-HANDLING.md](references/FAILURE-HANDLING.md) \| Retry logic, error recovery \|
32	\| Overall flow \| [ORCHESTRATION.md](references/ORCHESTRATION.md) \| Main orchestration loop, completion handling \|
33
34	Also reference superplan documents:
35	- `superplan/references/TASK-MICROSTRUCTURE.md` - TDD 5-step format per task
36	- `superplan/references/TDD-DISCIPLINE.md` - TDD enforcement rules
37	- `superbuild/references/ENFORCEMENT-GUIDE.md` - Quality gate commands by stack
38
39	DO NOT SKIP REFERENCES. They contain exact prompts, templates, and formats that are NOT duplicated here.
40
41	---
42
43	## CLI Arguments
44
45	```
46	/autobuild <plan-path> [options]
47
48	Arguments:
49	plan-path Path to superplan document (required)
50
51	Options:
52	--commit=<mode> Git commit behavior (required before execution)
53	- auto: Auto-commit after each phase passes
54	- message-only: Generate messages, user handles git
55	- single: One combined commit at the end
56
57	--resume Resume from existing state (default if .autobuild/ exists)
58	--fresh Ignore existing state, start from scratch
59	--dry-run Validate plan and show execution order without running
60	```
61
62	Example invocations:
63	```bash
64	/autobuild docs/feature-plan.md --commit=auto
65	/autobuild docs/feature-plan.md --commit=message-only --resume
66	/autobuild docs/feature-plan.md --commit=single --fresh
67	```
68
69	---
70
71	## Critical Workflow
72
73	```
74	+-----------------------------------------------------------------------+
75	\| AUTOBUILD EXECUTION FLOW \|
76	+-----------------------------------------------------------------------+
77	\| \|
78	\| 1. INITIALIZE \| Parse args, create .autobuild/, detect stack \|
79	\| \| \| NO PLAN = EXIT (ask user, then exit if none) \|
80	\| v \| NO --commit = STOP (require commit mode) \|
81	\| 2. LOAD STATE \| Read existing state files if --resume \|
82	\| \| \| Identify completed phases, pending phases \|
83	\| v \|
84	\| 3. EXECUTE PHASES \| For each pending phase (or parallel group): \|
85	\| \| \| \|
86	\| \| 3a. Launch sub-agent(s) for phase(s) \|
87	\| \| - Sequential phases: one sub-agent at a time \|
88	\| \| - Parallel phases (2a,2b,2c): concurrent sub-agents \|
89	\| \| \|
90	\| \| 3b. Sub-agent executes: \|
91	\| \| - Read plan section for its phase \|
92	\| \| - Follow TDD

People who liked this also viewed

6 picks

Type

autobuild

48stars2forks

View on GitHub

How to install autobuild?

asteroid-belt/skulto/autobuild

$npx -y skills add asteroid-belt/skulto --skill autobuild

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Autobuild: Autonomous Plan Execution Engine
2
3	Execute entire implementation plans in a single pass with zero user intervention. Each phase runs in its own sub-agent, writing state to the filesystem. Context never exhausts because sub-agents are isolated.
4
5	## Overview
6
7	Autobuild is an autonomous execution engine for superplan implementation plans. Unlike `superbuild` which stops after each phase for user confirmation, autobuild runs everything to completion.
8
9	Key Differences from superbuild:
10
11	\| Aspect \| superbuild \| autobuild \|
12	\|--------\|------------\|-----------\|
13	\| Execution \| Phase-by-phase with stops \| Continuous until complete \|
14	\| User intervention \| Required after each phase \| None (fully autonomous) \|
15	\| Context management \| Manual compaction \| Sub-agents isolate context \|
16	\| State persistence \| In conversation \| Filesystem (.autobuild/) \|
17	\| Resume capability \| Manual \| Automatic from state files \|
18
19	---
20
21	## Reference Index - MUST READ When Needed
22
23	References contain detailed templates and patterns. Read BEFORE you need them.
24
25	\| When \| Reference \| What You Get \|
26	\|------\|-----------\|--------------\|
27	\| Step 1: Initialize \| [STATE-FILES.md](references/STATE-FILES.md) \| State file format, directory structure \|
28	\| Step 3: Execute phases \| [PHASE-EXECUTION.md](references/PHASE-EXECUTION.md) \| Phase ordering, parallel detection, retry logic \|
29	\| Step 3: Launch sub-agents \| [SUBAGENT-PROMPTS.md](references/SUBAGENT-PROMPTS.md) \| Exact prompts for phase sub-agents \|
30	\| Step 4: Verify and commit \| [VERIFICATION.md](references/VERIFICATION.md) \| Fresh verification, commit handling \|
31	\| Step 5: Handle failures \| [FAILURE-HANDLING.md](references/FAILURE-HANDLING.md) \| Retry logic, error recovery \|
32	\| Overall flow \| [ORCHESTRATION.md](references/ORCHESTRATION.md) \| Main orchestration loop, completion handling \|
33
34	Also reference superplan documents:
35	- `superplan/references/TASK-MICROSTRUCTURE.md` - TDD 5-step format per task
36	- `superplan/references/TDD-DISCIPLINE.md` - TDD enforcement rules
37	- `superbuild/references/ENFORCEMENT-GUIDE.md` - Quality gate commands by stack
38
39	DO NOT SKIP REFERENCES. They contain exact prompts, templates, and formats that are NOT duplicated here.
40
41	---
42
43	## CLI Arguments
44
45	```
46	/autobuild <plan-path> [options]
47
48	Arguments:
49	plan-path Path to superplan document (required)
50
51	Options:
52	--commit=<mode> Git commit behavior (required before execution)
53	- auto: Auto-commit after each phase passes
54	- message-only: Generate messages, user handles git
55	- single: One combined commit at the end
56
57	--resume Resume from existing state (default if .autobuild/ exists)
58	--fresh Ignore existing state, start from scratch
59	--dry-run Validate plan and show execution order without running
60	```
61
62	Example invocations:
63	```bash
64	/autobuild docs/feature-plan.md --commit=auto
65	/autobuild docs/feature-plan.md --commit=message-only --resume
66	/autobuild docs/feature-plan.md --commit=single --fresh
67	```
68
69	---
70
71	## Critical Workflow
72
73	```
74	+-----------------------------------------------------------------------+
75	\| AUTOBUILD EXECUTION FLOW \|
76	+-----------------------------------------------------------------------+
77	\| \|
78	\| 1. INITIALIZE \| Parse args, create .autobuild/, detect stack \|
79	\| \| \| NO PLAN = EXIT (ask user, then exit if none) \|
80	\| v \| NO --commit = STOP (require commit mode) \|
81	\| 2. LOAD STATE \| Read existing state files if --resume \|
82	\| \| \| Identify completed phases, pending phases \|
83	\| v \|
84	\| 3. EXECUTE PHASES \| For each pending phase (or parallel group): \|
85	\| \| \| \|
86	\| \| 3a. Launch sub-agent(s) for phase(s) \|
87	\| \| - Sequential phases: one sub-agent at a time \|
88	\| \| - Parallel phases (2a,2b,2c): concurrent sub-agents \|
89	\| \| \|
90	\| \| 3b. Sub-agent executes: \|
91	\| \| - Read plan section for its phase \|
92	\| \| - Follow TDD

People who liked this also viewed

6 picks

Type