@chankov/agent-fleet 0.0.10 → 0.0.11

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 (316) hide show
  1. package/.pi/extensions/btw/README.md +3 -2
  2. package/.pi/extensions/pi-voice-stt/README.md +3 -0
  3. package/.pi/harnesses/agent-hub/README.md +3 -0
  4. package/.pi/harnesses/agent-hub/package.json +1 -1
  5. package/.pi/harnesses/coms/package.json +1 -1
  6. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  7. package/.versions/0.0.11/.claude/commands/build.md +44 -0
  8. package/.versions/0.0.11/.claude/commands/code-simplify.md +22 -0
  9. package/.versions/0.0.11/.claude/commands/design-agent.md +14 -0
  10. package/.versions/0.0.11/.claude/commands/doctor-agent-fleet.md +22 -0
  11. package/.versions/0.0.11/.claude/commands/orchestrate.md +112 -0
  12. package/.versions/0.0.11/.claude/commands/plan.md +16 -0
  13. package/.versions/0.0.11/.claude/commands/prime.md +22 -0
  14. package/.versions/0.0.11/.claude/commands/review.md +16 -0
  15. package/.versions/0.0.11/.claude/commands/set-hermes-telegram.md +15 -0
  16. package/.versions/0.0.11/.claude/commands/set-hermes-watchdog.md +6 -0
  17. package/.versions/0.0.11/.claude/commands/setup-agent-fleet.md +17 -0
  18. package/.versions/0.0.11/.claude/commands/ship.md +72 -0
  19. package/.versions/0.0.11/.claude/commands/spec.md +15 -0
  20. package/.versions/0.0.11/.claude/commands/test.md +19 -0
  21. package/.versions/0.0.11/.claude/commands/webperf.md +32 -0
  22. package/.versions/0.0.11/.claude/orchestrate-teams.yaml +24 -0
  23. package/.versions/0.0.11/.opencode/commands/af-build.md +17 -0
  24. package/.versions/0.0.11/.opencode/commands/af-code-simplify.md +16 -0
  25. package/.versions/0.0.11/.opencode/commands/af-compound.md +16 -0
  26. package/.versions/0.0.11/.opencode/commands/af-design-agent.md +15 -0
  27. package/.versions/0.0.11/.opencode/commands/af-doctor-agent-fleet.md +22 -0
  28. package/.versions/0.0.11/.opencode/commands/af-orchestrate.md +112 -0
  29. package/.versions/0.0.11/.opencode/commands/af-plan.md +16 -0
  30. package/.versions/0.0.11/.opencode/commands/af-prime.md +22 -0
  31. package/.versions/0.0.11/.opencode/commands/af-review.md +15 -0
  32. package/.versions/0.0.11/.opencode/commands/af-set-hermes-telegram.md +15 -0
  33. package/.versions/0.0.11/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  34. package/.versions/0.0.11/.opencode/commands/af-setup-agent-fleet.md +17 -0
  35. package/.versions/0.0.11/.opencode/commands/af-ship.md +16 -0
  36. package/.versions/0.0.11/.opencode/commands/af-spec.md +16 -0
  37. package/.versions/0.0.11/.opencode/commands/af-test.md +21 -0
  38. package/.versions/0.0.11/.opencode/commands/af-webperf.md +32 -0
  39. package/.versions/0.0.11/.opencode/orchestrate-teams.yaml +24 -0
  40. package/.versions/0.0.11/.pi/agents/dispatch-policy.yaml +32 -0
  41. package/.versions/0.0.11/.pi/agents/model-profiles.yaml +27 -0
  42. package/.versions/0.0.11/.pi/agents/peers.yaml +142 -0
  43. package/.versions/0.0.11/.pi/agents/teams.yaml +41 -0
  44. package/.versions/0.0.11/.pi/damage-control-rules.yaml +297 -0
  45. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  46. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  47. package/.versions/0.0.11/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  48. package/.versions/0.0.11/.pi/extensions/btw/README.md +119 -0
  49. package/.versions/0.0.11/.pi/extensions/btw/index.ts +917 -0
  50. package/.versions/0.0.11/.pi/extensions/btw/package.json +6 -0
  51. package/.versions/0.0.11/.pi/extensions/btw/state.js +179 -0
  52. package/.versions/0.0.11/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  53. package/.versions/0.0.11/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  54. package/.versions/0.0.11/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  55. package/.versions/0.0.11/.pi/extensions/compact-and-continue/README.md +42 -0
  56. package/.versions/0.0.11/.pi/extensions/compact-and-continue/index.ts +120 -0
  57. package/.versions/0.0.11/.pi/extensions/compact-and-continue/package.json +6 -0
  58. package/.versions/0.0.11/.pi/extensions/mcp-bridge/README.md +46 -0
  59. package/.versions/0.0.11/.pi/extensions/mcp-bridge/index.ts +206 -0
  60. package/.versions/0.0.11/.pi/extensions/mcp-bridge/package.json +6 -0
  61. package/.versions/0.0.11/.pi/extensions/package-lock.json +1143 -0
  62. package/.versions/0.0.11/.pi/extensions/package.json +9 -0
  63. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/README.md +204 -0
  64. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/config.ts +198 -0
  65. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  66. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/index.ts +248 -0
  67. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/package.json +6 -0
  68. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  69. package/.versions/0.0.11/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  70. package/.versions/0.0.11/.pi/harnesses/agent-hub/README.md +1004 -0
  71. package/.versions/0.0.11/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  72. package/.versions/0.0.11/.pi/harnesses/agent-hub/artifacts.js +146 -0
  73. package/.versions/0.0.11/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  74. package/.versions/0.0.11/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  75. package/.versions/0.0.11/.pi/harnesses/agent-hub/context-window.js +106 -0
  76. package/.versions/0.0.11/.pi/harnesses/agent-hub/delegate.ts +435 -0
  77. package/.versions/0.0.11/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  78. package/.versions/0.0.11/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  79. package/.versions/0.0.11/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  80. package/.versions/0.0.11/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  81. package/.versions/0.0.11/.pi/harnesses/agent-hub/footer.ts +31 -0
  82. package/.versions/0.0.11/.pi/harnesses/agent-hub/helpers.ts +248 -0
  83. package/.versions/0.0.11/.pi/harnesses/agent-hub/index.ts +9111 -0
  84. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  85. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  86. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  87. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  88. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  89. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  90. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  91. package/.versions/0.0.11/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  92. package/.versions/0.0.11/.pi/harnesses/agent-hub/package.json +7 -0
  93. package/.versions/0.0.11/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  94. package/.versions/0.0.11/.pi/harnesses/agent-hub/research-retention.js +34 -0
  95. package/.versions/0.0.11/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  96. package/.versions/0.0.11/.pi/harnesses/agent-hub/return-contract.js +293 -0
  97. package/.versions/0.0.11/.pi/harnesses/agent-hub/return-extract.js +75 -0
  98. package/.versions/0.0.11/.pi/harnesses/agent-hub/review-findings.js +102 -0
  99. package/.versions/0.0.11/.pi/harnesses/agent-hub/run-budget.js +479 -0
  100. package/.versions/0.0.11/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  101. package/.versions/0.0.11/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  102. package/.versions/0.0.11/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  103. package/.versions/0.0.11/.pi/harnesses/agent-hub/session-health.js +110 -0
  104. package/.versions/0.0.11/.pi/harnesses/agent-hub/spawn.ts +354 -0
  105. package/.versions/0.0.11/.pi/harnesses/agent-hub/version.ts +42 -0
  106. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/README.md +19 -0
  107. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/index.ts +321 -0
  108. package/.versions/0.0.11/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  109. package/.versions/0.0.11/.pi/harnesses/coms/README.md +100 -0
  110. package/.versions/0.0.11/.pi/harnesses/coms/index.ts +1767 -0
  111. package/.versions/0.0.11/.pi/harnesses/coms/package.json +7 -0
  112. package/.versions/0.0.11/.pi/harnesses/coms/version.ts +42 -0
  113. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/README.md +124 -0
  114. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/index.ts +536 -0
  115. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/package.json +7 -0
  116. package/.versions/0.0.11/.pi/harnesses/damage-control-continue/version.ts +42 -0
  117. package/.versions/0.0.11/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  118. package/.versions/0.0.11/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  119. package/.versions/0.0.11/.pi/harnesses/lib/herdr-client.ts +472 -0
  120. package/.versions/0.0.11/.pi/harnesses/lib/herdr-presence.ts +399 -0
  121. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  122. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  123. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  124. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  125. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  126. package/.versions/0.0.11/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  127. package/.versions/0.0.11/.pi/harnesses/lib/spawned-peers.js +190 -0
  128. package/.versions/0.0.11/.pi/harnesses/package-lock.json +35 -0
  129. package/.versions/0.0.11/.pi/harnesses/package.json +9 -0
  130. package/.versions/0.0.11/.pi/prompts/af-build.md +24 -0
  131. package/.versions/0.0.11/.pi/prompts/af-code-simplify.md +22 -0
  132. package/.versions/0.0.11/.pi/prompts/af-doctor-agent-fleet.md +22 -0
  133. package/.versions/0.0.11/.pi/prompts/af-plan.md +16 -0
  134. package/.versions/0.0.11/.pi/prompts/af-review.md +16 -0
  135. package/.versions/0.0.11/.pi/prompts/af-set-hermes-telegram.md +15 -0
  136. package/.versions/0.0.11/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  137. package/.versions/0.0.11/.pi/prompts/af-setup-agent-fleet.md +19 -0
  138. package/.versions/0.0.11/.pi/prompts/af-ship.md +17 -0
  139. package/.versions/0.0.11/.pi/prompts/af-spec.md +15 -0
  140. package/.versions/0.0.11/.pi/prompts/af-test.md +19 -0
  141. package/.versions/0.0.11/.pi/skills/bowser/SKILL.md +145 -0
  142. package/.versions/0.0.11/.version +1 -0
  143. package/.versions/0.0.11/agents/architect.md +24 -0
  144. package/.versions/0.0.11/agents/bowser.md +27 -0
  145. package/.versions/0.0.11/agents/builder.md +54 -0
  146. package/.versions/0.0.11/agents/code-reviewer.md +208 -0
  147. package/.versions/0.0.11/agents/deep-researcher.md +32 -0
  148. package/.versions/0.0.11/agents/documenter.md +18 -0
  149. package/.versions/0.0.11/agents/orchestrator.md +72 -0
  150. package/.versions/0.0.11/agents/plan-reviewer.md +83 -0
  151. package/.versions/0.0.11/agents/planner.md +70 -0
  152. package/.versions/0.0.11/agents/releaser.md +24 -0
  153. package/.versions/0.0.11/agents/researcher.md +28 -0
  154. package/.versions/0.0.11/agents/security-auditor.md +167 -0
  155. package/.versions/0.0.11/agents/test-engineer.md +153 -0
  156. package/.versions/0.0.11/agents/web-debugger.md +43 -0
  157. package/.versions/0.0.11/agents/web-performance-auditor.md +193 -0
  158. package/.versions/0.0.11/codex/CONDUCTOR.md +148 -0
  159. package/.versions/0.0.11/docs/ARCHITECTURE.md +303 -0
  160. package/.versions/0.0.11/docs/agent-fleet-setup.md +377 -0
  161. package/.versions/0.0.11/docs/claude-code-coms-bridge.md +109 -0
  162. package/.versions/0.0.11/docs/codex-remote-conductor.md +170 -0
  163. package/.versions/0.0.11/docs/coms-hermes-bridge.md +189 -0
  164. package/.versions/0.0.11/docs/getting-started.md +254 -0
  165. package/.versions/0.0.11/docs/npm-install.md +514 -0
  166. package/.versions/0.0.11/docs/opencode-setup.md +281 -0
  167. package/.versions/0.0.11/docs/pi-extensions.md +368 -0
  168. package/.versions/0.0.11/docs/pi-setup.md +571 -0
  169. package/.versions/0.0.11/docs/skill-anatomy.md +150 -0
  170. package/.versions/0.0.11/hermes/README.md +347 -0
  171. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  172. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  173. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  174. package/.versions/0.0.11/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  175. package/.versions/0.0.11/hermes/gates/gate-o-capability.md +8 -0
  176. package/.versions/0.0.11/hermes/gates/gate-o-validator-fixtures.json +1 -0
  177. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  178. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  179. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  180. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  181. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  182. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  183. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  184. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  185. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  186. package/.versions/0.0.11/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  187. package/.versions/0.0.11/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  188. package/.versions/0.0.11/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  189. package/.versions/0.0.11/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  190. package/.versions/0.0.11/hermes/skills/hub-conductor/SKILL.md +84 -0
  191. package/.versions/0.0.11/hermes/skills/hub-liaison/SKILL.md +84 -0
  192. package/.versions/0.0.11/hermes/skills/hub-watchdog/SKILL.md +76 -0
  193. package/.versions/0.0.11/hermes/skills/hub-watchdog/manifest.json +1 -0
  194. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  195. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  196. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  197. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  198. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  199. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  200. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  201. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  202. package/.versions/0.0.11/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  203. package/.versions/0.0.11/hermes/watchdog-tests/__init__.py +0 -0
  204. package/.versions/0.0.11/hooks/SIMPLIFY-IGNORE.md +90 -0
  205. package/.versions/0.0.11/hooks/coms-stop-hook.mjs +84 -0
  206. package/.versions/0.0.11/hooks/hooks.json +14 -0
  207. package/.versions/0.0.11/hooks/session-start.sh +74 -0
  208. package/.versions/0.0.11/hooks/simplify-ignore.sh +302 -0
  209. package/.versions/0.0.11/install-manifest.json +3615 -0
  210. package/.versions/0.0.11/justfile +254 -0
  211. package/.versions/0.0.11/manifest-meta.json +472 -0
  212. package/.versions/0.0.11/references/accessibility-checklist.md +160 -0
  213. package/.versions/0.0.11/references/definition-of-done.md +67 -0
  214. package/.versions/0.0.11/references/fleet-coordination-patterns.md +151 -0
  215. package/.versions/0.0.11/references/observability-checklist.md +91 -0
  216. package/.versions/0.0.11/references/orchestration-patterns.md +370 -0
  217. package/.versions/0.0.11/references/performance-checklist.md +153 -0
  218. package/.versions/0.0.11/references/prompting-patterns.md +380 -0
  219. package/.versions/0.0.11/references/security-checklist.md +179 -0
  220. package/.versions/0.0.11/references/testing-patterns.md +236 -0
  221. package/.versions/0.0.11/scripts/codex-conductor.ts +41 -0
  222. package/.versions/0.0.11/scripts/codex-remote-control.ts +167 -0
  223. package/.versions/0.0.11/scripts/coms-claude-bridge.ts +401 -0
  224. package/.versions/0.0.11/scripts/coms-cli.ts +484 -0
  225. package/.versions/0.0.11/scripts/coms-hermes-bridge.ts +413 -0
  226. package/.versions/0.0.11/scripts/fleet.ts +168 -0
  227. package/.versions/0.0.11/scripts/hermes-monitor-capability-runner.ts +25 -0
  228. package/.versions/0.0.11/scripts/hermes-monitor-scenario.ts +474 -0
  229. package/.versions/0.0.11/scripts/hermes-watchdog-capability-probe.ts +45 -0
  230. package/.versions/0.0.11/scripts/install-hermes-plugin.sh +180 -0
  231. package/.versions/0.0.11/scripts/lib/claude-bridge-core.ts +165 -0
  232. package/.versions/0.0.11/scripts/lib/codex-conductor.ts +88 -0
  233. package/.versions/0.0.11/scripts/lib/codex-remote-control.ts +480 -0
  234. package/.versions/0.0.11/scripts/lib/coms-envelope.ts +582 -0
  235. package/.versions/0.0.11/scripts/lib/fake-herdr-server.ts +88 -0
  236. package/.versions/0.0.11/scripts/lib/fleet-command.ts +111 -0
  237. package/.versions/0.0.11/scripts/lib/herdr-layout.ts +281 -0
  238. package/.versions/0.0.11/scripts/lib/hermes-bridge-core.ts +241 -0
  239. package/.versions/0.0.11/scripts/lib/hermes-monitor-events.ts +1 -0
  240. package/.versions/0.0.11/scripts/lib/hermes-monitor-herdr.ts +2 -0
  241. package/.versions/0.0.11/scripts/lib/hermes-monitor-model.ts +3 -0
  242. package/.versions/0.0.11/scripts/lib/hermes-monitor-registry.ts +2 -0
  243. package/.versions/0.0.11/scripts/lib/hermes-monitor-socket.ts +2 -0
  244. package/.versions/0.0.11/scripts/lib/hermes-monitor-store.ts +2 -0
  245. package/.versions/0.0.11/scripts/lib/monitor-env.ts +134 -0
  246. package/.versions/0.0.11/scripts/lib/peer-launch.ts +314 -0
  247. package/.versions/0.0.11/scripts/lib/persona-banner.ts +62 -0
  248. package/.versions/0.0.11/scripts/lib/spawn-stagger.ts +101 -0
  249. package/.versions/0.0.11/scripts/lib/team-project.ts +193 -0
  250. package/.versions/0.0.11/scripts/lib/team-snapshot.ts +147 -0
  251. package/.versions/0.0.11/scripts/peer-banner.ts +40 -0
  252. package/.versions/0.0.11/scripts/peer-launch.ts +259 -0
  253. package/.versions/0.0.11/scripts/team-snapshot.ts +237 -0
  254. package/.versions/0.0.11/scripts/team-up.ts +360 -0
  255. package/.versions/0.0.11/skills/_internal/grilling.md +11 -0
  256. package/.versions/0.0.11/skills/browser-testing-with-devtools/SKILL.md +351 -0
  257. package/.versions/0.0.11/skills/code-review-and-quality/SKILL.md +381 -0
  258. package/.versions/0.0.11/skills/compound-learning/SKILL.md +137 -0
  259. package/.versions/0.0.11/skills/context-engineering/SKILL.md +291 -0
  260. package/.versions/0.0.11/skills/deprecation-and-migration/SKILL.md +206 -0
  261. package/.versions/0.0.11/skills/designing-agents/SKILL.md +394 -0
  262. package/.versions/0.0.11/skills/designing-agents/pi-harness-authoring.md +222 -0
  263. package/.versions/0.0.11/skills/frontend-ui-engineering/SKILL.md +328 -0
  264. package/.versions/0.0.11/skills/git-workflow-and-versioning/SKILL.md +316 -0
  265. package/.versions/0.0.11/skills/guided-workspace-setup/SKILL.md +226 -0
  266. package/.versions/0.0.11/skills/guided-workspace-setup/companion-manifest.json +38 -0
  267. package/.versions/0.0.11/skills/idea-refine/SKILL.md +182 -0
  268. package/.versions/0.0.11/skills/idea-refine/examples.md +238 -0
  269. package/.versions/0.0.11/skills/idea-refine/frameworks.md +99 -0
  270. package/.versions/0.0.11/skills/idea-refine/refinement-criteria.md +113 -0
  271. package/.versions/0.0.11/skills/idea-refine/scripts/idea-refine.sh +15 -0
  272. package/.versions/0.0.11/skills/incremental-implementation/SKILL.md +287 -0
  273. package/.versions/0.0.11/skills/interview-me/SKILL.md +226 -0
  274. package/.versions/0.0.11/skills/orchestration-verification/SKILL.md +181 -0
  275. package/.versions/0.0.11/skills/peer-coms/SKILL.md +90 -0
  276. package/.versions/0.0.11/skills/performance-optimization/SKILL.md +350 -0
  277. package/.versions/0.0.11/skills/planning-and-task-breakdown/SKILL.md +254 -0
  278. package/.versions/0.0.11/skills/security-and-hardening/SKILL.md +461 -0
  279. package/.versions/0.0.11/skills/spec-driven-development/SKILL.md +257 -0
  280. package/.versions/0.0.11/skills/using-agent-skills/SKILL.md +199 -0
  281. package/.versions/0.0.11/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  282. package/.versions/0.0.11/vendor/agent-skills-upstream/LICENSE +21 -0
  283. package/.versions/0.0.11/vendor/agent-skills-upstream/README.md +11 -0
  284. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  285. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  286. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  287. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  288. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  289. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  290. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  291. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  292. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  293. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  294. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  295. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  296. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  297. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  298. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  299. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  300. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  301. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  302. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  303. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  304. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  305. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  306. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  307. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  308. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  309. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  310. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  311. package/.versions/0.0.11/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  312. package/CHANGELOG.md +7 -0
  313. package/docs/pi-extensions.md +5 -0
  314. package/install-manifest.json +1 -1
  315. package/package.json +1 -1
  316. package/scripts/lib/monitor-env.ts +15 -1
