@chankov/agent-fleet 0.0.11 → 1.0.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 (494) hide show
  1. package/.pi/extensions/agent-fleet-update-check/README.md +4 -4
  2. package/.pi/extensions/btw/README.md +26 -25
  3. package/.pi/extensions/btw/index.ts +80 -83
  4. package/.pi/extensions/pi-voice-stt/README.md +4 -3
  5. package/.pi/extensions/pi-voice-stt/config.ts +1 -1
  6. package/.pi/harnesses/agent-hub/README.md +106 -54
  7. package/.pi/harnesses/agent-hub/backend-policy.js +25 -4
  8. package/.pi/harnesses/agent-hub/footer.ts +4 -0
  9. package/.pi/harnesses/agent-hub/helpers.ts +18 -0
  10. package/.pi/harnesses/agent-hub/index.ts +537 -369
  11. package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +10 -1
  12. package/.pi/harnesses/agent-hub/package.json +1 -1
  13. package/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  14. package/.pi/harnesses/agent-hub/posture.ts +103 -0
  15. package/.pi/harnesses/ask-user-remote/README.md +37 -3
  16. package/.pi/harnesses/ask-user-remote/index.ts +173 -17
  17. package/.pi/harnesses/coms/package.json +1 -1
  18. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  19. package/.pi/harnesses/lib/fleet-dashboard-ops.ts +118 -0
  20. package/.pi/harnesses/lib/fleet-dashboard-view.ts +140 -0
  21. package/.pi/harnesses/lib/fleet-detail-view.ts +43 -0
  22. package/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  23. package/.pi/harnesses/lib/fleet-panel.ts +34 -0
  24. package/.pi/harnesses/lib/fleet-read-model.ts +131 -0
  25. package/.pi/harnesses/lib/fleet-selection.ts +24 -0
  26. package/.pi/harnesses/package-lock.json +2011 -0
  27. package/.pi/harnesses/package.json +1 -0
  28. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/README.md +4 -4
  29. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/README.md +4 -3
  30. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/config.ts +1 -1
  31. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-session-bridge.ts +10 -1
  32. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/README.md +37 -3
  33. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/index.ts +173 -17
  34. package/.versions/0.0.11/.pi/harnesses/package-lock.json +2011 -0
  35. package/.versions/0.0.11/.pi/harnesses/package.json +1 -0
  36. package/.versions/0.0.11/docs/ARCHITECTURE.md +6 -8
  37. package/.versions/0.0.11/docs/agent-fleet-setup.md +17 -43
  38. package/.versions/0.0.11/docs/claude-code-coms-bridge.md +20 -2
  39. package/.versions/0.0.11/docs/coms-hermes-bridge.md +1 -1
  40. package/.versions/0.0.11/docs/getting-started.md +26 -237
  41. package/.versions/0.0.11/docs/npm-install.md +60 -478
  42. package/.versions/0.0.11/docs/pi-extensions.md +4 -4
  43. package/.versions/0.0.11/docs/pi-setup.md +37 -551
  44. package/.versions/0.0.11/hermes/README.md +1 -1
  45. package/.versions/0.0.11/install-manifest.json +375 -1247
  46. package/.versions/0.0.11/justfile +13 -6
  47. package/.versions/0.0.11/manifest-meta.json +543 -134
  48. package/.versions/0.0.11/scripts/lib/fleet-command.ts +8 -0
  49. package/.versions/0.0.11/scripts/lib/monitor-env.ts +18 -6
  50. package/.versions/0.0.11/skills/designing-agents/SKILL.md +1 -1
  51. package/.versions/0.0.11/skills/designing-agents/pi-harness-authoring.md +1 -1
  52. package/.versions/1.0.0/.pi/agents/dispatch-policy.yaml +32 -0
  53. package/.versions/1.0.0/.pi/agents/model-profiles.yaml +27 -0
  54. package/.versions/1.0.0/.pi/agents/peers.yaml +142 -0
  55. package/.versions/1.0.0/.pi/agents/teams.yaml +41 -0
  56. package/.versions/1.0.0/.pi/damage-control-rules.yaml +297 -0
  57. package/.versions/1.0.0/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  58. package/.versions/1.0.0/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  59. package/.versions/1.0.0/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  60. package/.versions/1.0.0/.pi/extensions/btw/README.md +120 -0
  61. package/.versions/1.0.0/.pi/extensions/btw/index.ts +914 -0
  62. package/.versions/1.0.0/.pi/extensions/btw/package.json +6 -0
  63. package/.versions/1.0.0/.pi/extensions/btw/state.js +179 -0
  64. package/.versions/1.0.0/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  65. package/.versions/1.0.0/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  66. package/.versions/1.0.0/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  67. package/.versions/1.0.0/.pi/extensions/compact-and-continue/README.md +42 -0
  68. package/.versions/1.0.0/.pi/extensions/compact-and-continue/index.ts +120 -0
  69. package/.versions/1.0.0/.pi/extensions/compact-and-continue/package.json +6 -0
  70. package/.versions/1.0.0/.pi/extensions/mcp-bridge/README.md +46 -0
  71. package/.versions/1.0.0/.pi/extensions/mcp-bridge/index.ts +206 -0
  72. package/.versions/1.0.0/.pi/extensions/mcp-bridge/package.json +6 -0
  73. package/.versions/1.0.0/.pi/extensions/package-lock.json +1143 -0
  74. package/.versions/1.0.0/.pi/extensions/package.json +9 -0
  75. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/README.md +205 -0
  76. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/config.ts +198 -0
  77. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  78. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/index.ts +248 -0
  79. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/package.json +6 -0
  80. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  81. package/.versions/1.0.0/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  82. package/.versions/1.0.0/.pi/harnesses/agent-hub/README.md +1056 -0
  83. package/.versions/1.0.0/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  84. package/.versions/1.0.0/.pi/harnesses/agent-hub/artifacts.js +146 -0
  85. package/.versions/1.0.0/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  86. package/.versions/1.0.0/.pi/harnesses/agent-hub/backend-policy.js +174 -0
  87. package/.versions/1.0.0/.pi/harnesses/agent-hub/context-window.js +106 -0
  88. package/.versions/1.0.0/.pi/harnesses/agent-hub/delegate.ts +435 -0
  89. package/.versions/1.0.0/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  90. package/.versions/1.0.0/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  91. package/.versions/1.0.0/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  92. package/.versions/1.0.0/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  93. package/.versions/1.0.0/.pi/harnesses/agent-hub/footer.ts +35 -0
  94. package/.versions/1.0.0/.pi/harnesses/agent-hub/helpers.ts +266 -0
  95. package/.versions/1.0.0/.pi/harnesses/agent-hub/index.ts +9279 -0
  96. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  97. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  98. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  99. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  100. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  101. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  102. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  103. package/.versions/1.0.0/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
  104. package/.versions/1.0.0/.pi/harnesses/agent-hub/package.json +7 -0
  105. package/.versions/1.0.0/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  106. package/.versions/1.0.0/.pi/harnesses/agent-hub/posture.ts +103 -0
  107. package/.versions/1.0.0/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  108. package/.versions/1.0.0/.pi/harnesses/agent-hub/research-retention.js +34 -0
  109. package/.versions/1.0.0/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  110. package/.versions/1.0.0/.pi/harnesses/agent-hub/return-contract.js +293 -0
  111. package/.versions/1.0.0/.pi/harnesses/agent-hub/return-extract.js +75 -0
  112. package/.versions/1.0.0/.pi/harnesses/agent-hub/review-findings.js +102 -0
  113. package/.versions/1.0.0/.pi/harnesses/agent-hub/run-budget.js +479 -0
  114. package/.versions/1.0.0/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  115. package/.versions/1.0.0/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  116. package/.versions/1.0.0/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  117. package/.versions/1.0.0/.pi/harnesses/agent-hub/session-health.js +110 -0
  118. package/.versions/1.0.0/.pi/harnesses/agent-hub/spawn.ts +354 -0
  119. package/.versions/1.0.0/.pi/harnesses/agent-hub/version.ts +42 -0
  120. package/.versions/1.0.0/.pi/harnesses/ask-user-remote/README.md +53 -0
  121. package/.versions/1.0.0/.pi/harnesses/ask-user-remote/index.ts +477 -0
  122. package/.versions/1.0.0/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  123. package/.versions/1.0.0/.pi/harnesses/coms/README.md +100 -0
  124. package/.versions/1.0.0/.pi/harnesses/coms/index.ts +1767 -0
  125. package/.versions/1.0.0/.pi/harnesses/coms/package.json +7 -0
  126. package/.versions/1.0.0/.pi/harnesses/coms/version.ts +42 -0
  127. package/.versions/1.0.0/.pi/harnesses/damage-control-continue/README.md +124 -0
  128. package/.versions/1.0.0/.pi/harnesses/damage-control-continue/index.ts +536 -0
  129. package/.versions/1.0.0/.pi/harnesses/damage-control-continue/package.json +7 -0
  130. package/.versions/1.0.0/.pi/harnesses/damage-control-continue/version.ts +42 -0
  131. package/.versions/1.0.0/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  132. package/.versions/1.0.0/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  133. package/.versions/1.0.0/.pi/harnesses/lib/fleet-dashboard-ops.ts +118 -0
  134. package/.versions/1.0.0/.pi/harnesses/lib/fleet-dashboard-view.ts +140 -0
  135. package/.versions/1.0.0/.pi/harnesses/lib/fleet-detail-view.ts +43 -0
  136. package/.versions/1.0.0/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  137. package/.versions/1.0.0/.pi/harnesses/lib/fleet-panel.ts +34 -0
  138. package/.versions/1.0.0/.pi/harnesses/lib/fleet-read-model.ts +131 -0
  139. package/.versions/1.0.0/.pi/harnesses/lib/fleet-selection.ts +24 -0
  140. package/.versions/1.0.0/.pi/harnesses/lib/herdr-client.ts +472 -0
  141. package/.versions/1.0.0/.pi/harnesses/lib/herdr-presence.ts +399 -0
  142. package/.versions/1.0.0/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  143. package/.versions/1.0.0/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  144. package/.versions/1.0.0/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  145. package/.versions/1.0.0/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  146. package/.versions/1.0.0/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  147. package/.versions/1.0.0/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  148. package/.versions/1.0.0/.pi/harnesses/lib/spawned-peers.js +190 -0
  149. package/.versions/1.0.0/.pi/harnesses/package-lock.json +2046 -0
  150. package/.versions/1.0.0/.pi/harnesses/package.json +10 -0
  151. package/.versions/1.0.0/.pi/prompts/af-build.md +24 -0
  152. package/{.claude/commands/code-simplify.md → .versions/1.0.0/.pi/prompts/af-code-simplify.md} +3 -3
  153. package/{.claude/commands/plan.md → .versions/1.0.0/.pi/prompts/af-plan.md} +1 -1
  154. package/.versions/{0.0.11/.claude/commands/review.md → 1.0.0/.pi/prompts/af-review.md} +3 -3
  155. package/.versions/1.0.0/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  156. package/.versions/1.0.0/.pi/prompts/af-ship.md +17 -0
  157. package/.versions/{0.0.11/.claude/commands/spec.md → 1.0.0/.pi/prompts/af-spec.md} +1 -1
  158. package/.versions/{0.0.11/.claude/commands/test.md → 1.0.0/.pi/prompts/af-test.md} +2 -2
  159. package/.versions/1.0.0/.pi/skills/bowser/SKILL.md +145 -0
  160. package/.versions/1.0.0/.version +1 -0
  161. package/.versions/1.0.0/agents/architect.md +24 -0
  162. package/.versions/1.0.0/agents/bowser.md +27 -0
  163. package/.versions/1.0.0/agents/builder.md +54 -0
  164. package/.versions/1.0.0/agents/code-reviewer.md +208 -0
  165. package/.versions/1.0.0/agents/deep-researcher.md +32 -0
  166. package/.versions/1.0.0/agents/documenter.md +18 -0
  167. package/.versions/1.0.0/agents/orchestrator.md +72 -0
  168. package/.versions/1.0.0/agents/plan-reviewer.md +83 -0
  169. package/.versions/1.0.0/agents/planner.md +70 -0
  170. package/.versions/1.0.0/agents/releaser.md +24 -0
  171. package/.versions/1.0.0/agents/researcher.md +28 -0
  172. package/.versions/1.0.0/agents/security-auditor.md +167 -0
  173. package/.versions/1.0.0/agents/test-engineer.md +153 -0
  174. package/.versions/1.0.0/agents/web-debugger.md +43 -0
  175. package/.versions/1.0.0/agents/web-performance-auditor.md +193 -0
  176. package/.versions/1.0.0/codex/CONDUCTOR.md +148 -0
  177. package/.versions/1.0.0/docs/ARCHITECTURE.md +337 -0
  178. package/.versions/1.0.0/docs/agent-fleet-setup.md +437 -0
  179. package/.versions/1.0.0/docs/claude-code-coms-bridge.md +128 -0
  180. package/.versions/1.0.0/docs/codex-remote-conductor.md +170 -0
  181. package/.versions/1.0.0/docs/coms-hermes-bridge.md +189 -0
  182. package/.versions/1.0.0/docs/getting-started.md +98 -0
  183. package/.versions/1.0.0/docs/npm-install.md +292 -0
  184. package/.versions/1.0.0/docs/pi-extensions.md +412 -0
  185. package/.versions/1.0.0/docs/pi-setup.md +74 -0
  186. package/.versions/1.0.0/docs/skill-anatomy.md +150 -0
  187. package/.versions/1.0.0/hermes/README.md +347 -0
  188. package/.versions/1.0.0/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  189. package/.versions/1.0.0/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  190. package/.versions/1.0.0/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  191. package/.versions/1.0.0/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  192. package/.versions/1.0.0/hermes/gates/gate-o-capability.md +8 -0
  193. package/.versions/1.0.0/hermes/gates/gate-o-validator-fixtures.json +1 -0
  194. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  195. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  196. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  197. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  198. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  199. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  200. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  201. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  202. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  203. package/.versions/1.0.0/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  204. package/.versions/1.0.0/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  205. package/.versions/1.0.0/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  206. package/.versions/1.0.0/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  207. package/.versions/1.0.0/hermes/skills/hub-conductor/SKILL.md +84 -0
  208. package/.versions/1.0.0/hermes/skills/hub-liaison/SKILL.md +84 -0
  209. package/.versions/1.0.0/hermes/skills/hub-watchdog/SKILL.md +76 -0
  210. package/.versions/1.0.0/hermes/skills/hub-watchdog/manifest.json +1 -0
  211. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  212. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  213. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  214. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  215. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  216. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  217. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  218. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  219. package/.versions/1.0.0/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  220. package/.versions/1.0.0/hermes/watchdog-tests/__init__.py +0 -0
  221. package/.versions/1.0.0/hooks/coms-stop-hook.mjs +84 -0
  222. package/.versions/1.0.0/install-manifest.json +2745 -0
  223. package/.versions/1.0.0/justfile +272 -0
  224. package/.versions/1.0.0/manifest-meta.json +882 -0
  225. package/.versions/1.0.0/references/accessibility-checklist.md +160 -0
  226. package/.versions/1.0.0/references/definition-of-done.md +67 -0
  227. package/.versions/1.0.0/references/fleet-coordination-patterns.md +151 -0
  228. package/.versions/1.0.0/references/observability-checklist.md +91 -0
  229. package/.versions/1.0.0/references/orchestration-patterns.md +370 -0
  230. package/.versions/1.0.0/references/performance-checklist.md +153 -0
  231. package/.versions/1.0.0/references/prompting-patterns.md +380 -0
  232. package/.versions/1.0.0/references/security-checklist.md +179 -0
  233. package/.versions/1.0.0/references/testing-patterns.md +236 -0
  234. package/.versions/1.0.0/scripts/codex-conductor.ts +41 -0
  235. package/.versions/1.0.0/scripts/codex-remote-control.ts +167 -0
  236. package/.versions/1.0.0/scripts/coms-claude-bridge.ts +411 -0
  237. package/.versions/1.0.0/scripts/coms-cli.ts +484 -0
  238. package/.versions/1.0.0/scripts/coms-hermes-bridge.ts +413 -0
  239. package/.versions/1.0.0/scripts/fleet.ts +185 -0
  240. package/.versions/1.0.0/scripts/hermes-monitor-capability-runner.ts +25 -0
  241. package/.versions/1.0.0/scripts/hermes-monitor-scenario.ts +474 -0
  242. package/.versions/1.0.0/scripts/hermes-watchdog-capability-probe.ts +45 -0
  243. package/.versions/1.0.0/scripts/install-hermes-plugin.sh +180 -0
  244. package/.versions/1.0.0/scripts/lib/claude-bridge-core.ts +210 -0
  245. package/.versions/1.0.0/scripts/lib/codex-conductor.ts +88 -0
  246. package/.versions/1.0.0/scripts/lib/codex-remote-control.ts +480 -0
  247. package/.versions/1.0.0/scripts/lib/coms-envelope.ts +582 -0
  248. package/.versions/1.0.0/scripts/lib/fake-herdr-server.ts +88 -0
  249. package/.versions/1.0.0/scripts/lib/fleet-command.ts +266 -0
  250. package/.versions/1.0.0/scripts/lib/herdr-layout.ts +281 -0
  251. package/.versions/1.0.0/scripts/lib/hermes-bridge-core.ts +241 -0
  252. package/.versions/1.0.0/scripts/lib/hermes-monitor-events.ts +1 -0
  253. package/.versions/1.0.0/scripts/lib/hermes-monitor-herdr.ts +2 -0
  254. package/.versions/1.0.0/scripts/lib/hermes-monitor-model.ts +3 -0
  255. package/.versions/1.0.0/scripts/lib/hermes-monitor-registry.ts +2 -0
  256. package/.versions/1.0.0/scripts/lib/hermes-monitor-socket.ts +2 -0
  257. package/.versions/1.0.0/scripts/lib/hermes-monitor-store.ts +2 -0
  258. package/.versions/1.0.0/scripts/lib/monitor-env.ts +146 -0
  259. package/.versions/1.0.0/scripts/lib/peer-launch.ts +318 -0
  260. package/.versions/1.0.0/scripts/lib/persona-banner.ts +62 -0
  261. package/.versions/1.0.0/scripts/lib/spawn-stagger.ts +101 -0
  262. package/.versions/1.0.0/scripts/lib/team-project.ts +213 -0
  263. package/.versions/1.0.0/scripts/lib/team-snapshot.ts +147 -0
  264. package/.versions/1.0.0/scripts/peer-banner.ts +40 -0
  265. package/.versions/1.0.0/scripts/peer-launch.ts +259 -0
  266. package/.versions/1.0.0/scripts/team-snapshot.ts +237 -0
  267. package/.versions/1.0.0/scripts/team-up.ts +406 -0
  268. package/.versions/1.0.0/skills/_internal/grilling.md +11 -0
  269. package/.versions/1.0.0/skills/browser-testing-with-devtools/SKILL.md +351 -0
  270. package/.versions/1.0.0/skills/code-review-and-quality/SKILL.md +381 -0
  271. package/.versions/1.0.0/skills/compound-learning/SKILL.md +137 -0
  272. package/.versions/1.0.0/skills/context-engineering/SKILL.md +291 -0
  273. package/.versions/1.0.0/skills/deprecation-and-migration/SKILL.md +206 -0
  274. package/.versions/1.0.0/skills/designing-agents/SKILL.md +394 -0
  275. package/.versions/1.0.0/skills/designing-agents/pi-harness-authoring.md +222 -0
  276. package/.versions/1.0.0/skills/frontend-ui-engineering/SKILL.md +328 -0
  277. package/.versions/1.0.0/skills/git-workflow-and-versioning/SKILL.md +316 -0
  278. package/.versions/1.0.0/skills/idea-refine/SKILL.md +182 -0
  279. package/.versions/1.0.0/skills/idea-refine/examples.md +238 -0
  280. package/.versions/1.0.0/skills/idea-refine/frameworks.md +99 -0
  281. package/.versions/1.0.0/skills/idea-refine/refinement-criteria.md +113 -0
  282. package/.versions/1.0.0/skills/idea-refine/scripts/idea-refine.sh +15 -0
  283. package/.versions/1.0.0/skills/incremental-implementation/SKILL.md +287 -0
  284. package/.versions/1.0.0/skills/interview-me/SKILL.md +226 -0
  285. package/.versions/1.0.0/skills/orchestration-verification/SKILL.md +181 -0
  286. package/.versions/1.0.0/skills/peer-coms/SKILL.md +90 -0
  287. package/.versions/1.0.0/skills/performance-optimization/SKILL.md +350 -0
  288. package/.versions/1.0.0/skills/planning-and-task-breakdown/SKILL.md +254 -0
  289. package/.versions/1.0.0/skills/security-and-hardening/SKILL.md +461 -0
  290. package/.versions/1.0.0/skills/spec-driven-development/SKILL.md +257 -0
  291. package/.versions/1.0.0/skills/using-agent-skills/SKILL.md +199 -0
  292. package/.versions/1.0.0/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  293. package/.versions/1.0.0/vendor/agent-skills-upstream/LICENSE +21 -0
  294. package/.versions/1.0.0/vendor/agent-skills-upstream/README.md +11 -0
  295. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  296. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  297. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  298. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  299. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  300. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  301. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  302. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  303. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  304. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  305. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  306. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  307. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  308. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  309. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  310. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  311. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  312. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  313. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  314. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  315. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  316. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  317. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  318. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  319. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  320. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  321. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  322. package/.versions/1.0.0/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  323. package/CHANGELOG.md +142 -0
  324. package/README.md +117 -79
  325. package/agents/orchestrator.md +1 -1
  326. package/bin/cli.js +289 -359
  327. package/bin/force-patch-changesets.js +18 -2
  328. package/bin/lib/apply.js +86 -32
  329. package/bin/lib/desired.js +87 -0
  330. package/bin/lib/detect-agent.js +22 -38
  331. package/bin/lib/doctor.js +283 -33
  332. package/bin/lib/features.js +78 -0
  333. package/bin/lib/manifest.js +127 -48
  334. package/bin/lib/overrides.js +35 -0
  335. package/bin/lib/personas.js +37 -0
  336. package/bin/lib/plan.js +18 -9
  337. package/bin/lib/purge.js +11 -0
  338. package/bin/lib/reconcile.js +68 -0
  339. package/bin/lib/scan.js +24 -0
  340. package/bin/lib/state.js +25 -1
  341. package/bin/lib/stt-wizard.js +33 -0
  342. package/bin/lib/transaction.js +149 -0
  343. package/bin/lib/tui.js +71 -0
  344. package/bin/lib/verify.js +9 -26
  345. package/bin/snapshot-version.js +3 -6
  346. package/docs/ARCHITECTURE.md +55 -21
  347. package/docs/MIGRATION-agent-fleet.md +222 -0
  348. package/docs/agent-fleet-setup.md +124 -64
  349. package/docs/claude-code-coms-bridge.md +21 -2
  350. package/docs/coms-hermes-bridge.md +1 -1
  351. package/docs/getting-started.md +61 -217
  352. package/docs/npm-install.md +207 -429
  353. package/docs/pi-extensions.md +85 -41
  354. package/docs/pi-setup.md +48 -545
  355. package/hermes/README.md +1 -1
  356. package/install-manifest.json +385 -1255
  357. package/justfile +45 -27
  358. package/manifest-meta.json +544 -134
  359. package/node_modules/pi-ask-user/README.md +43 -5
  360. package/node_modules/pi-ask-user/index.ts +630 -75
  361. package/node_modules/pi-ask-user/package.json +1 -1
  362. package/package.json +5 -11
  363. package/scripts/coms-claude-bridge.ts +10 -0
  364. package/scripts/fleet.ts +107 -90
  365. package/scripts/lib/claude-bridge-core.ts +45 -0
  366. package/scripts/lib/fleet-command.ts +170 -15
  367. package/scripts/lib/monitor-env.ts +18 -6
  368. package/scripts/lib/peer-launch.ts +6 -2
  369. package/scripts/lib/team-project.ts +24 -4
  370. package/scripts/team-up.ts +57 -11
  371. package/skills/designing-agents/SKILL.md +1 -1
  372. package/skills/designing-agents/pi-harness-authoring.md +3 -3
  373. package/.claude/commands/build.md +0 -44
  374. package/.claude/commands/design-agent.md +0 -14
  375. package/.claude/commands/doctor-agent-fleet.md +0 -22
  376. package/.claude/commands/orchestrate.md +0 -112
  377. package/.claude/commands/prime.md +0 -22
  378. package/.claude/commands/review.md +0 -16
  379. package/.claude/commands/set-hermes-telegram.md +0 -15
  380. package/.claude/commands/set-hermes-watchdog.md +0 -6
  381. package/.claude/commands/setup-agent-fleet.md +0 -17
  382. package/.claude/commands/ship.md +0 -72
  383. package/.claude/commands/spec.md +0 -15
  384. package/.claude/commands/test.md +0 -19
  385. package/.claude/commands/webperf.md +0 -32
  386. package/.claude/orchestrate-teams.yaml +0 -24
  387. package/.opencode/commands/af-build.md +0 -17
  388. package/.opencode/commands/af-code-simplify.md +0 -16
  389. package/.opencode/commands/af-compound.md +0 -16
  390. package/.opencode/commands/af-design-agent.md +0 -15
  391. package/.opencode/commands/af-doctor-agent-fleet.md +0 -22
  392. package/.opencode/commands/af-orchestrate.md +0 -112
  393. package/.opencode/commands/af-plan.md +0 -16
  394. package/.opencode/commands/af-prime.md +0 -22
  395. package/.opencode/commands/af-review.md +0 -15
  396. package/.opencode/commands/af-set-hermes-watchdog.md +0 -6
  397. package/.opencode/commands/af-setup-agent-fleet.md +0 -17
  398. package/.opencode/commands/af-ship.md +0 -16
  399. package/.opencode/commands/af-spec.md +0 -16
  400. package/.opencode/commands/af-test.md +0 -21
  401. package/.opencode/commands/af-webperf.md +0 -32
  402. package/.opencode/orchestrate-teams.yaml +0 -24
  403. package/.pi/prompts/af-doctor-agent-fleet.md +0 -22
  404. package/.pi/prompts/af-setup-agent-fleet.md +0 -19
  405. package/.versions/0.0.1/.opencode/commands/af-doctor-agent-fleet.md +0 -15
  406. package/.versions/0.0.1/.opencode/commands/af-setup-agent-fleet.md +0 -15
  407. package/.versions/0.0.1/skills/guided-workspace-setup/SKILL.md +0 -506
  408. package/.versions/0.0.10/.opencode/commands/af-doctor-agent-fleet.md +0 -22
  409. package/.versions/0.0.10/.opencode/commands/af-setup-agent-fleet.md +0 -17
  410. package/.versions/0.0.10/.pi/prompts/af-doctor-agent-fleet.md +0 -22
  411. package/.versions/0.0.10/.pi/prompts/af-setup-agent-fleet.md +0 -19
  412. package/.versions/0.0.10/skills/guided-workspace-setup/SKILL.md +0 -226
  413. package/.versions/0.0.11/.claude/commands/build.md +0 -44
  414. package/.versions/0.0.11/.claude/commands/code-simplify.md +0 -22
  415. package/.versions/0.0.11/.claude/commands/design-agent.md +0 -14
  416. package/.versions/0.0.11/.claude/commands/doctor-agent-fleet.md +0 -22
  417. package/.versions/0.0.11/.claude/commands/orchestrate.md +0 -112
  418. package/.versions/0.0.11/.claude/commands/plan.md +0 -16
  419. package/.versions/0.0.11/.claude/commands/prime.md +0 -22
  420. package/.versions/0.0.11/.claude/commands/set-hermes-telegram.md +0 -15
  421. package/.versions/0.0.11/.claude/commands/set-hermes-watchdog.md +0 -6
  422. package/.versions/0.0.11/.claude/commands/setup-agent-fleet.md +0 -17
  423. package/.versions/0.0.11/.claude/commands/ship.md +0 -72
  424. package/.versions/0.0.11/.claude/commands/webperf.md +0 -32
  425. package/.versions/0.0.11/.claude/orchestrate-teams.yaml +0 -24
  426. package/.versions/0.0.11/.opencode/commands/af-build.md +0 -17
  427. package/.versions/0.0.11/.opencode/commands/af-code-simplify.md +0 -16
  428. package/.versions/0.0.11/.opencode/commands/af-compound.md +0 -16
  429. package/.versions/0.0.11/.opencode/commands/af-design-agent.md +0 -15
  430. package/.versions/0.0.11/.opencode/commands/af-doctor-agent-fleet.md +0 -22
  431. package/.versions/0.0.11/.opencode/commands/af-orchestrate.md +0 -112
  432. package/.versions/0.0.11/.opencode/commands/af-plan.md +0 -16
  433. package/.versions/0.0.11/.opencode/commands/af-prime.md +0 -22
  434. package/.versions/0.0.11/.opencode/commands/af-review.md +0 -15
  435. package/.versions/0.0.11/.opencode/commands/af-set-hermes-telegram.md +0 -15
  436. package/.versions/0.0.11/.opencode/commands/af-set-hermes-watchdog.md +0 -6
  437. package/.versions/0.0.11/.opencode/commands/af-setup-agent-fleet.md +0 -17
  438. package/.versions/0.0.11/.opencode/commands/af-ship.md +0 -16
  439. package/.versions/0.0.11/.opencode/commands/af-spec.md +0 -16
  440. package/.versions/0.0.11/.opencode/commands/af-test.md +0 -21
  441. package/.versions/0.0.11/.opencode/commands/af-webperf.md +0 -32
  442. package/.versions/0.0.11/.opencode/orchestrate-teams.yaml +0 -24
  443. package/.versions/0.0.11/.pi/prompts/af-doctor-agent-fleet.md +0 -22
  444. package/.versions/0.0.11/.pi/prompts/af-setup-agent-fleet.md +0 -19
  445. package/.versions/0.0.11/docs/opencode-setup.md +0 -281
  446. package/.versions/0.0.11/hooks/SIMPLIFY-IGNORE.md +0 -90
  447. package/.versions/0.0.11/hooks/hooks.json +0 -14
  448. package/.versions/0.0.11/hooks/session-start.sh +0 -74
  449. package/.versions/0.0.11/hooks/simplify-ignore.sh +0 -302
  450. package/.versions/0.0.11/skills/guided-workspace-setup/SKILL.md +0 -226
  451. package/.versions/0.0.4/.opencode/commands/af-doctor-agent-fleet.md +0 -17
  452. package/.versions/0.0.4/.opencode/commands/af-setup-agent-fleet.md +0 -15
  453. package/.versions/0.0.4/skills/guided-workspace-setup/SKILL.md +0 -535
  454. package/.versions/0.0.4/skills/guided-workspace-setup/companion-manifest.json +0 -33
  455. package/.versions/0.0.5/.opencode/commands/af-doctor-agent-fleet.md +0 -17
  456. package/.versions/0.0.5/.opencode/commands/af-setup-agent-fleet.md +0 -15
  457. package/.versions/0.0.5/skills/guided-workspace-setup/SKILL.md +0 -542
  458. package/.versions/0.0.5/skills/guided-workspace-setup/companion-manifest.json +0 -35
  459. package/.versions/0.0.6/.opencode/commands/af-doctor-agent-fleet.md +0 -17
  460. package/.versions/0.0.6/.opencode/commands/af-setup-agent-fleet.md +0 -15
  461. package/.versions/0.0.6/.pi/prompts/af-doctor-agent-fleet.md +0 -15
  462. package/.versions/0.0.6/.pi/prompts/af-setup-agent-fleet.md +0 -27
  463. package/.versions/0.0.6/skills/guided-workspace-setup/SKILL.md +0 -544
  464. package/.versions/0.0.6/skills/guided-workspace-setup/companion-manifest.json +0 -35
  465. package/.versions/0.0.7/.opencode/commands/af-doctor-agent-fleet.md +0 -17
  466. package/.versions/0.0.7/.opencode/commands/af-setup-agent-fleet.md +0 -15
  467. package/.versions/0.0.7/.pi/prompts/af-doctor-agent-fleet.md +0 -15
  468. package/.versions/0.0.7/.pi/prompts/af-setup-agent-fleet.md +0 -27
  469. package/.versions/0.0.7/skills/guided-workspace-setup/SKILL.md +0 -544
  470. package/.versions/0.0.7/skills/guided-workspace-setup/companion-manifest.json +0 -35
  471. package/.versions/0.0.8/.opencode/commands/af-doctor-agent-fleet.md +0 -17
  472. package/.versions/0.0.8/.opencode/commands/af-setup-agent-fleet.md +0 -15
  473. package/.versions/0.0.8/.pi/prompts/af-doctor-agent-fleet.md +0 -15
  474. package/.versions/0.0.8/.pi/prompts/af-setup-agent-fleet.md +0 -27
  475. package/.versions/0.0.8/skills/guided-workspace-setup/SKILL.md +0 -544
  476. package/.versions/0.0.8/skills/guided-workspace-setup/companion-manifest.json +0 -36
  477. package/.versions/0.0.9/.opencode/commands/af-doctor-agent-fleet.md +0 -17
  478. package/.versions/0.0.9/.opencode/commands/af-setup-agent-fleet.md +0 -15
  479. package/.versions/0.0.9/.pi/prompts/af-doctor-agent-fleet.md +0 -15
  480. package/.versions/0.0.9/.pi/prompts/af-setup-agent-fleet.md +0 -27
  481. package/.versions/0.0.9/skills/guided-workspace-setup/SKILL.md +0 -544
  482. package/bin/lib/bootstrap.js +0 -323
  483. package/bin/lib/transform-persona.js +0 -180
  484. package/docs/opencode-setup.md +0 -281
  485. package/hooks/SIMPLIFY-IGNORE.md +0 -90
  486. package/hooks/hooks.json +0 -14
  487. package/hooks/session-start.sh +0 -74
  488. package/hooks/simplify-ignore.sh +0 -302
  489. package/skills/guided-workspace-setup/SKILL.md +0 -226
  490. /package/.versions/0.0.10/{skills/guided-workspace-setup/companion-manifest.json → bin/catalog/harness-runtime-closure.json} +0 -0
  491. /package/.versions/0.0.11/{skills/guided-workspace-setup/companion-manifest.json → bin/catalog/harness-runtime-closure.json} +0 -0
  492. /package/{.opencode/commands → .versions/1.0.0/.pi/prompts}/af-set-hermes-telegram.md +0 -0
  493. /package/.versions/{0.0.9/skills/guided-workspace-setup/companion-manifest.json → 1.0.0/bin/catalog/harness-runtime-closure.json} +0 -0
  494. /package/{skills/guided-workspace-setup/companion-manifest.json → bin/catalog/harness-runtime-closure.json} +0 -0
