ai-engineering-loop 1.14.0 → 1.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (112) hide show
  1. package/.agents/{workflows/ai-engineering-loop.md → skills/ai-engineering-loop/SKILL.md} +9 -7
  2. package/{.gemini → .agents}/skills/ai-engineering-loop/references/loop-deliver.md +1 -0
  3. package/.agents/skills/ai-engineering-loop/references/loop-hosts.md +48 -0
  4. package/.agents/skills/ai-engineering-loop/references/loop-maker.md +13 -0
  5. package/{.gemini → .agents}/skills/ai-engineering-loop/references/loop-review.md +2 -0
  6. package/.claude/skills/ai-engineering-loop/SKILL.md +10 -11
  7. package/.claude/skills/ai-engineering-loop/references/loop-deliver.md +1 -0
  8. package/.claude/skills/ai-engineering-loop/references/loop-hosts.md +48 -0
  9. package/.claude/skills/ai-engineering-loop/references/loop-maker.md +6 -1
  10. package/.claude/skills/ai-engineering-loop/references/loop-review.md +2 -0
  11. package/CHANGELOG.md +83 -0
  12. package/README.md +54 -6
  13. package/adapters/README.md +22 -0
  14. package/adapters/dot/README.md +19 -9
  15. package/adapters/dot/gitlab.md +49 -0
  16. package/adapters/dot/mattermost.md +10 -0
  17. package/adapters/dot/skills/dot-dev-workflow/SKILL.md +27 -5
  18. package/adapters/dot/sonar.md +90 -0
  19. package/adapters/generate-adapter/SKILL.md +6 -5
  20. package/adapters/{dot → quality}/skills/task-impact-inquiry/SKILL.md +10 -7
  21. package/agents/instruction-only/AGENTS.md +24 -0
  22. package/bin/ai-engineering-loop.js +320 -34
  23. package/core/grill-policy.md +1 -1
  24. package/core/orchestration-model.md +11 -0
  25. package/core/runtime-safety.md +2 -1
  26. package/lib/adapter-check.js +102 -0
  27. package/lib/adapter-detect.js +125 -0
  28. package/lib/auto-update.js +3 -1
  29. package/lib/cli-args.js +11 -0
  30. package/lib/doctor.js +13 -17
  31. package/lib/gates.js +28 -1
  32. package/lib/generate-adapter.js +6 -30
  33. package/lib/host-skill-build.js +25 -15
  34. package/lib/hosts/agent-formats.js +135 -0
  35. package/lib/hosts/commands.js +126 -0
  36. package/lib/hosts/detect.js +56 -0
  37. package/lib/hosts/doctor.js +77 -0
  38. package/lib/hosts/redetect.js +60 -0
  39. package/lib/hosts/registry.js +298 -0
  40. package/lib/hosts/table.js +43 -0
  41. package/lib/orchestration.js +39 -6
  42. package/lib/run-abandon.js +116 -0
  43. package/lib/studio-server.js +1 -0
  44. package/lib/sync-hosts.js +156 -112
  45. package/package.json +2 -3
  46. package/schemas/report.schema.json +52 -5
  47. package/.agents/devil-advocate.md +0 -79
  48. package/.agents/judge.md +0 -58
  49. package/.claude/commands/ai-engineering-loop.md +0 -11
  50. package/.gemini/skills/ai-engineering-loop/SKILL.md +0 -61
  51. package/.gemini/skills/ai-engineering-loop/references/loop-maker.md +0 -8
  52. package/.gemini/skills/animate/RECIPES.md +0 -324
  53. package/.gemini/skills/animate/SKILL.md +0 -207
  54. package/.gemini/skills/animate-expo/RECIPES.md +0 -385
  55. package/.gemini/skills/animate-expo/SKILL.md +0 -263
  56. package/.gemini/skills/animation-vocabulary/SKILL.md +0 -181
  57. package/.gemini/skills/apple-design/SKILL.md +0 -290
  58. package/.gemini/skills/ask-sonner/API.md +0 -64
  59. package/.gemini/skills/ask-sonner/SKILL.md +0 -88
  60. package/.gemini/skills/backend-development/SKILL.md +0 -272
  61. package/.gemini/skills/backend-development/references/api-design-guidelines.md +0 -95
  62. package/.gemini/skills/backend-development/references/query-and-database-best-practices.md +0 -53
  63. package/.gemini/skills/backend-development/references/security-checklist.md +0 -60
  64. package/.gemini/skills/emil-design-eng/SKILL.md +0 -674
  65. package/.gemini/skills/find-animation-opportunities/SKILL.md +0 -140
  66. package/.gemini/skills/improve-animations/AUDIT.md +0 -115
  67. package/.gemini/skills/improve-animations/PLAN-TEMPLATE.md +0 -73
  68. package/.gemini/skills/improve-animations/SKILL.md +0 -109
  69. package/.gemini/skills/mobile-native/SKILL.md +0 -311
  70. package/.gemini/skills/pick-ui-library/SKILL.md +0 -85
  71. package/.gemini/skills/prototype/PICKER.md +0 -197
  72. package/.gemini/skills/prototype/SKILL.md +0 -98
  73. package/.gemini/skills/review-animations/SKILL.md +0 -120
  74. package/.gemini/skills/review-animations/STANDARDS.md +0 -187
  75. package/.gemini/skills/write-swift/SKILL.md +0 -396
  76. package/.grok/commands/ai-engineering-loop.md +0 -11
  77. package/.grok/skills/ai-engineering-loop/SKILL.md +0 -62
  78. package/.grok/skills/ai-engineering-loop/references/loop-commands.md +0 -20
  79. package/.grok/skills/ai-engineering-loop/references/loop-deliver.md +0 -8
  80. package/.grok/skills/ai-engineering-loop/references/loop-goal.md +0 -10
  81. package/.grok/skills/ai-engineering-loop/references/loop-maker.md +0 -8
  82. package/.grok/skills/ai-engineering-loop/references/loop-review.md +0 -18
  83. package/.grok/skills/ai-engineering-loop/references/loop-risky.md +0 -9
  84. package/.grok/skills/ai-engineering-loop/references/loop-verify.md +0 -20
  85. package/.grok/skills/animate/RECIPES.md +0 -324
  86. package/.grok/skills/animate/SKILL.md +0 -207
  87. package/.grok/skills/animate-expo/RECIPES.md +0 -385
  88. package/.grok/skills/animate-expo/SKILL.md +0 -263
  89. package/.grok/skills/animation-vocabulary/SKILL.md +0 -181
  90. package/.grok/skills/apple-design/SKILL.md +0 -290
  91. package/.grok/skills/ask-sonner/API.md +0 -64
  92. package/.grok/skills/ask-sonner/SKILL.md +0 -88
  93. package/.grok/skills/backend-development/SKILL.md +0 -272
  94. package/.grok/skills/backend-development/references/api-design-guidelines.md +0 -95
  95. package/.grok/skills/backend-development/references/query-and-database-best-practices.md +0 -53
  96. package/.grok/skills/backend-development/references/security-checklist.md +0 -60
  97. package/.grok/skills/emil-design-eng/SKILL.md +0 -674
  98. package/.grok/skills/find-animation-opportunities/SKILL.md +0 -140
  99. package/.grok/skills/improve-animations/AUDIT.md +0 -115
  100. package/.grok/skills/improve-animations/PLAN-TEMPLATE.md +0 -73
  101. package/.grok/skills/improve-animations/SKILL.md +0 -109
  102. package/.grok/skills/mobile-native/SKILL.md +0 -311
  103. package/.grok/skills/pick-ui-library/SKILL.md +0 -85
  104. package/.grok/skills/prototype/PICKER.md +0 -197
  105. package/.grok/skills/prototype/SKILL.md +0 -98
  106. package/.grok/skills/review-animations/SKILL.md +0 -120
  107. package/.grok/skills/review-animations/STANDARDS.md +0 -187
  108. package/.grok/skills/write-swift/SKILL.md +0 -396
  109. /package/{.gemini → .agents}/skills/ai-engineering-loop/references/loop-commands.md +0 -0
  110. /package/{.gemini → .agents}/skills/ai-engineering-loop/references/loop-goal.md +0 -0
  111. /package/{.gemini → .agents}/skills/ai-engineering-loop/references/loop-risky.md +0 -0
  112. /package/{.gemini → .agents}/skills/ai-engineering-loop/references/loop-verify.md +0 -0