@@ -0,0 +1,226 @@
1
+ ---
2
+ name: guided-workspace-setup
3
+ description: Guides installation of agent-fleet artifacts into a target workspace. Use when onboarding a project to agent-fleet, when installing skills, commands, prompts, personas, or pi extensions for a chosen coding agent, or when a workspace needs its setup files configured.
4
+ ---
5
+
6
+ # Guided Workspace Setup
7
+
8
+ ## Overview
9
+
10
+ A conversational front-end over the `agent-fleet` CLI's deterministic installer. The CLI decides
11
+ paths, states, merges, ownership, and writes — this skill asks the questions a program cannot
12
+ answer: which artifacts this project wants, what belongs in its overrides file, and which speech
13
+ provider to configure. Everything else is `agent-fleet <verb> --json`.
14
+
15
+ **You never write an install target yourself.** No copying, no symlinking, no path tables, no
16
+ merge rules. If you find yourself about to write into `.claude/`, `.opencode/`, `.pi/`, or the
17
+ `justfile`, you are in the wrong place — call the CLI.
18
+
19
+ ## When to Use
20
+
21
+ - Onboarding a project to agent-fleet, or changing which artifacts it uses
22
+ - Re-running setup to add, upgrade, repair, or remove artifacts
23
+ - Authoring or revising `.ai/agent-fleet-overrides.md`
24
+
25
+ **NOT for:** authoring new skills or personas (`designing-agents`); editing artifacts inside the
26
+ agent-fleet repo itself; general rules-file tuning (`context-engineering`).
27
+
28
+ ## Process
29
+
30
+ ### 1. Resolve the source root and agent
31
+
32
+ Run the CLI from the agent-fleet package the user actually installed:
33
+
34
+ 1. `<workspace>/.ai/.agent-fleet-bootstrap.json` → its `sourceRoot`. Authoritative; written by
35
+ `npx @chankov/agent-fleet init`. If the path no longer exists, say so and go to 3.
36
+ 2. This `SKILL.md`'s realpath, if it is a symlink. Never its *workspace* location — bootstrap
37
+ copies the file into `.pi/skills/…`, so that path is the target, not the source.
38
+ 3. Ask. **Never scan the filesystem for agent-fleet clones** — it finds forks and stale checkouts,
39
+ not the package the user installed from.
40
+
41
+ Confirm the workspace path exists. The agent (`claude-code` / `opencode` / `pi`) comes from the
42
+ recorded state; pass `--agent` only to override it.
43
+
44
+ ### 2. Read the workspace's current state
45
+
46
+ ```
47
+ node <source-root>/bin/cli.js verify --workspace <workspace> [--agent <agent>] --json
48
+ ```
49
+
50
+ One command, everything you need: `groups` (menu headings, agent-filtered), `profiles` (the
51
+ shortcuts), and `items` — each with `id`, `group`, `subcategory`, `title`, `summary`,
52
+ `recommended`, `consent`, `owned`, and `state`. Plus `findings`, `recordedVersion`, and
53
+ `summary.versionDrift`.
54
+
55
+ The states are the CLI's, not yours: `absent`, `up-to-date`, `linked`, `outdated`, `modified`,
56
+ `conflict`, `missing`, `broken-link`, `foreign-link`, `partial`, `gone`, `not-applicable`.
57
+ Do not compute, guess, or re-derive them.
58
+
59
+ If `findings` is non-empty or any item is broken, offer `doctor --fix` before the menu — a broken
60
+ workspace makes the menu lie about what is installed.
61
+
62
+ ### 3. Ask what to install
63
+
64
+ Present the `items` grouped by `group`, chunked by `subcategory`. Interaction mode:
65
+
66
+ - **pi** → the `ask_user` widget from the external `pi-ask-user` package. If it is missing, offer
67
+ to install it (`pi install -l npm:pi-ask-user`), then **stop the pass** and ask the user to
68
+ reload and re-run — the widget is not callable until then. If they decline, use the text
69
+ fallback.
70
+ - **claude-code** → `AskUserQuestion` (max 4 options per call).
71
+ - **anything else** → print a compact table and take a text reply.
72
+
73
+ Screen budget: ≤ 8 context lines, ≤ 9 options per call (≤ 4 on `AskUserQuestion`). Options carry
74
+ the data — `{title, description}`, never a table pasted into `context`. Titles are
75
+ `<title> ★ [state]`; descriptions say what picking it does in plain words ("update available",
76
+ "locally modified — installing overwrites your edits"). Long material (diffs, changelog, the plan)
77
+ prints as agent text *before* the call, with `displayMode: "inline"` so it stays visible.
78
+
79
+ Open with one Express single-select that can resolve the whole menu — the `profiles` map supplies
80
+ the shortcuts (`recommended`, `full`, `minimal`, `pi-fleet-core`, …). Group screens run only on
81
+ `Custom`. Cancel is a no-op everywhere except the final confirmation.
82
+
83
+ **Selection never removes.** Leaving an installed item unpicked keeps it. Removal is its own
84
+ explicit screen, and it runs `uninstall --items`.
85
+
86
+ ### 4. Offer project overrides *(this is genuinely yours)*
87
+
88
+ Scan the workspace — language, framework, test runner, dev server, rule-file trees, doc entry
89
+ points — and propose draft sections for `.ai/agent-fleet-overrides.md`:
90
+ `spec-driven-development`, `planning-and-task-breakdown`, `browser-testing-with-devtools`,
91
+ `git-workflow-and-versioning`, and for `pi` with `agent-hub` selected, `## agent-hub` (a legacy
92
+ `## agent-team` section keeps its name — preserve, never duplicate).
93
+
94
+ In `## agent-hub`, offer `language:` (default `English`, preserving any existing value) and the
95
+ project-knowledge keys **only when the scan finds matching material** — `rules:` for a rule-file
96
+ tree (`.ai/rules/`, `docs/rules/`, `.cursor/rules/`; point at the tree root, which resolves
97
+ index-first), `docs:` for canonical WHAT/WHY entry points. An empty guess sends every specialist
98
+ hunting for files that are not there.
99
+
100
+ Terse `key: value` lines only — the lifecycle skills and `agent-hub` parse this file on every run.
101
+ Reference env-var *names*; secrets stay in a gitignored `.env`. When any section names env vars,
102
+ offer an `## env` section with `required: <NAME>[, <NAME>]`. Schema: `docs/agent-fleet-setup.md`.
103
+
104
+ Print each draft as agent text, then ask `Accept` / `Edit` / `Skip` per section (or one
105
+ multi-select when there are more than two). This file is yours to write directly — it is not an
106
+ install target.
107
+
108
+ ### 5. Configure `pi-voice-stt`, if selected *(also genuinely yours)*
109
+
110
+ The extension is a no-op until a provider is configured, and the CLI reports it as an operator
111
+ step rather than inventing one. Offer — never force — the Q&A:
112
+
113
+ - **Azure Speech** (`type: azure`) — resource endpoint, optional `locales` for per-phrase language
114
+ ID (e.g. `["bg-BG","en-US"]`). Env: `AZURE_SPEECH_KEY`, `AZURE_SPEECH_ENDPOINT`.
115
+ - **Azure OpenAI Whisper** (`type: azure-openai`) — best for mixed-language speech. `endpoint`,
116
+ Whisper `deployment`, `apiVersion` (default `2024-10-21`). Use the legacy data-plane host
117
+ `https://<resource>.openai.azure.com` (or `…cognitiveservices.azure.com`) — transcription 404s
118
+ on the Foundry `…services.ai.azure.com` host. Env: `AZURE_OPENAI_API_KEY`,
119
+ `AZURE_OPENAI_ENDPOINT`; offer `apiKeyEnv: AZURE_SPEECH_KEY` when the key is shared.
120
+ - **OpenAI-compatible** (`type: openai`) — `baseUrl` (default `https://api.openai.com/v1`; a
121
+ `http://127.0.0.1:*/v1` loopback is fine for local whisper), `model` (default `whisper-1`).
122
+ Env: `OPENAI_API_KEY`.
123
+
124
+ Write `<workspace>/.ai/stt.json` with the non-secret config and `apiKeyEnv` — **never a key
125
+ value** — and append the referenced names to the repo-root `.env` as empty placeholders only if
126
+ absent, never overwriting. Ensure `.env` is gitignored. On removal, delete `stt.json` only if
127
+ unedited; never touch `.env`.
128
+
129
+ ### 6. Apply
130
+
131
+ ```
132
+ node <source-root>/bin/cli.js install --workspace <ws> --agent <a> \
133
+ --profile <name> | --items <id,…> [--allow-exec] --yes --json
134
+ ```
135
+
136
+ `upgrade` for a version bump (three-way merge, preserves local edits, `--accept-theirs` /
137
+ `--accept-ours` for conflicts), `uninstall --items <id,…>` for removals, `doctor --fix` for
138
+ repairs. Add `--dry-run` first when the user wants to see the plan; `--json` requires `--yes`.
139
+
140
+ Print the plan as compact action-grouped lines before the confirm — `Add (N): …`,
141
+ `Refresh (N): …` (append *overwrites local edits* when the plan reports `overwrites`),
142
+ `Remove (N): …`, `Keep (N)` as a count, `Method:`. When `versionDrift` is set, lead with
143
+ **"Changes since v<recorded> → v<current>"** and short bullets from `CHANGELOG.md`. Then one
144
+ `inline` single-select: `Apply — and remove the installer commands` (default) /
145
+ `Apply — keep the installer commands` / `Adjust picks` / `Cancel`.
146
+
147
+ Exit codes are the contract: `0` done, `1` error, `2` findings, `3` conflicts. On `3`, the CLI
148
+ wrote `<file>.new` beside each conflicted file and touched nothing else — show the list and let
149
+ the user resolve, or re-run with `--accept-theirs` / `--accept-ours`.
150
+
151
+ Artifacts install as copies. There is no copy-vs-symlink question to ask — symlinks exist only
152
+ inside an agent-fleet checkout, and a workspace that recorded them before that is migrated to
153
+ copies by the CLI on this run. Never offer the choice, and never pass `--method`.
154
+
155
+ `--allow-exec` covers the `npm ci` steps for `.pi/extensions` and `.pi/harnesses`; ask before
156
+ passing it. `external` and `operator` actions carry their own instructions in the plan output —
157
+ relay them verbatim; the CLI performs none of them, and neither do you.
158
+
159
+ ### 7. Clean up and report
160
+
161
+ Unless the user chose to keep them:
162
+
163
+ ```
164
+ node <source-root>/bin/cli.js cleanup-installer --agent <agent> --workspace <workspace>
165
+ ```
166
+
167
+ Then `verify` once more and report what changed, plus the one-line cleanup outcome
168
+ ("Installer slash commands removed — `npx @chankov/agent-fleet init` restores them", or the
169
+ retained command names). Point the user at `.ai/agent-fleet-overrides.md` and suggest loading
170
+ `using-agent-skills` first next session.
171
+
172
+ ## Common Rationalizations
173
+
174
+ | Rationalization | Reality |
175
+ |---|---|
176
+ | "I'll copy this one file myself — calling the CLI for it is overkill." | Then it is not recorded in `.ai/agent-fleet-state.json`, so `verify` calls it unowned, `upgrade` skips it, and `uninstall` refuses to remove it. The state file is what makes any of this reversible. |
177
+ | "The installed file looks different from the source, so it's modified." | `modified`, `outdated`, and `conflict` are three different answers with three different consequences, and they need the recorded hash and the version snapshot to tell apart. Read `state` from `verify --json`. |
178
+ | "The user picked a narrower profile, so I'll remove what's no longer in it." | Selection never removes. Removal is `uninstall` with named items, and only after an explicit remove screen. |
179
+ | "The plan says `conflict` — I'll take the new version, it's newer." | Exit `3` means both sides changed. The `.new` file exists so a human decides. `--accept-theirs` is the user's call to make, not yours. |
180
+ | "I'll run `npm ci` for the extensions — it's obviously needed." | It is an `exec` item, gated on `--allow-exec`. Running commands in someone's repo is a consent boundary, not a formality. |
181
+ | "The Hermes plugin just needs a symlink into the profile directory — I can do that." | Operator items exist because their targets are outside the workspace: a Hermes profile, a user systemd unit, a running gateway. Relay the declared steps; perform none of them. |
182
+ | "The user is on `pi` and `pi-ask-user` is missing — I'll use the text fallback." | Offer the install-then-reload bootstrap first. A ~50-row menu through plain text is the experience that widget exists to replace. Fall back only if they decline. |
183
+ | "I installed `pi-ask-user`, so I'll keep going in the same pass." | It is not callable until pi reloads. Stop, ask them to reload and re-run. |
184
+ | "The user didn't tick that installed item in the drill-in, so remove it." | Not selecting means keep as-is. An accidental non-pick must never delete anything. |
185
+ | "They pressed `esc` — I'll take the defaults and continue." | Cancel is skip/no-op on every screen except the final confirm, where it means do not apply. |
186
+ | "I'll write the install detail into the overrides file too — one place is simpler." | Every skill and every `agent-hub` session loads the overrides file. Install detail lives in the state file, which nothing loads at runtime. |
187
+ | "There's no rule-file tree, but `rules:` looks incomplete without a value." | An invented path sends every specialist hunting for files that do not exist. Skip the key. |
188
+ | "The user asked for symlinks so `git pull` updates everything." | Symlinks are checkout-only now: outside one, the link target has to stay put forever, an npx cache clean breaks every link at once, and a source `git pull` rewrites artifacts nobody agreed to change. `agent-fleet upgrade` gives the same freshness with a real three-way merge. Say that, don't pass `--method`. |
189
+ | "I'll put the Azure key in `stt.json` — it's in `.ai/`, that's fine." | `.ai/` is committed. The config names an env var; the value lives in a gitignored `.env`. |
190
+
191
+ ## Red Flags
192
+
193
+ - Any write by this skill into `.claude/`, `.opencode/`, `.pi/`, `agents/`, or the `justfile` —
194
+ those are the CLI's, exclusively. Only `.ai/agent-fleet-overrides.md` and `.ai/stt.json` are yours.
195
+ - An item state computed by eye instead of read from `verify --json`.
196
+ - A path table, merge rule, or removal-ownership rule restated in the conversation — all three
197
+ live in code, and a second copy will drift from it.
198
+ - `--json` used without `--yes`, or a plan applied without printing it first.
199
+ - A markdown table pasted into a widget call's `question` or `context`, or a screen over budget.
200
+ - The `pi-ask-user` bootstrap skipped on `pi`, or the pass continued after installing it.
201
+ - An artifact removed without an explicit remove screen, or `esc` treated as consent.
202
+ - Exit `3` handled by picking a side instead of showing the `.new` files.
203
+ - `operator` or `external` steps performed instead of relayed.
204
+ - A key value written into `.ai/stt.json`, or `.env` overwritten rather than appended to.
205
+ - Source root found by scanning the filesystem, or taken from `SKILL.md`'s workspace location.
206
+
207
+ ## Verification
208
+
209
+ - [ ] Source root came from the bootstrap marker, `SKILL.md`'s realpath, or the user — never a scan.
210
+ - [ ] Every item state, group, and profile came from `verify --json`.
211
+ - [ ] Broken items and findings were offered `doctor --fix` before the menu.
212
+ - [ ] The menu opened with the Express question; group screens ran only on `Custom`; every screen
213
+ stayed within budget, with options carrying the data.
214
+ - [ ] On `pi`, `pi-ask-user` was present or its install-then-reload bootstrap was offered, and the
215
+ pass stopped after installing it.
216
+ - [ ] Nothing was written to an install target except by the CLI, and the plan was printed before
217
+ the single confirmation.
218
+ - [ ] `--allow-exec` was passed only after asking; `operator` / `external` steps were relayed verbatim.
219
+ - [ ] No copy-vs-symlink question was asked and no `--method` flag was passed.
220
+ - [ ] A `3` exit was surfaced as conflicts with their `.new` files, not resolved by guessing.
221
+ - [ ] `.ai/agent-fleet-overrides.md` holds terse `key: value` sections and nothing else; `rules:` /
222
+ `docs:` were offered only when the scan found matching material.
223
+ - [ ] `.ai/stt.json` names env vars and holds no key values; `.env` was appended to, gitignored,
224
+ and never overwritten.
225
+ - [ ] `cleanup-installer` ran unless the user kept the installer commands, and the report says which.
226
+ - [ ] The final `verify` exited `0`.
@@ -0,0 +1,38 @@
1
+ {
2
+ "version": 1,
3
+ "description": "Runtime closure refreshed with any pi harness selection. Paths are repository-relative and contain no user configuration or credentials.",
4
+ "directories": [
5
+ "codex",
6
+ "hermes/skills",
7
+ "systemd"
8
+ ],
9
+ "files": [
10
+ "justfile",
11
+ "docs/ARCHITECTURE.md",
12
+ "docs/codex-remote-conductor.md",
13
+ "docs/coms-hermes-bridge.md",
14
+ "scripts/codex-conductor.ts",
15
+ "scripts/codex-remote-control.ts",
16
+ "scripts/coms-claude-bridge.ts",
17
+ "scripts/coms-cli.ts",
18
+ "scripts/coms-hermes-bridge.ts",
19
+ "scripts/fleet.ts",
20
+ "scripts/peer-banner.ts",
21
+ "scripts/peer-launch.ts",
22
+ "scripts/team-snapshot.ts",
23
+ "scripts/team-up.ts",
24
+ "scripts/lib/claude-bridge-core.ts",
25
+ "scripts/lib/codex-conductor.ts",
26
+ "scripts/lib/codex-remote-control.ts",
27
+ "scripts/lib/coms-envelope.ts",
28
+ "scripts/lib/fleet-command.ts",
29
+ "scripts/lib/herdr-layout.ts",
30
+ "scripts/lib/hermes-bridge-core.ts",
31
+ "scripts/lib/monitor-env.ts",
32
+ "scripts/lib/peer-launch.ts",
33
+ "scripts/lib/persona-banner.ts",
34
+ "scripts/lib/spawn-stagger.ts",
35
+ "scripts/lib/team-project.ts",
36
+ "scripts/lib/team-snapshot.ts"
37
+ ]
38
+ }
@@ -0,0 +1,182 @@
1
+ ---
2
+ name: idea-refine
3
+ description: Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", "stress-test my plan", or "grill this".
4
+ ---
5
+
6
+ # Idea Refine
7
+
8
+ Refines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.
9
+
10
+ ## How It Works
11
+
12
+ 1. **Understand & Expand (Divergent):** Restate the idea, ask sharpening questions, and generate variations.
13
+ 2. **Evaluate & Converge:** Cluster ideas, stress-test them, and surface hidden assumptions.
14
+ 3. **Sharpen & Ship:** Produce a concrete markdown one-pager moving work forward.
15
+
16
+ ## Usage
17
+
18
+ This skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.
19
+
20
+ ```bash
21
+ # Optional: Initialize the ideas directory
22
+ bash /mnt/skills/user/idea-refine/scripts/idea-refine.sh
23
+ ```
24
+
25
+ **Trigger Phrases:**
26
+ - "Help me refine this idea"
27
+ - "Ideate on [concept]"
28
+ - "Stress-test my plan"
29
+ - "Grill this plan"
30
+
31
+ ## Output
32
+
33
+ The final output is a markdown one-pager saved to `docs/ideas/[idea-name].md` (after user confirmation), containing:
34
+ - Problem Statement
35
+ - Recommended Direction
36
+ - Key Assumptions
37
+ - MVP Scope
38
+ - Not Doing list
39
+
40
+ ## Detailed Instructions
41
+
42
+ You are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.
43
+
44
+ ### Philosophy
45
+
46
+ - Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.
47
+ - Start with the user experience, work backwards to technology.
48
+ - Say no to 1,000 things. Focus beats breadth.
49
+ - Challenge every assumption. "How it's usually done" is not a reason.
50
+ - Show people the future — don't just give them better horses.
51
+ - The parts you can't see should be as beautiful as the parts you can.
52
+
53
+ ### Process
54
+
55
+ When the user invokes this skill with an idea (`$ARGUMENTS`), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.
56
+
57
+ #### Phase 1: Understand & Expand (Divergent)
58
+
59
+ **Goal:** Take the raw idea and open it up. If the invocation is specifically a grill/stress-test request for an existing plan, read the shared internal helper at [`../_internal/grilling.md`](../_internal/grilling.md) after any needed codebase scan and ask one decision question at a time instead of batching sharpening questions.
60
+
61
+ 1. **Restate the idea** as a crisp "How Might We" problem statement. This forces clarity on what's actually being solved.
62
+
63
+ 2. **Ask 3-5 sharpening questions** — no more. Focus on:
64
+ - Who is this for, specifically?
65
+ - What does success look like?
66
+ - What are the real constraints (time, tech, resources)?
67
+ - What's been tried before?
68
+ - Why now?
69
+
70
+ Use the `AskUserQuestion` tool to gather this input. Do NOT proceed until you understand who this is for and what success looks like.
71
+
72
+ 3. **Generate 5-8 idea variations** using these lenses:
73
+ - **Inversion:** "What if we did the opposite?"
74
+ - **Constraint removal:** "What if budget/time/tech weren't factors?"
75
+ - **Audience shift:** "What if this were for [different user]?"
76
+ - **Combination:** "What if we merged this with [adjacent idea]?"
77
+ - **Simplification:** "What's the version that's 10x simpler?"
78
+ - **10x version:** "What would this look like at massive scale?"
79
+ - **Expert lens:** "What would [domain] experts find obvious that outsiders wouldn't?"
80
+
81
+ Push beyond what the user initially asked for. Create products people don't know they need yet.
82
+
83
+ **If running inside a codebase:** Use `Glob`, `Grep`, and `Read` to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.
84
+
85
+ Read `frameworks.md` in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.
86
+
87
+ #### Phase 2: Evaluate & Converge
88
+
89
+ After the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode.
90
+
91
+ **Grilling mode:** If the user asks to "grill" or stress-test a specific plan/design, read the shared internal helper at [`../_internal/grilling.md`](../_internal/grilling.md) and use that one-question-at-a-time decision interview before producing the one-pager. Treat the answers as inputs to Key Assumptions, MVP Scope, Not Doing, and Open Questions.
92
+
93
+ 1. **Cluster** the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.
94
+
95
+ 2. **Stress-test** each direction against three criteria:
96
+ - **User value:** Who benefits and how much? Is this a painkiller or a vitamin?
97
+ - **Feasibility:** What's the technical and resource cost? What's the hardest part?
98
+ - **Differentiation:** What makes this genuinely different? Would someone switch from their current solution?
99
+
100
+ Read `refinement-criteria.md` in this skill directory for the full evaluation rubric.
101
+
102
+ 3. **Surface hidden assumptions.** For each direction, explicitly name:
103
+ - What you're betting is true (but haven't validated)
104
+ - What could kill this idea
105
+ - What you're choosing to ignore (and why that's okay for now)
106
+
107
+ This is where most ideation fails. Don't skip it.
108
+
109
+ **Be honest, not supportive.** If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.
110
+
111
+ #### Phase 3: Sharpen & Ship
112
+
113
+ Produce a concrete artifact — a markdown one-pager that moves work forward:
114
+
115
+ ```markdown
116
+ # [Idea Name]
117
+
118
+ ## Problem Statement
119
+ [One-sentence "How Might We" framing]
120
+
121
+ ## Recommended Direction
122
+ [The chosen direction and why — 2-3 paragraphs max]
123
+
124
+ ## Key Assumptions to Validate
125
+ - [ ] [Assumption 1 — how to test it]
126
+ - [ ] [Assumption 2 — how to test it]
127
+ - [ ] [Assumption 3 — how to test it]
128
+
129
+ ## MVP Scope
130
+ [The minimum version that tests the core assumption. What's in, what's out.]
131
+
132
+ ## Not Doing (and Why)
133
+ - [Thing 1] — [reason]
134
+ - [Thing 2] — [reason]
135
+ - [Thing 3] — [reason]
136
+
137
+ ## Open Questions
138
+ - [Question that needs answering before building]
139
+ ```
140
+
141
+ **The "Not Doing" list is arguably the most valuable part.** Focus is about saying no to good ideas. Make the trade-offs explicit.
142
+
143
+ Ask the user if they'd like to save this to `docs/ideas/[idea-name].md` (or a location of their choosing). Only save if they confirm.
144
+
145
+ ### Anti-patterns to Avoid
146
+
147
+ - **Don't generate 20+ ideas.** Quality over quantity. 5-8 well-considered variations beat 20 shallow ones.
148
+ - **Don't be a yes-machine.** Push back on weak ideas with specificity and kindness.
149
+ - **Don't skip "who is this for."** Every good idea starts with a person and their problem.
150
+ - **Don't produce a plan without surfacing assumptions.** Untested assumptions are the #1 killer of good ideas.
151
+ - **Don't over-engineer the process.** Three phases, each doing one thing well. Resist adding steps.
152
+ - **Don't just list ideas — tell a story.** Each variation should have a reason it exists, not just be a bullet point.
153
+ - **Don't ignore the codebase.** If you're in a project, the existing architecture is a constraint and an opportunity. Use it.
154
+
155
+ ### Tone
156
+
157
+ Direct, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of "that's interesting, but what if..." -- always pushing one step further without being exhausting.
158
+
159
+ Read `examples.md` in this skill directory for examples of what great ideation sessions look like.
160
+
161
+ ## Red Flags
162
+
163
+ - Generating 20+ shallow variations instead of 5-8 considered ones
164
+ - Skipping the "who is this for" question
165
+ - No assumptions surfaced before committing to a direction
166
+ - Yes-machining weak ideas instead of pushing back with specificity
167
+ - Producing a plan without a "Not Doing" list
168
+ - Ignoring existing codebase constraints when ideating inside a project
169
+ - Jumping straight to Phase 3 output without running Phases 1 and 2
170
+
171
+ ## Verification
172
+
173
+ After completing an ideation session:
174
+
175
+ - [ ] A clear "How Might We" problem statement exists
176
+ - [ ] The target user and success criteria are defined
177
+ - [ ] Multiple directions were explored, not just the first idea
178
+ - [ ] Hidden assumptions are explicitly listed with validation strategies
179
+ - [ ] If grilling was invoked, decisions were resolved one at a time and reflected in the one-pager
180
+ - [ ] A "Not Doing" list makes trade-offs explicit
181
+ - [ ] The output is a concrete artifact (markdown one-pager), not just conversation
182
+ - [ ] The user confirmed the final direction before any implementation work