@@ -1,72 +0,0 @@
1
- ---
2
- description: Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision
3
- ---
4
-
5
- Invoke the agent-fleet:shipping-and-launch skill.
6
-
7
- `/ship` is a **fan-out orchestrator**. It runs three specialist personas in parallel against the current change, then merges their reports into a single go/no-go decision with a rollback plan. The personas operate independently — no shared state, no ordering — which is what makes parallel execution safe and useful here.
8
-
9
- ## Phase A — Parallel fan-out
10
-
11
- Spawn three subagents concurrently using the Agent tool. **Issue all three Agent tool calls in a single assistant turn so they execute in parallel** — sequential calls defeat the purpose of this command.
12
-
13
- In Claude Code, each call passes `subagent_type` matching the persona's `name` field:
14
-
15
- 1. **`code-reviewer`** — Run a five-axis review (correctness, readability, architecture, security, performance) on the staged changes or recent commits. Output the standard review template.
16
- 2. **`security-auditor`** — Run a vulnerability and threat-model pass. Check OWASP Top 10, secrets handling, auth/authz, dependency CVEs. Output the standard audit report.
17
- 3. **`test-engineer`** — Analyze test coverage for the change. Identify gaps in happy path, edge cases, error paths, and concurrency scenarios. Output the standard coverage analysis.
18
-
19
- In other harnesses without an Agent tool, invoke each persona's system prompt sequentially and treat their outputs as if returned in parallel — the merge phase still works.
20
-
21
- Constraints (from Claude Code's subagent model):
22
- - Subagents cannot spawn other subagents — do not let one persona delegate to another.
23
- - Each subagent gets its own context window and returns only its report to this main session.
24
- - If you need teammates that talk to each other instead of just reporting back, use Claude Code Agent Teams and reference these personas as teammate types (see `references/orchestration-patterns.md`).
25
-
26
- **Persona resolution.** If you've defined your own `code-reviewer`, `security-auditor`, or `test-engineer` in `.claude/agents/` or `~/.claude/agents/`, those take precedence over this plugin's versions — `/ship` picks up your customizations automatically. This is intentional: plugin subagents sit at the bottom of Claude Code's scope priority table, so user-level definitions win by design.
27
-
28
- ## Phase B — Merge in main context
29
-
30
- Once all three reports are back, the main agent (not a sub-persona) synthesizes them:
31
-
32
- 1. **Code Quality** — Aggregate Critical/Important findings from `code-reviewer` and any failing tests, lint, or build output. Resolve duplicates between reviewers.
33
- 2. **Security** — Promote any Critical/High `security-auditor` findings to launch blockers. Cross-reference with `code-reviewer`'s security axis.
34
- 3. **Performance** — Pull from `code-reviewer`'s performance axis; cross-check Core Web Vitals if applicable.
35
- 4. **Accessibility** — Verify keyboard nav, screen reader support, contrast (not covered by the three personas — handle directly here, or invoke the accessibility checklist).
36
- 5. **Infrastructure** — Env vars, migrations, monitoring, feature flags. Verify directly.
37
- 6. **Documentation** — README, ADRs, changelog. Verify directly.
38
-
39
- ## Phase C — Decision and rollback
40
-
41
- Produce a single output:
42
-
43
- ```markdown
44
- ## Ship Decision: GO | NO-GO
45
-
46
- ### Blockers (must fix before ship)
47
- - [Source persona: Critical finding + file:line]
48
-
49
- ### Recommended fixes (should fix before ship)
50
- - [Source persona: Important finding + file:line]
51
-
52
- ### Acknowledged risks (shipping anyway)
53
- - [Risk + mitigation]
54
-
55
- ### Rollback plan
56
- - Trigger conditions: [what signals would prompt rollback]
57
- - Rollback procedure: [exact steps]
58
- - Recovery time objective: [target]
59
-
60
- ### Specialist reports (full)
61
- - [code-reviewer report]
62
- - [security-auditor report]
63
- - [test-engineer report]
64
- ```
65
-
66
- ## Rules
67
-
68
- 1. The three Phase A personas run in parallel — never sequentially.
69
- 2. Personas do not call each other. The main agent merges in Phase B.
70
- 3. The rollback plan is mandatory before any GO decision.
71
- 4. If any persona returns a Critical finding, the default verdict is NO-GO unless the user explicitly accepts the risk.
72
- 5. **Skip the fan-out only if all of the following are true:** the change touches 2 files or fewer, the diff is under 50 lines, and it does not touch auth, payments, data access, or config/env. Otherwise, default to fan-out. `/ship` is designed for production-bound changes — when the blast radius is non-trivial, run the parallel review even if the diff looks small.
@@ -1,32 +0,0 @@
1
- ---
2
- description: Run a web performance audit via the web-performance-auditor persona
3
- ---
4
-
5
- `/webperf` targets web applications specifically. Do not use it for utility libraries, CLIs, or server-only code with no browser-facing output.
6
-
7
- ## Determine the mode
8
-
9
- **Deep mode** — activate when any of these is available:
10
- - A Lighthouse JSON report file (e.g. `npx lighthouse <url> --output json --output-path ./report.json`, or `npx -p chrome-devtools-mcp chrome-devtools lighthouse_audit --output-format=json` from the Chrome DevTools MCP CLI)
11
- - A PageSpeed Insights JSON response (includes Lighthouse + CrUX)
12
- - A CrUX API response (requires `CRUX_API_KEY` or `GOOGLE_API_KEY`)
13
- - A DevTools performance trace
14
- - A live URL plus the `chrome-devtools` MCP server configured in the harness (the agent can capture metrics directly via `lighthouse_audit` and `performance_*` tools)
15
- - The Chrome DevTools MCP CLI invoked locally (via `npx -p chrome-devtools-mcp chrome-devtools <tool>` or after `npm i -g chrome-devtools-mcp`) — the user runs commands like `chrome-devtools lighthouse_audit --output-format=json` and passes the JSON output to the agent
16
-
17
- **Quick mode** — default when none of the above are available. The agent scans source code for structural anti-patterns and labels every finding as `potential impact`.
18
-
19
- ## Run the audit
20
-
21
- Spawn the `web-performance-auditor` subagent. Pass it explicitly:
22
-
23
- - The files, components, or diff under review
24
- - Any artifact paths (Lighthouse JSON, PSI JSON, CrUX response, trace) or pasted JSON content
25
- - The target URL or page name when known
26
- - A note on which mode you expect (Quick or Deep), so the agent surfaces missing inputs if Deep was intended
27
-
28
- The subagent returns a scorecard (only populated with sourced values), a ranked list of findings, positive observations, and proactive recommendations.
29
-
30
- ## Output
31
-
32
- Return the full audit report to the user. No synthesis or merge step is needed — this is a single-persona command.
@@ -1,24 +0,0 @@
1
- # Teams for /orchestrate. The main session reads this file and routes the
2
- # named team as a ROSTER (runtime-decided order), not a fixed pipeline.
3
- #
4
- # Rules the /orchestrate command relies on:
5
- # 1. First key is the default team (used when no team argument is given).
6
- # 2. researcher / deep-researcher are NOT listed — they are always available
7
- # out-of-band for NEEDS_RESEARCH dispatch (mirrors pi's spawn_research).
8
- # 3. Every listed persona must exist in .claude/agents/ or it is skipped with
9
- # a warning.
10
- #
11
- # Switch at runtime: /orchestrate <team> "<task>" (parallels pi's /agents-team).
12
-
13
- default:
14
- - planner
15
- - builder
16
-
17
- full:
18
- - planner
19
- - plan-reviewer
20
- - builder
21
- - code-reviewer
22
-
23
- hotfix:
24
- - builder
@@ -1,17 +0,0 @@
1
- ---
2
- description: Implement the next task incrementally - build, test, verify, commit
3
- ---
4
-
5
- Invoke the `incremental-implementation` skill and the `test-driven-development` skill via the `skill` tool.
6
-
7
- Pick the next pending task from the plan. For each task:
8
-
9
- 1. Read the task's acceptance criteria.
10
- 2. Load relevant context: existing code, patterns, and types.
11
- 3. Write a failing test for the expected behavior.
12
- 4. Implement the minimum code to pass the test.
13
- 5. Run the relevant test suite to check for regressions.
14
- 6. Run the build to verify compilation.
15
- 7. Mark the task complete and move to the next one.
16
-
17
- If any step fails, invoke the `debugging-and-error-recovery` skill via the `skill` tool.
@@ -1,16 +0,0 @@
1
- ---
2
- description: Simplify code for clarity and maintainability without changing behavior
3
- ---
4
-
5
- Invoke the `code-simplification` skill via the `skill` tool.
6
-
7
- Simplify recently changed code, or the scope specified in `$ARGUMENTS`, while preserving exact behavior:
8
-
9
- 1. Read the project's agent instructions and study project conventions.
10
- 2. Identify the target code: recent changes unless a broader scope is specified.
11
- 3. Understand the code's purpose, callers, edge cases, and test coverage before touching it.
12
- 4. Scan for simplification opportunities: deep nesting, long functions, nested ternaries, generic names, duplicated logic, or dead code.
13
- 5. Apply each simplification incrementally and run relevant tests after each change.
14
- 6. Verify tests pass, the build succeeds, and the diff is clean.
15
-
16
- If tests fail after a simplification, revert only that simplification and reconsider. Invoke `code-review-and-quality` via the `skill` tool to review the result.
@@ -1,16 +0,0 @@
1
- ---
2
- description: Capture this session's lessons into the project's rules and docs — compound engineering pass
3
- ---
4
-
5
- Invoke the `compound-learning` skill via the `skill` tool.
6
-
7
- Capture this session's lessons into the project's own rules (HOW) and docs (WHAT/WHY), optionally focused on `$ARGUMENTS`:
8
-
9
- 1. Resolve the targets: read `.ai/agent-fleet-overrides.md` — the `## agent-hub` (legacy `## agent-team`) section's `rules:` and `docs:` keys name the rule folders and documentation entry points. If absent, locate an existing rules/docs tree and confirm it with the user; never invent a new tree.
10
- 2. Gather the evidence: this conversation (user corrections, decisions, rejected approaches), the session's `git diff` / `git log`, and any review findings produced during the session.
11
- 3. Extract at most 5 candidate lessons — each one imperative sentence plus a one-line Why (the failure it prevents) and a one-line Evidence (what happened this session). Classify each as rule, doc, or neither; the default verdict is neither.
12
- 4. Dedupe index-first: read the rules tree's `README.md`/`index.md` manifest, grep for existing coverage, and prefer sharpening an existing rule in place over adding a new one.
13
- 5. Propose the surviving lessons — target file, Why, Evidence, and the exact diff — and wait for approval. The user filters preferences-of-the-moment from durable policy.
14
- 6. Apply the approved diffs as minimal edits to existing files (at most 1 new file, registered in the tree's index), verify links and indexes still resolve, and report the changes file by file.
15
-
16
- Run this at the end of a session, before the context is gone. If nothing rises to a lesson, say so and stop — compounding a smooth session produces filler.
@@ -1,15 +0,0 @@
1
- ---
2
- description: Design and write a new agent persona, workflow skill, or pi harness
3
- ---
4
-
5
- Invoke the `designing-agents` skill via the `skill` tool.
6
-
7
- Begin by understanding what the user wants to author:
8
-
9
- 1. Is this a persona (a role or lens the agent adopts), a skill (a repeatable workflow with gated steps and verification), or a pi harness (a TypeScript pi extension that reshapes the session)?
10
- 2. What is the one-sentence purpose and when should it be invoked?
11
- 3. What framework or steps should it follow?
12
- 4. What are the explicit non-goals and scope limits?
13
- 5. What output shape should a typical invocation produce?
14
-
15
- Then scan the target location — `agents/`, `skills/`, or `.pi/harnesses/` — for overlap. Draft the artifact using the matching template, verify the draft against prompting guidance when available, and confirm with the user before writing the file(s).
@@ -1,22 +0,0 @@
1
- ---
2
- description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
3
- ---
4
-
5
- Invoke the `guided-workspace-setup` skill via the `skill` tool and run its repair path only — not the rest of the install flow. `/af-setup-agent-fleet` offers the same thing as soon as it finds prior install state.
6
-
7
- Run the CLI — do not walk directories or repair files yourself:
8
-
9
- ```
10
- node <source-root>/bin/cli.js doctor --workspace <workspace> [--agent <agent>] --json
11
- ```
12
-
13
- Resolve `<source-root>` from `<workspace>/.ai/.agent-fleet-bootstrap.json`, or this prompt's realpath if it is a symlink, or by asking. Never scan the filesystem for agent-fleet clones.
14
-
15
- The report has two halves, and they are repaired differently on purpose:
16
-
17
- - `repairs` — recorded items that are missing, dangling, or linked outside the source root. These are rebuilt through the same `apply()` path `install` writes with, so a repaired file is byte-identical to a freshly installed one.
18
- - `findings` — what the install record cannot own: broken symlinks in a pre-engine workspace, stale persona names in `.pi/agents/*.yaml` (`reviewer` → `code-reviewer`, `red-team` → `security-auditor`), plus advisory ones. `overrides` and `yaml-shape` findings are **advisory**: report them with "edit by hand" and never fix them, because the fix is always a hand edit of the flagged file.
19
-
20
- Print the two lists as text, then ask one native single-select (or a plain text question without a widget) — *"Apply the suggested fixes?"* — and on yes re-run with `--fix`. An empty answer or a cancel applies nothing.
21
-
22
- Exit codes: `0` nothing to repair, `2` repairable issues found (or advisories present, or a repair failed), `1` could not run. Report the counts the CLI returns; do not invent your own.
@@ -1,112 +0,0 @@
1
- ---
2
- description: Orchestrate a config-defined team of subagents — route planner/builder (and more) as a runtime roster, handling NEEDS_RESEARCH and PLAN_FILE handoffs
3
- ---
4
-
5
- You are the **orchestrator**. The primary agent drives a team of installed `mode: subagent`
6
- agents to deliver the task in `$ARGUMENTS`. Subagents cannot nest — **all dispatching is
7
- yours**.
8
-
9
- ## Roles
10
-
11
- | Role | What it does |
12
- |---|---|
13
- | `researcher` | Always-available read-only recon. Cites `file:line`. Never edits. |
14
- | `planner` | Writes a plan doc only; ends with `PLAN_FILE: <path>` or pauses on `NEEDS_RESEARCH:`. |
15
- | `builder` | Implements in small increments; may pause on `NEEDS_RESEARCH:`. |
16
- | `plan-reviewer` / `code-reviewer` | Read-only; their whole result is findings (no handoff marker). |
17
-
18
- ## Step 0 — Resolve the team
19
-
20
- 1. Read `.opencode/orchestrate-teams.yaml` (a map of team-name → ordered persona list).
21
- 2. Resolve team + task from `$ARGUMENTS`:
22
- - Treat the **first token** as a team name **only** when it is a bare single word that
23
- exactly matches a config key **and** is followed by the rest of the task. To force a
24
- team explicitly, the user writes `/af-orchestrate team=<name> <task>`. Otherwise the
25
- team is the first key (`default`) and all of `$ARGUMENTS` is the task.
26
- - **Fallbacks:** if the config is **absent / empty / fails to parse**, fall back to the
27
- built-in `planner` + `builder` default and **say which fallback fired** (don't proceed
28
- silently). If a named team is requested but not found, list the available team keys and
29
- ask rather than guessing.
30
- 3. **Validate personas:** each persona in the resolved team must exist in `.opencode/agent/`.
31
- Skip-with-warning any that don't. If every persona is missing, fall back to the built-in
32
- default.
33
- 4. List the resolved team back to the user before dispatching.
34
-
35
- `researcher` / `deep-researcher` are **always available** even when not listed in the team.
36
-
37
- ## Step 1 — The team is a roster, not a fixed pipeline
38
-
39
- The persona list is the set of specialists you may route to; **you decide the order at
40
- runtime from the task state** (the listed order is only a sensible starting default). So:
41
-
42
- - **Skip `planner`** when a usable plan already exists (the user passed a `PLAN_FILE` or
43
- pointed at one) — go straight to `builder`.
44
- - **Re-dispatch `researcher` at any point** — after `planner`, mid-build — whenever a
45
- specialist needs a fact checked, not only as a first step.
46
- - **Loop back to `planner`** if `builder` surfaces that the plan is wrong.
47
-
48
- Do **not** enforce a hard `researcher → planner → builder` sequence.
49
-
50
- ## The Verification Contract (applies across every step)
51
-
52
- Read `skills/orchestration-verification/SKILL.md` before non-trivial work and hold its
53
- contract for the whole run. Subagents here cannot persist a shared ledger, so **you** keep
54
- the acceptance assertions in your own working notes and refuse "done" until each is proven.
55
-
56
- - **Build the assertions first.** Before dispatching `builder` for any non-trivial task,
57
- convert the request into numbered, tagged assertions (`test` | `runtime-ui` | `code-grep`
58
- | `manual`, one checkable pass condition each). Pass the relevant assertions **verbatim**
59
- into each dispatch and advance only on assertions that come back *proven with named
60
- evidence* — propagation in prose is not verification.
61
- - **Inventory parity for "behave like X" requests.** When the request is "make X behave like
62
- existing Y", dispatch `researcher` / `deep-researcher` **first** to enumerate every site
63
- where the exemplar is special-cased (flags, branches, display, validation, translations,
64
- fixtures, tests), and turn each site into an assertion covering the *whole* set — otherwise
65
- the exemplar ships and its siblings are missed.
66
- - **Require runtime proof for UI assertions.** A `runtime-ui` assertion (visibility,
67
- placement, "appears in the table") is closed only by an actual runtime observation via
68
- `browser-testing-with-devtools`, never a static review.
69
- - **Accept assertion status, not verdicts.** Treat specialist returns as `assertions_proven`
70
- / `assertions_unproven` / `assertions_failed`; demote any "approved" claim with no named
71
- evidence to unproven and re-dispatch it.
72
- - **Reset on "wrong again".** When the user reports a delivered requirement is wrong again,
73
- treat prior summaries as suspect, rebuild the affected assertions from the **latest**
74
- correction (re-running the parity inventory for "behave like" cases), then re-dispatch.
75
-
76
- ## Step 2 — Route to specialists, honouring handoff markers
77
-
78
- State the chosen next step (and why) before each dispatch, so routing is visible.
79
-
80
- - `planner` → read its `PLAN_FILE: <path>` and load the plan.
81
- - `builder` → loop over the plan's `## Task List`, **one task per dispatch**, checking each
82
- task's acceptance criteria **and the relevant acceptance assertions** before moving on.
83
- - **Marker-less personas** (`plan-reviewer` / `code-reviewer`) emit no handoff marker —
84
- their returned report **is** the result; "done" = the report came back, nothing to wait
85
- for. Fold findings forward; if a `code-reviewer` raised must-fix issues, loop back to
86
- `builder`.
87
-
88
- ## Step 3 — NEEDS_RESEARCH dispatch (core)
89
-
90
- Whenever any persona's result contains one or more `NEEDS_RESEARCH: <question>` lines:
91
-
92
- 1. Pause that track.
93
- 2. Dispatch `researcher` (read-only) once per question — in parallel when independent.
94
- 3. Collect the findings.
95
- 4. Resume the paused persona by re-dispatching it with the **original task plus the
96
- findings inlined**.
97
-
98
- **Never** answer a `NEEDS_RESEARCH` by guessing.
99
-
100
- ## Step 4 — Reviewer only if present
101
-
102
- The `default` roster has **no reviewer**. After the final builder task's acceptance criteria
103
- pass, report completion and **state explicitly that review/verification was not run** and
104
- which acceptance assertions therefore remain unproven (the user can pick the `full` team or
105
- run `/af-review`). When the active team *does* include a reviewer, run it as a normal step and
106
- require it to report parity across sibling cases, not just the exemplar.
107
-
108
- ## Step 5 — Report
109
-
110
- Report crisply: **active team**, what changed, which acceptance assertions are **proven (with
111
- evidence)**, which remain **unproven or failed**, and what's next. Never report "done" while a
112
- relevant assertion is unproven.
@@ -1,16 +0,0 @@
1
- ---
2
- description: Break work into small verifiable tasks with acceptance criteria and dependency ordering
3
- ---
4
-
5
- Invoke the `planning-and-task-breakdown` skill via the `skill` tool.
6
-
7
- Read the existing spec, such as `SPEC.md`, and relevant codebase sections. Then:
8
-
9
- 1. Enter planning mode: read only, no code changes.
10
- 2. Identify the dependency graph between components.
11
- 3. Slice work vertically, with one complete path per task rather than horizontal layers.
12
- 4. Write tasks with acceptance criteria and verification steps.
13
- 5. Add checkpoints between phases.
14
- 6. Present the plan for human review.
15
-
16
- Save the plan to the location the `planning-and-task-breakdown` skill defines (default `docs/plans/{area}/PLAN-{prd-name}-{phase}.md`, with the task list embedded — no separate todo file; overridable per project via `.ai/agent-fleet-overrides.md`), only after the user confirms the plan should be written.
@@ -1,22 +0,0 @@
1
- ---
2
- description: Load foundational context for the agent-fleet repository
3
- ---
4
-
5
- # Purpose
6
-
7
- Orient yourself in **agent-fleet** — a collection of production-grade engineering skills
8
- for AI coding agents, plus pi extensions, specialist agent personas, and lifecycle
9
- commands that map to the software development lifecycle.
10
-
11
- ## Workflow
12
-
13
- 1. Run `git ls-files` to see the full project file tree
14
- 2. Read `README.md` and `CLAUDE.md` for the project overview and conventions
15
- 3. Read `docs/skill-anatomy.md` to learn the required skill format
16
- 4. Skim `skills/*/SKILL.md` — the core skills, grouped by lifecycle phase
17
- (Define → Plan → Build → Verify → Review → Ship)
18
- 5. Read `agents/*.md` — the specialist review personas
19
- 6. Read `docs/pi-extensions.md`, `.pi/extensions/*/README.md` (always-on utilities), and `.pi/harnesses/*/README.md` (selectable session harnesses)
20
- 7. Summarize your understanding: purpose, structure, key files, and entry points
21
-
22
- Do this directly — read the files yourself rather than delegating to subagents.
@@ -1,15 +0,0 @@
1
- ---
2
- description: Conduct a five-axis code review - correctness, readability, architecture, security, performance
3
- ---
4
-
5
- Invoke the `code-review-and-quality` skill via the `skill` tool.
6
-
7
- Review the current changes, staged changes, or scope specified in `$ARGUMENTS` across these axes:
8
-
9
- 1. Correctness: Does it match the spec? Are edge cases handled? Are tests adequate?
10
- 2. Readability: Are names clear? Is the logic straightforward and well organized?
11
- 3. Architecture: Does it follow existing patterns? Are boundaries clean? Is the abstraction level right?
12
- 4. Security: Is input validated? Are secrets safe? Is authorization checked? Invoke `security-and-hardening` via the `skill` tool when relevant.
13
- 5. Performance: Are there N+1 queries, unbounded operations, or avoidable frontend regressions? Invoke `performance-optimization` via the `skill` tool when relevant.
14
-
15
- Categorize findings as Critical, Important, or Suggestion. Output a structured review with specific file and line references plus fix recommendations.
@@ -1,15 +0,0 @@
1
- ---
2
- description: Install/status the Hermes liaison or turn its Telegram ask_user bridge on/off
3
- argument-hint: "<install|status|on|off> [telegram-id] [--profile NAME] [--force] [--restart]"
4
- ---
5
-
6
- Run the deterministic Agent Fleet controller with the arguments from `$ARGUMENTS`. Supported forms are:
7
-
8
- ```text
9
- set-hermes-telegram install [--profile NAME] [--force] [--restart]
10
- set-hermes-telegram status [--profile NAME]
11
- set-hermes-telegram on <telegram-id[:topic-id]> [--profile NAME]
12
- set-hermes-telegram off <telegram-id[:topic-id]> [--profile NAME]
13
- ```
14
-
15
- Use `node bin/cli.js set-hermes-telegram ...` when the checkout-local CLI exists; otherwise use `npx --no-install agent-fleet set-hermes-telegram ...`. Pass parsed values as separately quoted shell arguments. If neither CLI exists, report that Agent Fleet must be installed or updated. Do not reproduce installation or Herdr lifecycle with ad-hoc commands, do not bypass a `--force` refusal, and do not send a test Telegram message. Return the controller output verbatim.
@@ -1,6 +0,0 @@
1
- ---
2
- description: Inspect or safely install the fail-closed Hermes watchdog
3
- argument-hint: "<status|install|update|uninstall> [--profile NAME] [--force] [--dry-run]"
4
- ---
5
-
6
- Ask the user before every write or `--force`. Use the deterministic watchdog installer only; status is read-only, stopped profiles require explicit `--profile`, and the controller never changes Hermes services, starts a watcher, or changes unrelated permissions. Gate O remains unproven and fail-closed: no live origin delivery, steering, surgical, or out-of-turn chat claim.
@@ -1,17 +0,0 @@
1
- ---
2
- description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
3
- ---
4
-
5
- Invoke the `guided-workspace-setup` skill via the `skill` tool and follow it.
6
-
7
- Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask. Confirm the coding agent (`opencode` here unless the user says otherwise).
8
-
9
- The skill is a front-end over the `agent-fleet` CLI's installer engine: `verify --json` supplies the menu (groups, profiles, per-item state), and `install` / `upgrade` / `uninstall` / `doctor --fix` do every write. **Do not copy, symlink, or delete an install target yourself** — the CLI records ownership in `.ai/agent-fleet-state.json`, and anything written by hand is invisible to every later run. Personas land in `.opencode/agent/<name>.md` as generated files; the CLI handles that too. Artifacts install as copies; never ask copy-vs-symlink and never pass `--method`.
10
-
11
- Two things are yours rather than the CLI's: drafting `.ai/agent-fleet-overrides.md` from a scan of the project, and the `pi-voice-stt` provider Q&A (pi workspaces only).
12
-
13
- With a native select widget, open with the Express question backed by the manifest's profiles, then run group screens only on `Custom`, with drill-ins behind `Customise`. Without one, print a compact table and take a text reply. Option titles carry `<name> ★ [state]`; descriptions say what picking it does in plain words. Leaving an installed item unpicked keeps it — removal is its own explicit screen and runs `uninstall`. Cancel is a no-op everywhere except the final confirmation.
14
-
15
- If `verify` reports findings or broken items, offer `doctor --fix` before the menu — a broken workspace makes the menu lie about what is installed.
16
-
17
- Print the plan as compact action-grouped lines and wait for explicit confirmation before anything is written. Exit `3` from the CLI means conflicts: show the `.new` files it wrote and let the user decide — never pick a side for them. Relay `operator` and `external` steps verbatim; the CLI performs neither, and neither do you.
@@ -1,16 +0,0 @@
1
- ---
2
- description: Run the pre-launch checklist and prepare for production deployment
3
- ---
4
-
5
- Invoke the `shipping-and-launch` skill via the `skill` tool.
6
-
7
- Run through the complete pre-launch checklist:
8
-
9
- 1. Code quality: tests pass, build clean, lint clean, no stray TODOs or console logs.
10
- 2. Security: dependency audit checked, no secrets in code, auth in place, headers configured where applicable.
11
- 3. Performance: Core Web Vitals or relevant performance checks are acceptable, no N+1 queries, images and bundles are reasonable.
12
- 4. Accessibility: keyboard navigation works, screen reader semantics are acceptable, contrast is adequate.
13
- 5. Infrastructure: environment variables are set, migrations are ready, monitoring is configured.
14
- 6. Documentation: README is current, ADRs are written when needed, changelog is updated when relevant.
15
-
16
- Report any failing checks and help resolve them before deployment. Define the rollback plan before proceeding.
@@ -1,16 +0,0 @@
1
- ---
2
- description: Start spec-driven development by writing a structured specification before code
3
- ---
4
-
5
- Invoke the `spec-driven-development` skill via the `skill` tool.
6
-
7
- Begin by understanding what the user wants to build. Ask clarifying questions about:
8
-
9
- 1. The objective and target users.
10
- 2. Core features and acceptance criteria.
11
- 3. Tech stack preferences and constraints.
12
- 4. Known boundaries: what to always do, ask first about, and never do.
13
-
14
- Then generate a structured spec covering objective, commands, project structure, code style, testing strategy, and boundaries.
15
-
16
- Confirm with the user before saving, then save the spec to the location the `spec-driven-development` skill defines (default `docs/prds/{area}/PRD{n}-{topic}.md`; overridable per project via `.ai/agent-fleet-overrides.md`).
@@ -1,21 +0,0 @@
1
- ---
2
- description: Run a TDD workflow - write failing tests, implement, verify
3
- ---
4
-
5
- Invoke the `test-driven-development` skill via the `skill` tool.
6
-
7
- For new features:
8
-
9
- 1. Write tests that describe the expected behavior and confirm they fail.
10
- 2. Implement the code to make them pass.
11
- 3. Refactor while keeping tests green.
12
-
13
- For bug fixes, use the Prove-It pattern:
14
-
15
- 1. Write a test that reproduces the bug and must fail.
16
- 2. Confirm the test fails.
17
- 3. Implement the fix.
18
- 4. Confirm the test passes.
19
- 5. Run the relevant full test suite for regressions.
20
-
21
- For browser-related issues, also invoke `browser-testing-with-devtools` via the `skill` tool to verify with Chrome DevTools MCP.
@@ -1,32 +0,0 @@
1
- ---
2
- description: Run a web performance audit via the web-performance-auditor subagent
3
- ---
4
-
5
- `/webperf` targets web applications specifically. Do not use it for utility libraries, CLIs, or server-only code with no browser-facing output.
6
-
7
- ## Determine the mode
8
-
9
- **Deep mode** - activate when any of these is available:
10
- - A Lighthouse JSON report file (e.g. `npx lighthouse <url> --output json --output-path ./report.json`, or `npx -p chrome-devtools-mcp chrome-devtools lighthouse_audit --output-format=json` from the Chrome DevTools MCP CLI)
11
- - A PageSpeed Insights JSON response (includes Lighthouse + CrUX)
12
- - A CrUX API response (requires `CRUX_API_KEY` or `GOOGLE_API_KEY`)
13
- - A DevTools performance trace
14
- - A live URL plus the `chrome-devtools` MCP server configured in the harness (the agent can capture metrics directly via `lighthouse_audit` and `performance_*` tools)
15
- - The Chrome DevTools MCP CLI invoked locally (via `npx -p chrome-devtools-mcp chrome-devtools <tool>` or after `npm i -g chrome-devtools-mcp`) - the user runs commands like `chrome-devtools lighthouse_audit --output-format=json` and passes the JSON output to the agent
16
-
17
- **Quick mode** - default when none of the above are available. The agent scans source code for structural anti-patterns and labels every finding as `potential impact`.
18
-
19
- ## Run the audit
20
-
21
- Delegate to the `web-performance-auditor` subagent (mention `@web-performance-auditor`). Pass it explicitly:
22
-
23
- - The files, components, or diff under review
24
- - Any artifact paths (Lighthouse JSON, PSI JSON, CrUX response, trace) or pasted JSON content
25
- - The target URL or page name when known
26
- - A note on which mode you expect (Quick or Deep), so the agent surfaces missing inputs if Deep was intended
27
-
28
- The subagent returns a scorecard (only populated with sourced values), a ranked list of findings, positive observations, and proactive recommendations.
29
-
30
- ## Output
31
-
32
- Return the full audit report to the user. No synthesis or merge step is needed - this is a single-subagent command.
@@ -1,24 +0,0 @@
1
- # Teams for /orchestrate. The main session reads this file and routes the
2
- # named team as a ROSTER (runtime-decided order), not a fixed pipeline.
3
- #
4
- # Rules the /orchestrate command relies on:
5
- # 1. First key is the default team (used when no team argument is given).
6
- # 2. researcher / deep-researcher are NOT listed — they are always available
7
- # out-of-band for NEEDS_RESEARCH dispatch (mirrors pi's spawn_research).
8
- # 3. Every listed persona must exist in .opencode/agent/ or it is skipped with
9
- # a warning.
10
- #
11
- # Switch at runtime: /orchestrate <team> "<task>" (parallels pi's /agents-team).
12
-
13
- default:
14
- - planner
15
- - builder
16
-
17
- full:
18
- - planner
19
- - plan-reviewer
20
- - builder
21
- - code-reviewer
22
-
23
- hotfix:
24
- - builder
@@ -1,22 +0,0 @@
1
- ---
2
- description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
3
- ---
4
-
5
- Load and follow the `guided-workspace-setup` skill's repair path — without running the rest of the install flow. Use this when the user wants the repair pass on its own; `/af-setup-agent-fleet` offers the same thing as soon as it finds prior install state.
6
-
7
- Run the CLI — do not walk directories or repair files yourself:
8
-
9
- ```
10
- node <source-root>/bin/cli.js doctor --workspace <workspace> [--agent <agent>] --json
11
- ```
12
-
13
- Resolve `<source-root>` from `<workspace>/.ai/.agent-fleet-bootstrap.json`, or this prompt's realpath if it is a symlink, or by asking. Never scan the filesystem for agent-fleet clones.
14
-
15
- The report has two halves, and they are repaired differently on purpose:
16
-
17
- - `repairs` — recorded items that are missing, dangling, or linked outside the source root. These are rebuilt through the same `apply()` path `install` writes with, so a repaired file is byte-identical to a freshly installed one.
18
- - `findings` — what the install record cannot own: broken symlinks in a pre-engine workspace, stale persona names in `.pi/agents/*.yaml` (`reviewer` → `code-reviewer`, `red-team` → `security-auditor`), plus advisory ones. `overrides` and `yaml-shape` findings are **advisory**: report them with "edit by hand" and never fix them, because the fix is always a hand edit of the flagged file.
19
-
20
- Print the two lists as text, then ask one `ask_user` single-select (or a plain text question without the widget) — *"Apply the suggested fixes?"* — and on yes re-run with `--fix`. An empty answer or a cancel applies nothing.
21
-
22
- Exit codes: `0` nothing to repair, `2` repairable issues found (or advisories present, or a repair failed), `1` could not run. Report the counts the CLI returns; do not invent your own.
@@ -1,19 +0,0 @@
1
- ---
2
- description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
3
- ---
4
-
5
- Load and follow the `guided-workspace-setup` skill before proceeding.
6
-
7
- Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask. Confirm the coding agent (`pi` here unless the user says otherwise).
8
-
9
- The skill is a front-end over the `agent-fleet` CLI's installer engine: `verify --json` supplies the menu (groups, profiles, per-item state), and `install` / `upgrade` / `uninstall` / `doctor --fix` do every write. **Do not copy, symlink, or delete an install target yourself** — the CLI records ownership in `.ai/agent-fleet-state.json`, and anything written by hand is invisible to every later run. The harness/extension closures (Fleet Core, the `justfile` managed region, the `.pi/agents` configs, the runtime script closure) are manifest data, so the CLI already pulls them in; you do not restate or reassemble them. Artifacts install as copies; never ask copy-vs-symlink and never pass `--method`.
10
-
11
- Two things are yours rather than the CLI's: drafting `.ai/agent-fleet-overrides.md` from a scan of the project, and the `pi-voice-stt` provider Q&A (`.ai/stt.json` names env vars; the key goes in a gitignored `.env`).
12
-
13
- **Bootstrap `pi-ask-user` first.** Before the menu, check whether the interaction package is available (bundled by `@chankov/agent-fleet`, recorded as a project package, or global). If it is missing, offer `pi install -l npm:pi-ask-user`, then **stop the pass** and ask the user to reload pi and re-run `/af-setup-agent-fleet` — the widget is not callable until then. Fall back to a text menu in this pass only if the user declines.
14
-
15
- Drive every decision through the `ask_user` widget: ≤ 9 options and ≤ 8 `context` lines per call, options carrying the data (never a table in `context`). Open with the Express question backed by the manifest's profiles; group screens run only on `Custom`; drill-ins appear only behind `Customise`. Option titles carry `<name> ★ [state]`, descriptions say what picking it does in plain words. Leaving an installed item unpicked keeps it — removal is its own explicit screen and runs `uninstall`. Cancel is a no-op everywhere except the final confirmation.
16
-
17
- If `verify` reports findings or broken items, offer `doctor --fix` before the menu — a broken workspace makes the menu lie about what is installed.
18
-
19
- Print the plan as compact action-grouped lines before confirming, then confirm with one `displayMode: "inline"` single-select: `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel`. Ask before passing `--allow-exec` (the `npm ci` steps). Exit `3` means conflicts: show the `.new` files the CLI wrote and let the user decide — never pick a side for them. Relay `operator` and `external` steps verbatim; the CLI performs neither, and neither do you.