@@ -20,6 +20,9 @@ flowchart TD
20
20
 
21
21
  PushBranch --> CreateMR[Create Merge Request via glab]
22
22
  CreateMR --> CaptureMR[Capture MR URL & ID for Multi-Branch / Bot Triage]
23
+ CaptureMR --> Gate[Pipeline + Sonar gate: sonar.md]
24
+ Gate --> Triage[Coreview triage: coreview.md]
25
+ Triage --> Ready[Move card to Ready to review: Step 4]
23
26
  ```
24
27
 
25
28
  ---
@@ -150,3 +153,49 @@ glab mr create \
150
153
  ## Note for Deployment
151
154
  - No manual database migrations required. (or specify migration command if applicable)
152
155
  ```
156
+
157
+ ---
158
+
159
+ ## 6. Step 4: Move the Card to "Ready to review"
160
+
161
+ Run this only when all three hold:
162
+
163
+ 1. The MR pipeline passed and the Sonar gate is PASS or SKIPPED ([`sonar.md`](sonar.md)).
164
+ 2. The Coreview triage report is printed ([`coreview.md`](coreview.md)).
165
+ 3. An issue is linked to this MR (Step 2).
166
+
167
+ If the Sonar gate is FAIL, stop here. Do not move the card, and do not notify.
168
+
169
+ ### A. No card linked: skip cleanly
170
+
171
+ If Step 2 found no issue and none was created (for example, the tracker is not this repo and the user did not name one), print `Card: none linked (skipped)` and continue to Mattermost. Do not create an issue just to move it.
172
+
173
+ ### B. Read the board lists and the card's current labels
174
+
175
+ GitLab board columns are labels. Find the label of the "Ready to review" list and of every other list:
176
+
177
+ ```bash
178
+ glab api "projects/:fullpath/boards" # lists[].label.name per board
179
+ glab api "projects/:fullpath/issues/<issue-iid>" # labels[] on the card
180
+ ```
181
+
182
+ The target label is the list label whose name equals `Ready to review` (case-insensitive). If `.ai-engineering-loop/adapter.md` names `board_ready_label`, use that instead. No such list on any board: print `Card: no "Ready to review" list (skipped)` and continue.
183
+
184
+ ### C. Move it (idempotent)
185
+
186
+ - The card already has the target label and no other list label: print `Card: already in Ready to review` and do nothing.
187
+ - Otherwise add the target label and remove only the **other board-list labels** currently on the card. Leave every non-list label alone.
188
+
189
+ ```bash
190
+ glab issue update <issue-iid> --repo <repo> \
191
+ --label "Ready to review" \
192
+ --unlabel "<other list label currently on the card>"
193
+ ```
194
+
195
+ Re-read the issue and print:
196
+
197
+ ```text
198
+ Card: #<issue-iid> -> Ready to review (removed: <labels or none>)
199
+ ```
200
+
201
+ Running Step 4 twice must not change anything the second time.
@@ -8,6 +8,16 @@ This gives QA, product, and reviewers visibility when the delivery pipeline fini
8
8
 
