superbuild

Name: superbuild
Author: asteroid-belt

48stars2forks

How to install superbuild?

asteroid-belt/skulto/superbuild

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

Installs into the current project.

Summary

Use when executing implementation plans phase-by-phase with strict enforcement of quality gates, tests, and Definition of Done. Triggers on "build this plan", "execute plan", "implement phases", or when user provides a plan document to execute.

Files · 1

View on GitHub

SKILL.md

1	# Superbuild: Plan Execution Engine
2
3	Execute implementation plans one phase at a time with strict quality enforcement, test verification, and conventional commit generation.
4
5	## Overview
6
7	Superbuild is a rigid execution engine for implementation plans. It enforces:
8	- Phase-by-phase execution (no skipping ahead)
9	- Definition of Done verification before phase completion
10	- Test presence and passing verification
11	- Linter/formatter/typechecker enforcement
12	- Conventional commit message generation per phase
13
14	This is NOT a planning skill. Use `superplan` to create plans, then `superbuild` to execute them.
15
16	## Critical Workflow
17
18	```
19	┌─────────────────────────────────────────────────────────────────────┐
20	│ SUPERBUILD EXECUTION FLOW │
21	│ (REPEAT FOR EACH PHASE) │
22	├─────────────────────────────────────────────────────────────────────┤
23	│ │
24	│ 1. INGEST PLAN │ User provides plan document path │
25	│ ↓ │ NO PLAN = EXIT (ask user, then exit if none) │
26	│ 2. READ PHASES │ Output ALL phases with estimates │
27	│ ↓ │ IF context high → suggest compact first │
28	│ 3. EXECUTE PHASE │ One phase at a time (or parallel if marked) │
29	│ ↓ │ USE SUB-AGENTS for parallel phases │
30	│ 4. ENFORCE DOD │ Tests exist? Tests pass? Linter? Formatter? │
31	│ ↓ │ ALL must pass → continue. ANY fail → STOP │
32	│ 5. UPDATE PLAN │ Check off tasks, update status in plan file │
33	│ ↓ │ ⚠️ THIS HAPPENS AFTER EVERY PHASE │
34	│ 6. COMMIT MSG │ Generate conventional commit (NEVER git ops) │
35	│ ↓ │ User handles all git operations │
36	│ 7. FUNCTIONAL TEST│ Explain how to test. Offer integration script │
37	│ ↓ │ NEVER auto-create scripts. ALWAYS ask first │
38	│ 8. STOP │ Full stop. Suggest compact. Wait for user. │
39	│ │ OVERRIDE: --build-all flag continues │
40	│ │
41	│ ════════════════════════════════════════════════════════════════ │
42	│ Steps 3-8 repeat for EACH PHASE. Plan updates after EVERY phase. │
43	│ ════════════════════════════════════════════════════════════════ │
44	│ │
45	└─────────────────────────────────────────────────────────────────────┘
46	```
47
48	## Step 1: Ingest Plan
49
50	REQUIRED: Plan document must be provided.
51
52	```
53	I'll help you execute your implementation plan.
54
55	Please provide the plan document:
56	1. Path to plan file (e.g., docs/feature-plan.md)
57	2. Paste the plan content directly
58
59	Which would you prefer?
60	```
61
62	If no plan provided after asking: EXIT immediately.
63
64	```
65	I cannot execute without a plan document.
66
67	To create a plan, use the `superplan` skill first:
68	/superplan
69
70	Then come back with the completed plan.
71
72	[EXIT - No further action]
73	```
74
75	NO EXCEPTIONS. Do not improvise. Do not create plans on the fly. Do not proceed without a plan document.
76
77	## Step 2: Read All Phases
78
79	After ingesting the plan:
80
81	1. Output all phases with their estimates and dependencies
82	2. Check context usage - if high, suggest compacting first
83
84	```
85	PLAN LOADED: [Feature Name]
86	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
87
88	\| Phase \| Name \| Est. \| Depends On \| Parallel With \| Status \|
89	\|-------\|------\|------\|------------\|---------------\|--------\|
90	\| 0 \| Bootstrap \| 5 \| - \| - \| ⬜ \|
91	\| 1 \| Setup \| 3 \| 0 \| - \| ⬜ \|
92	\| 2A \| Backend \| 8 \| 1 \| 2B, 2C \| ⬜ \|
93	\| 2B \| Frontend \| 5 \| 1 \| 2A, 2C \| ⬜ \|
94	\| 2C \| Tests \| 3 \| 1 \| 2A, 2B \| ⬜ \|
95	\| 3 \| Integration \| 5 \| 2A,2B,2C \| - \| ⬜ \|
96
97	Total: 29 points \| Parallel phases: 2A, 2B, 2C
98
99	⚠️ Context Usage Advisory
100	If context is high, consider compacting before continuing.
101	Large plans consume significant context per phase.
102
103	Ready to execute Phase 0?
104	```
105
106	## Step 3: Execute Phase
107
108	### Sequential Phases
109
110	Execute one at a time. Do not proceed to next phase until current is COMPLETE.
111
112	### Parallel Phases
113
114	For phases marked "Parallel With", MUST use sub-agents or parallel Task tool calls.
115
116	```
117	EXECUTING PARALLEL PHASES: 2A, 2B, 2C
118	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
119
120	Launching 3 parallel sub-agents...
121
122	[Sub-agent 2A: Backend implementation]
123	[Sub-agent 2B: Frontend implementation]
124	[Sub-agent 2C: Test implementation]
125
126	Each sub-agent MUST return:
127	- Implementatio

People who liked this also viewed

6 picks

Type

superbuild

48stars2forks

View on GitHub

How to install superbuild?

asteroid-belt/skulto/superbuild

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Superbuild: Plan Execution Engine
2
3	Execute implementation plans one phase at a time with strict quality enforcement, test verification, and conventional commit generation.
4
5	## Overview
6
7	Superbuild is a rigid execution engine for implementation plans. It enforces:
8	- Phase-by-phase execution (no skipping ahead)
9	- Definition of Done verification before phase completion
10	- Test presence and passing verification
11	- Linter/formatter/typechecker enforcement
12	- Conventional commit message generation per phase
13
14	This is NOT a planning skill. Use `superplan` to create plans, then `superbuild` to execute them.
15
16	## Critical Workflow
17
18	```
19	┌─────────────────────────────────────────────────────────────────────┐
20	│ SUPERBUILD EXECUTION FLOW │
21	│ (REPEAT FOR EACH PHASE) │
22	├─────────────────────────────────────────────────────────────────────┤
23	│ │
24	│ 1. INGEST PLAN │ User provides plan document path │
25	│ ↓ │ NO PLAN = EXIT (ask user, then exit if none) │
26	│ 2. READ PHASES │ Output ALL phases with estimates │
27	│ ↓ │ IF context high → suggest compact first │
28	│ 3. EXECUTE PHASE │ One phase at a time (or parallel if marked) │
29	│ ↓ │ USE SUB-AGENTS for parallel phases │
30	│ 4. ENFORCE DOD │ Tests exist? Tests pass? Linter? Formatter? │
31	│ ↓ │ ALL must pass → continue. ANY fail → STOP │
32	│ 5. UPDATE PLAN │ Check off tasks, update status in plan file │
33	│ ↓ │ ⚠️ THIS HAPPENS AFTER EVERY PHASE │
34	│ 6. COMMIT MSG │ Generate conventional commit (NEVER git ops) │
35	│ ↓ │ User handles all git operations │
36	│ 7. FUNCTIONAL TEST│ Explain how to test. Offer integration script │
37	│ ↓ │ NEVER auto-create scripts. ALWAYS ask first │
38	│ 8. STOP │ Full stop. Suggest compact. Wait for user. │
39	│ │ OVERRIDE: --build-all flag continues │
40	│ │
41	│ ════════════════════════════════════════════════════════════════ │
42	│ Steps 3-8 repeat for EACH PHASE. Plan updates after EVERY phase. │
43	│ ════════════════════════════════════════════════════════════════ │
44	│ │
45	└─────────────────────────────────────────────────────────────────────┘
46	```
47
48	## Step 1: Ingest Plan
49
50	REQUIRED: Plan document must be provided.
51
52	```
53	I'll help you execute your implementation plan.
54
55	Please provide the plan document:
56	1. Path to plan file (e.g., docs/feature-plan.md)
57	2. Paste the plan content directly
58
59	Which would you prefer?
60	```
61
62	If no plan provided after asking: EXIT immediately.
63
64	```
65	I cannot execute without a plan document.
66
67	To create a plan, use the `superplan` skill first:
68	/superplan
69
70	Then come back with the completed plan.
71
72	[EXIT - No further action]
73	```
74
75	NO EXCEPTIONS. Do not improvise. Do not create plans on the fly. Do not proceed without a plan document.
76
77	## Step 2: Read All Phases
78
79	After ingesting the plan:
80
81	1. Output all phases with their estimates and dependencies
82	2. Check context usage - if high, suggest compacting first
83
84	```
85	PLAN LOADED: [Feature Name]
86	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
87
88	\| Phase \| Name \| Est. \| Depends On \| Parallel With \| Status \|
89	\|-------\|------\|------\|------------\|---------------\|--------\|
90	\| 0 \| Bootstrap \| 5 \| - \| - \| ⬜ \|
91	\| 1 \| Setup \| 3 \| 0 \| - \| ⬜ \|
92	\| 2A \| Backend \| 8 \| 1 \| 2B, 2C \| ⬜ \|
93	\| 2B \| Frontend \| 5 \| 1 \| 2A, 2C \| ⬜ \|
94	\| 2C \| Tests \| 3 \| 1 \| 2A, 2B \| ⬜ \|
95	\| 3 \| Integration \| 5 \| 2A,2B,2C \| - \| ⬜ \|
96
97	Total: 29 points \| Parallel phases: 2A, 2B, 2C
98
99	⚠️ Context Usage Advisory
100	If context is high, consider compacting before continuing.
101	Large plans consume significant context per phase.
102
103	Ready to execute Phase 0?
104	```
105
106	## Step 3: Execute Phase
107
108	### Sequential Phases
109
110	Execute one at a time. Do not proceed to next phase until current is COMPLETE.
111
112	### Parallel Phases
113
114	For phases marked "Parallel With", MUST use sub-agents or parallel Task tool calls.
115
116	```
117	EXECUTING PARALLEL PHASES: 2A, 2B, 2C
118	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
119
120	Launching 3 parallel sub-agents...
121
122	[Sub-agent 2A: Backend implementation]
123	[Sub-agent 2B: Frontend implementation]
124	[Sub-agent 2C: Test implementation]
125
126	Each sub-agent MUST return:
127	- Implementatio

People who liked this also viewed

6 picks

Type