9
9
  ---
10
10
 
11
+ ## 2. Preconditions (gate)
12
+
13
+ Send only after all of these are printed in the conversation:
14
+
15
+ 1. Sonar Gate report with `Quality gate: PASS` or `SKIPPED` ([`sonar.md`](sonar.md)). On `FAIL`, do not send.
16
+ 2. Phase 8 Triage report ([`coreview.md`](coreview.md)).
17
+ 3. Card line from [`gitlab.md`](gitlab.md) Step 4 (`-> Ready to review`, `already in Ready to review`, or `skipped`).
18
+
19
+ ---
20
+
11
21
  ## 2. Channel Resolution & Dispatch Flow
12
22
 
13
23
  ```text
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: dot-dev-workflow
3
- description: DOT Stage 8 delivery after AI Engineering Loop Judge PASS. GitLab issue/MR, one topic-branch MR (extra env cherry-pick only if named this turn), Coreview triage, Mattermost. Not a substitute for ai-engineering-loop.
3
+ description: DOT Stage 8 delivery after AI Engineering Loop Judge PASS. GitLab issue/MR, one topic-branch MR (extra env cherry-pick only if named this turn), pipeline + Sonar gate, Coreview triage, card to Ready to review, Mattermost. Not a substitute for ai-engineering-loop.
4
4
  ---
5
5
 
6
6
  # DOT Delivery Workflow (Stage 8)
@@ -22,7 +22,7 @@ If `ai-engineering-loop` is missing on this host, say so and stop. Do not silent
22
22
  | Phase 2 impact inquiry | AEL Stage 1 grill + `task-impact-inquiry` |
23
23
  | Phase 3-5 code / tests / tsc | AEL Stages 4-5 (`policies/tdd-policy.md`, `.ai-engineering-loop/verification.md`) |
24
24
  | Phase 6 `devils-advocate` | AEL Stages 6-7 (Finding Ledger + Judge PASS/ITERATE/ESCALATE) |
25
- | Phase 7-9 glab / Coreview / Mattermost | **This skill** (AEL Stage 8). Prefer `adapters/dot/` in the AEL package when present. |
25
+ | Phase 7-9 glab / Sonar / Coreview / board / Mattermost | **This skill** (AEL Stage 8). Prefer `adapters/dot/` in the AEL package when present. |
26
26
 
27
27
  `git commit`, `git push`, and `glab mr create` are forbidden until Judge `PASS`.
28
28
 
@@ -63,7 +63,23 @@ git commit -m "<type>(<scope>): <summary>"
63
63
 
64
64
  ---
65
65
 
66
- ## Stage 8b — Coreview and MR discussions
66
+ ## Stage 8b — Pipeline and Sonar gate
67
+
68
+ Follow `adapters/dot/sonar.md` when present. Wait for the MR pipeline, then read the Sonar quality gate from the pipeline's Sonar job (`glab ci trace <job-id>`) or the Sonar MR comment (`glab mr view <id> --comments`). Print:
69
+
70
+ ```text
71
+ Sonar Gate
72
+ MR: !<id>
73
+ Pipeline: #<id> <passed|failed>
74
+ Quality gate: <PASS | FAIL | SKIPPED>
75
+ Action: <none | fix>
76
+ ```
77
+
78
+ FAIL: fix on the same topic MR, re-verify, push, wait for the new pipeline. While FAIL, do not move the card and do not send Mattermost. No Sonar on the project is `SKIPPED`, never PASS. Use `glab` only; no tokens in prompts.
79
+
80
+ ---
81
+
82
+ ## Stage 8c — Coreview and MR discussions
67
83
 
68
84
  Follow `adapters/dot/coreview.md` when present, plus `gitlab-mr-feedback` and `receiving-code-review`.
69
85
 
@@ -91,9 +107,15 @@ glab api "projects/:fullpath/merge_requests/<mr-id>/discussions/<discussion_id>/
91
107
 
92
108
  ---
93
109
 
94
- ## Stage 8c — Mattermost (`no-ai-slop`)
110
+ ## Stage 8d — Card to "Ready to review"
111
+
112
+ Follow `adapters/dot/gitlab.md` Step 4 when present. Only after Sonar PASS/SKIPPED and the printed triage. No linked card: print `Card: none linked (skipped)`. Otherwise add the `Ready to review` list label and remove only other board-list labels (`glab issue update <iid> --label "Ready to review" --unlabel "<old list label>"`). Already there: change nothing.
113
+
114
+ ---
115
+
116
+ ## Stage 8e — Mattermost (`no-ai-slop`)
95
117
 
96
- Follow `adapters/dot/mattermost.md` when present.
118
+ Follow `adapters/dot/mattermost.md` when present. Send only after the Sonar Gate (PASS/SKIPPED), triage, and card lines are printed.
97
119
 
98
120
  1. Resolve channel and PIC from `~/.gemini/config/mattermost-channel-mapping.json`. If PIC is missing, ask the user and save it.
99
121
  2. Send via MCP `mattermost_send_message` with `from: "AI Agent"`. Use the Mattermost CLI only if MCP fails. Do not send twice.
@@ -0,0 +1,90 @@
1
+ # DOT Adapter: Pipeline and Sonar Quality Gate
2
+
3
+ ## 1. Purpose
4
+
5
+ After the MR exists, the MR pipeline and its Sonar quality gate must pass **before** Coreview triage closes, the card moves to "Ready to review", or Mattermost is sent. A green unit-test run on your machine is not a passed quality gate.
6
+
7
+ Use `glab` only. Do not paste tokens, Sonar URLs with tokens, or `SONAR_TOKEN` into prompts, commands, or notes.
8
+
9
+ ---
10
+
11
+ ## 2. Flow
12
+
13
+ ```text
14
+ MR created (gitlab.md Step 3)
15
+ -> wait for the MR pipeline to finish
16
+ -> pipeline failed -> FAIL (fix, push, wait again)
17
+ -> pipeline passed
18
+ -> Sonar result found -> PASS | FAIL
19
+ -> no Sonar on this repo -> SKIPPED (say so; not PASS)
20
+ -> FAIL: do not move the card, do not notify; loop back
21
+ -> PASS or SKIPPED: continue to coreview.md
22
+ ```
23
+
24
+ ---
25
+
26
+ ## 3. Step 1: Wait for the MR pipeline
27
+
28
+ ```bash
29
+ glab ci status --branch <branch-name> --repo <repo>
30
+ glab ci view <branch-name> --repo <repo> # interactive, optional
31
+ glab api "projects/:fullpath/merge_requests/<mr-iid>/pipelines"
32
+ ```
33
+
34
+ Take the newest pipeline for the MR's head commit. `running` / `pending`: wait and check again. Do not report the gate while the pipeline is still running.
35
+
36
+ ---
37
+
38
+ ## 4. Step 2: Read the Sonar quality gate
39
+
40
+ Check both sources. Use whichever the project has.
41
+
42
+ **A. Sonar job in the pipeline** (for example `sonarqube-check`, `sonar`, any job whose name contains `sonar`):
43
+
44
+ ```bash
45
+ glab api "projects/:fullpath/pipelines/<pipeline-id>/jobs"
46
+ glab ci trace <job-id> --repo <repo>
47
+ ```
48
+
49
+ `failed` job, or a log line like `QUALITY GATE STATUS: FAILED` → FAIL. `success` with `QUALITY GATE STATUS: PASSED` → PASS.
50
+
51
+ **B. Sonar comment on the MR** (Sonar's MR decoration bot):
52
+
53
+ ```bash
54
+ glab mr view <mr-iid> --comments --repo <repo>
55
+ ```
56
+
57
+ The newest Sonar note for the current head commit decides: "Quality Gate passed" → PASS, "Quality Gate failed" → FAIL. An older note for an earlier commit does not count.
58
+
59
+ Neither source present → `SKIPPED (no Sonar on this project)`. Do not invent a PASS.
60
+
61
+ ---
62
+
63
+ ## 5. Step 3: Print the gate report (mandatory)
64
+
65
+ ```text
66
+ Sonar Gate
67
+ MR: !<mr-iid>
68
+ Pipeline: #<pipeline-id> <passed|failed>
69
+ Source: <job <name> | MR comment | none>
70
+ Quality gate: <PASS | FAIL | SKIPPED>
71
+ New issues: <n or list, from the job log / comment>
72
+ Coverage on new code: <value or n/a>
73
+ Action: <none | fix>
74
+ ```
75
+
76
+ ---
77
+
78
+ ## 6. On FAIL: loop back
79
+
80
+ 1. List the new issues and the coverage gap from the job log or comment, with file paths.
81
+ 2. Fix surgically on the same topic branch. Re-run the commands in `.ai-engineering-loop/verification.md`.
82
+ 3. Commit and push to the same MR. Do not cherry-pick unless the user named extra envs this turn.
83
+ 4. Go back to Step 1 and wait for the new pipeline.
84
+
85
+ While the gate is FAIL:
86
+
87
+ - Do **not** move the card to "Ready to review" (`gitlab.md` Step 4).
88
+ - Do **not** send Mattermost (`mattermost.md`).
89
+
90
+ If the fix would change the frozen Goal Contract's behavior, stop and ask the user. Do not widen scope to make Sonar green.
@@ -50,12 +50,13 @@ Or run `npx ai-engineering-loop generate-adapter` and use its detected block.
50
50
 
51
51
  Cite the remote host. Do not ask what git already shows.
52
52
 
53
- Recommended type:
53
+ Recommended type (same rules as `init` and Studio; the CLI prints the reason):
54
54
 
55
- - `github.com` → `github`
56
- - GitLab host that is not a named company adapter → `gitlab`
57
- - no remote / unknown → `standard`
58
- - user said they need the DOT pipeline → `dot` (load `adapters/dot/`, do not invent extra tools)
55
+ 1. `origin` remote host (else the first remote): DOT GitLab host → `dot`, `github.com` → `github`, any other host with `gitlab` in it → `gitlab`
56
+ 2. unknown or no remote: `.github/workflows/` → `github`, `.gitlab-ci.yml` → `gitlab`
57
+ 3. otherwise → `standard`
58
+
59
+ Do not downgrade a `dot` recommendation to `gitlab`. `dot` loads `adapters/dot/`; do not invent extra tools.
59
60
 
60
61
  ### 2. Grill (wait)
61
62
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: task-impact-inquiry
3
- description: Map business blast radius before code. Use for impact, side effects, sibling data, approval, queues, or when a new developer must learn the current flow. Triggers: cek impactnya, blast radius, analisa pengaruh, brainstorming impact. Not a substitute for ai-engineering-loop.
3
+ description: Map business blast radius before code. Use for impact, side effects, sibling data, approval, queues, or when a new developer must learn the current flow. Triggers (EN/ID): check the impact, impact analysis, blast radius, side effects, cek impactnya, analisa pengaruh. Not a substitute for ai-engineering-loop.
4
4
  ---
5
5
 
6
6
  # Task Impact Inquiry
@@ -9,7 +9,9 @@ Map the **current business flow** and the **blast radius** of a change before an
9
9
 
10
10
  This skill fills AI Engineering Loop Stage 1 grill. It is not a parallel engineering OS.
11
11
 
12
- If Stage 1 grill already produced this matrix and the user confirmed it, stop. Do not interview again. On commit-bound work, continue in `ai-engineering-loop` (freeze the Goal Contract, then Maker). Do not start `dot-dev-workflow` Phases 1-6.
12
+ If Stage 1 grill already produced this matrix and the user confirmed it, stop. Do not interview again. On commit-bound work, continue in `ai-engineering-loop` (freeze the Goal Contract, then Maker). Do not start a second engineering loop from your team's own workflow skill.
13
+
14
+ Works on any adapter. On `adapter_type: dot` it is mandatory in Stage 1; the DOT-only rules live in `adapters/dot/README.md`.
13
15
 
14
16
  ## Hard gate
15
17
 
@@ -23,7 +25,8 @@ Green unit tests later are not proof that siblings, approvals, or downstream job
23
25
 
24
26
  ## When to use
25
27
 
26
- - "cek impactnya", "blast radius", "analisa pengaruh", "brainstorming impact"
28
+ - "check the impact", "impact analysis", "blast radius", "side effects"
29
+ - Indonesian: "cek impactnya", "analisa pengaruh", "brainstorming impact"
27
30
  - Bug, edge case, or business-logic change
28
31
  - Shared service, status transition, calculation, validation, authorization, schema
29
32
  - The user is new to the domain and does not know the flow
@@ -47,8 +50,8 @@ Look up facts (files, enums, jobs). Grill only **decisions**.
47
50
  Read in this order. Skip a source if it is missing. Do not invent statuses.
48
51
 
49
52
  1. `.ai-engineering-loop/glossary.md`
50
- 2. Existing FSD if present (`docs/fsd/`, `specs-book/fsd/`, especially `impact-matrix.md`). Read only. Do not generate an FSD.
51
- 3. Status enums, services, validators, listeners, BullMQ / cron / queue processors
53
+ 2. Existing functional spec (FSD/PRD) if present (`docs/fsd/`, `specs-book/fsd/`, especially `impact-matrix.md`). Read only. Do not generate an FSD.
54
+ 3. Status enums, services, validators, listeners, queue / cron / job processors
52
55
  4. Matching FE pages, routes, and permission guards when both FE and BE are in the workspace
53
56
 
54
57
  Cite the path for each claim. If FE or BE is missing, say so.
@@ -76,7 +79,7 @@ If the flow cannot be determined from the repo, say what is missing.
76
79
 
77
80
  **Actor and approval.** Who creates, who may edit, who must re-approve? When is an existing approval void, and when must it be kept?
78
81
 
79
- **Downstream.** BullMQ, cron, listeners, billing, dashboard totals.
82
+ **Downstream.** Queues, cron, listeners, billing, dashboard totals.
80
83
 
81
84
  ### 4. Where it hits (hit map + blast picture)
82
85
 
@@ -152,4 +155,4 @@ Next: freeze Goal Contract | stop (impact-only)
152
155
  - Mermaid or LaTeX
153
156
  - Claiming isolation because unit tests passed
154
157
  - Inventing business rules the repo and the user did not supply
155
- - Generating an FSD or starting `dot-dev-workflow` as a second loop
158
+ - Generating an FSD or starting another workflow skill as a second loop
@@ -0,0 +1,24 @@
1
+ <!-- Generated from skill-src/ by npm run build:skills; do not edit. -->
2
+ # AI Engineering Loop (digest)
3
+
4
+ For hosts with no subagent tool (certification `instruction-only`). Full skill: `~/.agents/skills/ai-engineering-loop/SKILL.md` after `sync-hosts`. Stage details: `npx ai-engineering-loop docs loop-<goal|maker|verify|review|deliver>`.
5
+
6
+ Loop: Specify (0-1), Make (2-4), Review (5-7), Deliver (8). You are Maker. Devil's Advocate (DA) and Judge run in this session as `CONTEXT_ISOLATION_ONLY`, with the same budgets; never claim independent review.
7
+
8
+ 1. `npx ai-engineering-loop run --json` gives runId, tier, budget. Read `.ai-engineering-loop/glossary.md`.
9
+ 2. Goal Contract: AC is a failure table (happy, empty, boundary, error). Only after the human freezes: `goal freeze --latest --run <runId> --by human`. Chat agreement is not freeze.
10
+ 3. Maker: one red test per AC row before the fix, then `gate maker`.
11
+ 4. `verify --cmd <test command>`, then write claimed-vs-reality.md.
12
+ 5. DA: re-read only the diff, Goal, and evidence; log findings; `gate review`. Judge: write the verdict from the evidence, then `gate judge`. ITERATE at most 3 times.
13
+ 6. Deliver per `.ai-engineering-loop/adapter.md`. ASSISTED: `deliver --approve --by <human>` only after the human says so.
14
+
15
+ Never: edit `state.json`/`current.json`, skip a gate, infer approval, invent usage counts, or put secrets in messages. A gate failure overrides prose.
16
+
17
+ Report header:
18
+
19
+ ```
20
+ Execution Mode: CONTEXT_ISOLATION_ONLY
21
+ Independent LLM Execution: NOT PROVEN
22
+ Native Subagent Invocation: UNAVAILABLE
23
+ Review Method: Clean-Slate Artifact Isolation Barrier
24
+ ```