@chankov/agent-fleet 2.0.9 → 2.0.10

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 (465) hide show
  1. package/.pi/extensions/pi-voice-stt/README.md +24 -5
  2. package/.pi/extensions/pi-voice-stt/examples/stt.json +4 -4
  3. package/.pi/harnesses/agent-hub/package.json +1 -1
  4. package/.pi/harnesses/agent-hub/return-contract.js +34 -0
  5. package/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +80 -18
  6. package/.pi/harnesses/coms/package.json +1 -1
  7. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  8. package/.pi/harnesses/lib/changed-file-diagnostics.ts +642 -0
  9. package/.versions/2.0.10/.pi/agent-fleet/hermes/README.md +347 -0
  10. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  11. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  12. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  13. package/.versions/2.0.10/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  14. package/.versions/2.0.10/.pi/agent-fleet/hermes/gates/gate-o-capability.md +8 -0
  15. package/.versions/2.0.10/.pi/agent-fleet/hermes/gates/gate-o-validator-fixtures.json +1 -0
  16. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +773 -0
  17. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  18. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  19. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  20. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  21. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  22. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  23. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  24. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  25. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  26. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  27. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  28. package/.versions/2.0.10/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  29. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-conductor/SKILL.md +84 -0
  30. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-liaison/SKILL.md +84 -0
  31. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md +76 -0
  32. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/manifest.json +1 -0
  33. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  34. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  35. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  36. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  37. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  38. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  39. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  40. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  41. package/.versions/2.0.10/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  42. package/.versions/2.0.10/.pi/agent-fleet/hermes/watchdog-tests/__init__.py +0 -0
  43. package/.versions/2.0.10/.pi/agent-fleet/hooks/coms-stop-hook.mjs +84 -0
  44. package/.versions/2.0.10/.pi/agent-fleet/scripts/claude-code-preflight.ts +70 -0
  45. package/.versions/2.0.10/.pi/agent-fleet/scripts/coms-claude-bridge.ts +411 -0
  46. package/.versions/2.0.10/.pi/agent-fleet/scripts/coms-cli.ts +425 -0
  47. package/.versions/2.0.10/.pi/agent-fleet/scripts/coms-hermes-bridge.ts +413 -0
  48. package/.versions/2.0.10/.pi/agent-fleet/scripts/fleet-codex-client.ts +69 -0
  49. package/.versions/2.0.10/.pi/agent-fleet/scripts/fleet-codex-read.py +148 -0
  50. package/.versions/2.0.10/.pi/agent-fleet/scripts/fleet.ts +216 -0
  51. package/.versions/2.0.10/.pi/agent-fleet/scripts/flow.ts +137 -0
  52. package/.versions/2.0.10/.pi/agent-fleet/scripts/hermes-monitor-capability-runner.ts +25 -0
  53. package/.versions/2.0.10/.pi/agent-fleet/scripts/hermes-monitor-scenario.ts +474 -0
  54. package/.versions/2.0.10/.pi/agent-fleet/scripts/hermes-watchdog-capability-probe.ts +45 -0
  55. package/.versions/2.0.10/.pi/agent-fleet/scripts/install-hermes-plugin.sh +180 -0
  56. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/claude-bridge-core.ts +210 -0
  57. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/coms-envelope.ts +582 -0
  58. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fake-herdr-server.ts +88 -0
  59. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-catalog.ts +63 -0
  60. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-operations.ts +190 -0
  61. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-session.ts +166 -0
  62. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-codex-transport.ts +124 -0
  63. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/fleet-command.ts +252 -0
  64. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/flow-command.ts +93 -0
  65. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/flow-maintenance.ts +230 -0
  66. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/herdr-layout.ts +281 -0
  67. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-bridge-core.ts +241 -0
  68. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-events.ts +1 -0
  69. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-herdr.ts +2 -0
  70. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-model.ts +3 -0
  71. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-registry.ts +2 -0
  72. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-socket.ts +2 -0
  73. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/hermes-monitor-store.ts +2 -0
  74. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/monitor-env.ts +146 -0
  75. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/peer-launch.ts +318 -0
  76. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/persona-banner.ts +62 -0
  77. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/persona-dirs.ts +25 -0
  78. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/runtime-dependencies.js +124 -0
  79. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/spawn-stagger.ts +101 -0
  80. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/team-project.ts +178 -0
  81. package/.versions/2.0.10/.pi/agent-fleet/scripts/lib/team-snapshot.ts +147 -0
  82. package/.versions/2.0.10/.pi/agent-fleet/scripts/package-lock.json +35 -0
  83. package/.versions/2.0.10/.pi/agent-fleet/scripts/package.json +9 -0
  84. package/.versions/2.0.10/.pi/agent-fleet/scripts/peer-banner.ts +41 -0
  85. package/.versions/2.0.10/.pi/agent-fleet/scripts/peer-launch.ts +283 -0
  86. package/.versions/2.0.10/.pi/agent-fleet/scripts/team-snapshot.ts +237 -0
  87. package/.versions/2.0.10/.pi/agent-fleet/scripts/team-up.ts +378 -0
  88. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/agent-phase.ts +133 -0
  89. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/changes.ts +61 -0
  90. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/debate.ts +149 -0
  91. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/env.ts +34 -0
  92. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/envelopes.ts +169 -0
  93. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/gates.ts +81 -0
  94. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/git.ts +96 -0
  95. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/merge.ts +95 -0
  96. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/model-profile.ts +22 -0
  97. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/model-visibility.ts +92 -0
  98. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/permissions.ts +130 -0
  99. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/personas.ts +57 -0
  100. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/poll.ts +86 -0
  101. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/quality.ts +64 -0
  102. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/run.ts +108 -0
  103. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/trace.ts +34 -0
  104. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/voices.ts +128 -0
  105. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/lib/writer-lease.ts +112 -0
  106. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/tsconfig.json +22 -0
  107. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-build-test.ts +61 -0
  108. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-debate.ts +87 -0
  109. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-document.ts +50 -0
  110. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-poll.ts +95 -0
  111. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-quality.ts +20 -0
  112. package/.versions/2.0.10/.pi/agent-fleet/scripts/workflows/wf-scout.ts +38 -0
  113. package/.versions/2.0.10/.pi/agents/dispatch-policy.yaml +32 -0
  114. package/.versions/2.0.10/.pi/agents/model-profiles.yaml +83 -0
  115. package/.versions/2.0.10/.pi/agents/peers.yaml +147 -0
  116. package/.versions/2.0.10/.pi/agents/teams.yaml +41 -0
  117. package/.versions/2.0.10/.pi/agents/voices.yaml +13 -0
  118. package/.versions/2.0.10/.pi/damage-control-rules.yaml +297 -0
  119. package/.versions/2.0.10/.pi/extensions/btw/README.md +120 -0
  120. package/.versions/2.0.10/.pi/extensions/btw/index.ts +914 -0
  121. package/.versions/2.0.10/.pi/extensions/btw/package.json +6 -0
  122. package/.versions/2.0.10/.pi/extensions/btw/state.js +179 -0
  123. package/.versions/2.0.10/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  124. package/.versions/2.0.10/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  125. package/.versions/2.0.10/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  126. package/.versions/2.0.10/.pi/extensions/compact-and-continue/README.md +42 -0
  127. package/.versions/2.0.10/.pi/extensions/compact-and-continue/index.ts +120 -0
  128. package/.versions/2.0.10/.pi/extensions/compact-and-continue/package.json +6 -0
  129. package/.versions/2.0.10/.pi/extensions/mcp-bridge/README.md +46 -0
  130. package/.versions/2.0.10/.pi/extensions/mcp-bridge/index.ts +206 -0
  131. package/.versions/2.0.10/.pi/extensions/mcp-bridge/package.json +6 -0
  132. package/.versions/2.0.10/.pi/extensions/package-lock.json +1175 -0
  133. package/.versions/2.0.10/.pi/extensions/package.json +9 -0
  134. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/README.md +224 -0
  135. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/config.ts +198 -0
  136. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  137. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/index.ts +248 -0
  138. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/package.json +6 -0
  139. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  140. package/.versions/2.0.10/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  141. package/.versions/2.0.10/.pi/harnesses/agent-hub/README.md +1217 -0
  142. package/.versions/2.0.10/.pi/harnesses/agent-hub/acceptance.ts +62 -0
  143. package/.versions/2.0.10/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  144. package/.versions/2.0.10/.pi/harnesses/agent-hub/artifacts.js +146 -0
  145. package/.versions/2.0.10/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  146. package/.versions/2.0.10/.pi/harnesses/agent-hub/backend-policy.js +174 -0
  147. package/.versions/2.0.10/.pi/harnesses/agent-hub/budget-continuation.ts +13 -0
  148. package/.versions/2.0.10/.pi/harnesses/agent-hub/budget-recovery.ts +97 -0
  149. package/.versions/2.0.10/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
  150. package/.versions/2.0.10/.pi/harnesses/agent-hub/capability-packs.ts +180 -0
  151. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
  152. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
  153. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
  154. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
  155. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
  156. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
  157. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
  158. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
  159. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
  160. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
  161. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
  162. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/budget-continue.ts +10 -0
  163. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
  164. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
  165. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
  166. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/context.ts +43 -0
  167. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
  168. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
  169. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
  170. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
  171. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/models.ts +10 -0
  172. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
  173. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/retry.ts +10 -0
  174. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
  175. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/work-mode.ts +29 -0
  176. package/.versions/2.0.10/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
  177. package/.versions/2.0.10/.pi/harnesses/agent-hub/config/agents.ts +177 -0
  178. package/.versions/2.0.10/.pi/harnesses/agent-hub/config/model-profiles.ts +216 -0
  179. package/.versions/2.0.10/.pi/harnesses/agent-hub/config/overrides.ts +153 -0
  180. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
  181. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +213 -0
  182. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/budgets.ts +202 -0
  183. package/.versions/2.0.10/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
  184. package/.versions/2.0.10/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
  185. package/.versions/2.0.10/.pi/harnesses/agent-hub/context-pressure.ts +191 -0
  186. package/.versions/2.0.10/.pi/harnesses/agent-hub/context-window.js +106 -0
  187. package/.versions/2.0.10/.pi/harnesses/agent-hub/debate-command.ts +176 -0
  188. package/.versions/2.0.10/.pi/harnesses/agent-hub/delegate.ts +446 -0
  189. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-coms.ts +237 -0
  190. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
  191. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-complete.ts +154 -0
  192. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +156 -0
  193. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +193 -0
  194. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native-types.ts +230 -0
  195. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-native.ts +213 -0
  196. package/.versions/2.0.10/.pi/harnesses/agent-hub/dispatch-observability.ts +225 -0
  197. package/.versions/2.0.10/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  198. package/.versions/2.0.10/.pi/harnesses/agent-hub/drift-watchdog.js +218 -0
  199. package/.versions/2.0.10/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  200. package/.versions/2.0.10/.pi/harnesses/agent-hub/execution-evidence.ts +80 -0
  201. package/.versions/2.0.10/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  202. package/.versions/2.0.10/.pi/harnesses/agent-hub/fixtures/registration-surface.json +57 -0
  203. package/.versions/2.0.10/.pi/harnesses/agent-hub/footer.ts +30 -0
  204. package/.versions/2.0.10/.pi/harnesses/agent-hub/helpers.ts +266 -0
  205. package/.versions/2.0.10/.pi/harnesses/agent-hub/hub-state-audit.js +64 -0
  206. package/.versions/2.0.10/.pi/harnesses/agent-hub/index.ts +2132 -0
  207. package/.versions/2.0.10/.pi/harnesses/agent-hub/input/completions.ts +76 -0
  208. package/.versions/2.0.10/.pi/harnesses/agent-hub/input/shortcuts.ts +20 -0
  209. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +123 -0
  210. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
  211. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +143 -0
  212. package/.versions/2.0.10/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +74 -0
  213. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  214. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  215. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  216. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  217. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  218. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  219. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  220. package/.versions/2.0.10/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
  221. package/.versions/2.0.10/.pi/harnesses/agent-hub/no-progress.ts +76 -0
  222. package/.versions/2.0.10/.pi/harnesses/agent-hub/package.json +7 -0
  223. package/.versions/2.0.10/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  224. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/models.ts +153 -0
  225. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
  226. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/profile-runtime.ts +120 -0
  227. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/roster.ts +94 -0
  228. package/.versions/2.0.10/.pi/harnesses/agent-hub/policy/work-mode.ts +119 -0
  229. package/.versions/2.0.10/.pi/harnesses/agent-hub/poll-command.ts +176 -0
  230. package/.versions/2.0.10/.pi/harnesses/agent-hub/presentation.ts +48 -0
  231. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/context.ts +47 -0
  232. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/fragments.ts +115 -0
  233. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/session-start.ts +90 -0
  234. package/.versions/2.0.10/.pi/harnesses/agent-hub/prompts/system-prompt.ts +112 -0
  235. package/.versions/2.0.10/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  236. package/.versions/2.0.10/.pi/harnesses/agent-hub/research/controls.ts +74 -0
  237. package/.versions/2.0.10/.pi/harnesses/agent-hub/research/runtime.ts +192 -0
  238. package/.versions/2.0.10/.pi/harnesses/agent-hub/research/spawn-run.ts +156 -0
  239. package/.versions/2.0.10/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  240. package/.versions/2.0.10/.pi/harnesses/agent-hub/return-contract.js +327 -0
  241. package/.versions/2.0.10/.pi/harnesses/agent-hub/return-extract.js +75 -0
  242. package/.versions/2.0.10/.pi/harnesses/agent-hub/review-findings.js +102 -0
  243. package/.versions/2.0.10/.pi/harnesses/agent-hub/run-budget.js +537 -0
  244. package/.versions/2.0.10/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  245. package/.versions/2.0.10/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  246. package/.versions/2.0.10/.pi/harnesses/agent-hub/scope-gate.js +123 -0
  247. package/.versions/2.0.10/.pi/harnesses/agent-hub/session-health.js +110 -0
  248. package/.versions/2.0.10/.pi/harnesses/agent-hub/session-start.ts +42 -0
  249. package/.versions/2.0.10/.pi/harnesses/agent-hub/spawn.ts +404 -0
  250. package/.versions/2.0.10/.pi/harnesses/agent-hub/timeline.ts +54 -0
  251. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/action-executors.ts +149 -0
  252. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
  253. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/context.ts +134 -0
  254. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +82 -0
  255. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +335 -0
  256. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +22 -0
  257. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/fleet-tools.ts +200 -0
  258. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/herdr-executors.ts +86 -0
  259. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/set-task-tier.ts +29 -0
  260. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/spawn-research.ts +62 -0
  261. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
  262. package/.versions/2.0.10/.pi/harnesses/agent-hub/tools/verification-contract.ts +77 -0
  263. package/.versions/2.0.10/.pi/harnesses/agent-hub/types.ts +63 -0
  264. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/activity-dots.ts +16 -0
  265. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/context-budget.ts +86 -0
  266. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/detail-panel.ts +178 -0
  267. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-actions.ts +76 -0
  268. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +99 -0
  269. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-editor.ts +44 -0
  270. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/fleet-source.ts +157 -0
  271. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/grid.ts +154 -0
  272. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
  273. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/history.ts +234 -0
  274. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
  275. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/running-strip.ts +2 -0
  276. package/.versions/2.0.10/.pi/harnesses/agent-hub/ui/zoom.ts +204 -0
  277. package/.versions/2.0.10/.pi/harnesses/agent-hub/version.ts +42 -0
  278. package/.versions/2.0.10/.pi/harnesses/agent-hub/work-mode-controls.ts +56 -0
  279. package/.versions/2.0.10/.pi/harnesses/agent-hub/work-mode.ts +167 -0
  280. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/README.md +59 -0
  281. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/index.ts +558 -0
  282. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/questions.ts +161 -0
  283. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/race-core.js +124 -0
  284. package/.versions/2.0.10/.pi/harnesses/ask-user-remote/runtime-ask.ts +43 -0
  285. package/.versions/2.0.10/.pi/harnesses/coms/README.md +100 -0
  286. package/.versions/2.0.10/.pi/harnesses/coms/index.ts +282 -0
  287. package/.versions/2.0.10/.pi/harnesses/coms/package.json +7 -0
  288. package/.versions/2.0.10/.pi/harnesses/coms/version.ts +42 -0
  289. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/README.md +135 -0
  290. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/index.ts +541 -0
  291. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/package.json +7 -0
  292. package/.versions/2.0.10/.pi/harnesses/damage-control-continue/version.ts +42 -0
  293. package/.versions/2.0.10/.pi/harnesses/lib/changed-file-diagnostics.ts +642 -0
  294. package/.versions/2.0.10/.pi/harnesses/lib/coms-core-io.ts +385 -0
  295. package/.versions/2.0.10/.pi/harnesses/lib/coms-core.ts +577 -0
  296. package/.versions/2.0.10/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  297. package/.versions/2.0.10/.pi/harnesses/lib/context-budget-child-prompt.ts +180 -0
  298. package/.versions/2.0.10/.pi/harnesses/lib/context-budget-hub-prompt.ts +114 -0
  299. package/.versions/2.0.10/.pi/harnesses/lib/context-budget-view.ts +107 -0
  300. package/.versions/2.0.10/.pi/harnesses/lib/context-budget.ts +114 -0
  301. package/.versions/2.0.10/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  302. package/.versions/2.0.10/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
  303. package/.versions/2.0.10/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
  304. package/.versions/2.0.10/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
  305. package/.versions/2.0.10/.pi/harnesses/lib/fleet-dashboard-ops.ts +178 -0
  306. package/.versions/2.0.10/.pi/harnesses/lib/fleet-dashboard-view.ts +134 -0
  307. package/.versions/2.0.10/.pi/harnesses/lib/fleet-detail-view.ts +247 -0
  308. package/.versions/2.0.10/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  309. package/.versions/2.0.10/.pi/harnesses/lib/fleet-panel.ts +34 -0
  310. package/.versions/2.0.10/.pi/harnesses/lib/fleet-read-model.ts +213 -0
  311. package/.versions/2.0.10/.pi/harnesses/lib/fleet-selection.ts +24 -0
  312. package/.versions/2.0.10/.pi/harnesses/lib/fleet-strip-controller.ts +74 -0
  313. package/.versions/2.0.10/.pi/harnesses/lib/fleet-strip-view.ts +132 -0
  314. package/.versions/2.0.10/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
  315. package/.versions/2.0.10/.pi/harnesses/lib/herdr-client.ts +472 -0
  316. package/.versions/2.0.10/.pi/harnesses/lib/herdr-presence.ts +399 -0
  317. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  318. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  319. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  320. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  321. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  322. package/.versions/2.0.10/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  323. package/.versions/2.0.10/.pi/harnesses/lib/spawned-peers.js +190 -0
  324. package/.versions/2.0.10/.pi/harnesses/lib/update-check.ts +222 -0
  325. package/.versions/2.0.10/.pi/harnesses/package-lock.json +2039 -0
  326. package/.versions/2.0.10/.pi/harnesses/package.json +10 -0
  327. package/.versions/2.0.10/.pi/prompts/af-build.md +24 -0
  328. package/.versions/2.0.10/.pi/prompts/af-code-simplify.md +22 -0
  329. package/.versions/2.0.10/.pi/prompts/af-constraints.md +31 -0
  330. package/.versions/2.0.10/.pi/prompts/af-plan.md +17 -0
  331. package/.versions/2.0.10/.pi/prompts/af-review.md +16 -0
  332. package/.versions/2.0.10/.pi/prompts/af-set-hermes-telegram.md +15 -0
  333. package/.versions/2.0.10/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  334. package/.versions/2.0.10/.pi/prompts/af-ship.md +17 -0
  335. package/.versions/2.0.10/.pi/prompts/af-spec.md +15 -0
  336. package/.versions/2.0.10/.pi/prompts/af-test.md +19 -0
  337. package/.versions/2.0.10/.pi/skills/bowser/SKILL.md +145 -0
  338. package/.versions/2.0.10/.version +1 -0
  339. package/.versions/2.0.10/agents/architect.md +25 -0
  340. package/.versions/2.0.10/agents/bowser.md +28 -0
  341. package/.versions/2.0.10/agents/builder.md +56 -0
  342. package/.versions/2.0.10/agents/code-reviewer.md +210 -0
  343. package/.versions/2.0.10/agents/deep-researcher.md +33 -0
  344. package/.versions/2.0.10/agents/documenter.md +23 -0
  345. package/.versions/2.0.10/agents/orchestrator.md +23 -0
  346. package/.versions/2.0.10/agents/plan-reviewer.md +84 -0
  347. package/.versions/2.0.10/agents/planner.md +106 -0
  348. package/.versions/2.0.10/agents/releaser.md +25 -0
  349. package/.versions/2.0.10/agents/researcher.md +31 -0
  350. package/.versions/2.0.10/agents/security-auditor.md +168 -0
  351. package/.versions/2.0.10/agents/test-engineer.md +154 -0
  352. package/.versions/2.0.10/agents/web-debugger.md +44 -0
  353. package/.versions/2.0.10/agents/web-performance-auditor.md +194 -0
  354. package/.versions/2.0.10/bin/catalog/harness-runtime-closure.json +32 -0
  355. package/.versions/2.0.10/codex/fleet-session-client/SKILL.md +34 -0
  356. package/.versions/2.0.10/codex/fleet-session-client.zip +0 -0
  357. package/.versions/2.0.10/docs/ARCHITECTURE.md +416 -0
  358. package/.versions/2.0.10/docs/agent-fleet-setup.md +586 -0
  359. package/.versions/2.0.10/docs/claude-code-coms-bridge.md +134 -0
  360. package/.versions/2.0.10/docs/codex-session-bridge.md +219 -0
  361. package/.versions/2.0.10/docs/coms-hermes-bridge.md +188 -0
  362. package/.versions/2.0.10/docs/getting-started.md +126 -0
  363. package/.versions/2.0.10/docs/npm-install.md +383 -0
  364. package/.versions/2.0.10/docs/pi-extensions.md +449 -0
  365. package/.versions/2.0.10/docs/pi-setup.md +92 -0
  366. package/.versions/2.0.10/docs/skill-anatomy.md +150 -0
  367. package/.versions/2.0.10/install-manifest.json +2991 -0
  368. package/.versions/2.0.10/justfile +247 -0
  369. package/.versions/2.0.10/manifest-meta.json +970 -0
  370. package/.versions/2.0.10/references/accessibility-checklist.md +160 -0
  371. package/.versions/2.0.10/references/communication-contract.md +26 -0
  372. package/.versions/2.0.10/references/definition-of-done.md +67 -0
  373. package/.versions/2.0.10/references/fleet-coordination-patterns.md +171 -0
  374. package/.versions/2.0.10/references/observability-checklist.md +92 -0
  375. package/.versions/2.0.10/references/orchestration-patterns.md +370 -0
  376. package/.versions/2.0.10/references/performance-checklist.md +236 -0
  377. package/.versions/2.0.10/references/prompting-patterns.md +380 -0
  378. package/.versions/2.0.10/references/security-checklist.md +245 -0
  379. package/.versions/2.0.10/references/testing-patterns.md +235 -0
  380. package/.versions/2.0.10/references/workflow-authoring.md +304 -0
  381. package/.versions/2.0.10/skills/_internal/grilling.md +59 -0
  382. package/.versions/2.0.10/skills/browser-testing-with-devtools/SKILL.md +351 -0
  383. package/.versions/2.0.10/skills/code-review-and-quality/SKILL.md +396 -0
  384. package/.versions/2.0.10/skills/compound-learning/SKILL.md +137 -0
  385. package/.versions/2.0.10/skills/constraint-driven-development/SKILL.md +338 -0
  386. package/.versions/2.0.10/skills/constraint-driven-development/references/floor-guard.md +99 -0
  387. package/.versions/2.0.10/skills/context-engineering/SKILL.md +341 -0
  388. package/.versions/2.0.10/skills/deprecation-and-migration/SKILL.md +247 -0
  389. package/.versions/2.0.10/skills/designing-agents/SKILL.md +394 -0
  390. package/.versions/2.0.10/skills/designing-agents/pi-harness-authoring.md +222 -0
  391. package/.versions/2.0.10/skills/drafting-workflows/SKILL.md +143 -0
  392. package/.versions/2.0.10/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
  393. package/.versions/2.0.10/skills/frontend-ui-engineering/SKILL.md +328 -0
  394. package/.versions/2.0.10/skills/git-workflow-and-versioning/SKILL.md +316 -0
  395. package/.versions/2.0.10/skills/idea-refine/SKILL.md +182 -0
  396. package/.versions/2.0.10/skills/idea-refine/examples.md +238 -0
  397. package/.versions/2.0.10/skills/idea-refine/frameworks.md +99 -0
  398. package/.versions/2.0.10/skills/idea-refine/refinement-criteria.md +113 -0
  399. package/.versions/2.0.10/skills/idea-refine/scripts/idea-refine.sh +15 -0
  400. package/.versions/2.0.10/skills/incremental-implementation/SKILL.md +302 -0
  401. package/.versions/2.0.10/skills/interview-me/SKILL.md +226 -0
  402. package/.versions/2.0.10/skills/orchestration-verification/SKILL.md +182 -0
  403. package/.versions/2.0.10/skills/peer-coms/SKILL.md +90 -0
  404. package/.versions/2.0.10/skills/performance-optimization/SKILL.md +496 -0
  405. package/.versions/2.0.10/skills/planning-and-task-breakdown/SKILL.md +289 -0
  406. package/.versions/2.0.10/skills/security-and-hardening/SKILL.md +524 -0
  407. package/.versions/2.0.10/skills/spec-driven-development/SKILL.md +295 -0
  408. package/.versions/2.0.10/skills/using-agent-skills/SKILL.md +198 -0
  409. package/.versions/2.0.10/vendor/agent-skills-upstream/LICENSE +21 -0
  410. package/.versions/2.0.10/vendor/agent-skills-upstream/README.md +430 -0
  411. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +367 -0
  412. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  413. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  414. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  415. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  416. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/constraint-driven-development/SKILL.md +311 -0
  417. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/constraint-driven-development/references/floor-guard.md +99 -0
  418. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +337 -0
  419. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  420. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  421. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +288 -0
  422. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  423. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  424. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  425. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  426. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  427. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  428. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  429. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  430. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  431. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  432. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +238 -0
  433. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +496 -0
  434. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +257 -0
  435. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +524 -0
  436. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +330 -0
  437. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +216 -0
  438. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +245 -0
  439. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +398 -0
  440. package/.versions/2.0.10/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +192 -0
  441. package/CHANGELOG.md +11 -0
  442. package/agents/architect.md +1 -1
  443. package/agents/bowser.md +1 -1
  444. package/agents/builder.md +1 -1
  445. package/agents/code-reviewer.md +1 -1
  446. package/agents/deep-researcher.md +1 -1
  447. package/agents/documenter.md +1 -1
  448. package/agents/orchestrator.md +1 -1
  449. package/agents/plan-reviewer.md +1 -1
  450. package/agents/planner.md +1 -1
  451. package/agents/releaser.md +1 -1
  452. package/agents/researcher.md +1 -1
  453. package/agents/security-auditor.md +1 -1
  454. package/agents/test-engineer.md +1 -1
  455. package/agents/web-debugger.md +1 -1
  456. package/agents/web-performance-auditor.md +1 -1
  457. package/bin/cli.js +8 -5
  458. package/bin/lib/path-boundaries.js +5 -6
  459. package/bin/lib/stt-wizard.js +154 -23
  460. package/docs/agent-fleet-setup.md +26 -8
  461. package/docs/npm-install.md +29 -2
  462. package/docs/pi-setup.md +16 -0
  463. package/install-manifest.json +1 -1
  464. package/package.json +13 -3
  465. package/skills/orchestration-verification/SKILL.md +1 -0
@@ -0,0 +1,295 @@
1
+ ---
2
+ name: spec-driven-development
3
+ description: Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, only exist as a vague idea, or need to be grilled before planning. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
4
+ ---
5
+
6
+ # Spec-Driven Development
7
+
8
+ ## Overview
9
+
10
+ Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing.
11
+
12
+ ## When to Use
13
+
14
+ - Starting a new project or feature
15
+ - Requirements are ambiguous or incomplete
16
+ - The change touches multiple files or modules
17
+ - You're about to make an architectural decision
18
+ - The user asks to grill or stress-test a concept/spec before planning
19
+ - The task would take more than 30 minutes to implement
20
+
21
+ **When NOT to use:** Single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained.
22
+
23
+ ## Proportionality gate (check before writing anything)
24
+
25
+ A spec is a commitment device: once it exists, everything in it gets planned, built, reviewed, and evidenced. That makes an oversized spec the most expensive mistake available here — it is cheaper to under-specify and ask than to over-specify and execute.
26
+
27
+ Before writing one, answer in one sentence: **what did the human actually ask for?** Then:
28
+
29
+ - **If the answer fits in a sentence and the change fits in a file, do not write a spec.** Make the change, state your assumptions, and let the human correct you. A one-line correction is cheaper than a spec review.
30
+ - **Spec the request, not the domain.** A request to fix how one service reads its configuration is not a mandate to specify that service's deployment, telemetry, and the retirement of its predecessor. Related work goes in a "Future / not now" list, not in scope.
31
+ - **Do not let non-goals grow the document.** A long list of things you will not do is not safety; it is surface area that later reviews will treat as requirements.
32
+ - **Verification must be proportionate.** Ask what evidence the human would actually want to see. "The tests pass and the app starts" is a complete verification story for most changes; per-item runtime provenance is warranted only when the human asked for it or the change is irreversible.
33
+ - **If the spec grows past the ask while you write it, stop and check in.** Say what it grew into and let the human choose the scope. A spec that outgrew its request is a finding, not a deliverable.
34
+
35
+ ## Output Location
36
+
37
+ By default, save the spec to `docs/prds/{area}/PRD{n}-{topic}.md`:
38
+
39
+ - `{area}` — the functional area of the codebase the change belongs to. Ask the user or infer it from the change (e.g. `tournaments`, `calendar`, `auth`).
40
+ - `{n}` — the next free PRD number. Scan `docs/prds/` recursively for the highest existing `PRD<number>` and add 1; start at `1` if none exist.
41
+ - `{topic}` — a short kebab-case slug of the feature.
42
+
43
+ Match the project's existing `docs` vs `Docs` capitalization, and create the directory if it does not exist.
44
+
45
+ **Project overrides:** if `.ai/agent-fleet-overrides.md` has a `## spec-driven-development` section, its keys (`spec-dir`, `naming`) override these defaults. Absent file or section → use the defaults above. See [docs/agent-fleet-setup.md](../../docs/agent-fleet-setup.md).
46
+
47
+ ## The Gated Workflow
48
+
49
+ Spec-driven development has four phases, preceded by a scope check (Phase 0) that activates only when one request bundles several independently testable capabilities. Do not advance to the next phase until the current one is validated.
50
+
51
+ ```
52
+ SPECIFY ──→ PLAN ──→ TASKS ──→ IMPLEMENT
53
+ │ │ │ │
54
+ ▼ ▼ ▼ ▼
55
+ Human Human Human Human
56
+ reviews reviews reviews reviews
57
+ ```
58
+
59
+ ### Phase 0: Scope Check
60
+
61
+ Most requests describe one capability. If this one does, skip this phase and go straight to Specify — Phase 0 exists for the exception, not the rule, and it puts no hierarchy on single-capability features.
62
+
63
+ **Detection.** Decompose before specifying when a single requirement bundles several independently testable capabilities:
64
+
65
+ - The requirement names distinct capabilities with their own consumers or data (e.g. identity, billing, notifications, reporting)
66
+ - Acceptance criteria cluster into groups that could ship and be verified separately
67
+ - One capability could be cut or replaced without rewriting the others' requirements
68
+
69
+ **Propose a capability map before writing any spec.** Small and reviewable — a module table plus a build order, not a project plan:
70
+
71
+ ```markdown
72
+ # Capability Map: [Initiative Name]
73
+
74
+ | Module id | Responsibility | Depends on |
75
+ |---|---|---|
76
+ | identity | Accounts, sessions, SSO | — |
77
+ | billing | Plans, invoices, payments | identity |
78
+ | notifications | Email and webhook fan-out | identity |
79
+ | reporting | Usage dashboards | billing, notifications |
80
+
81
+ Build order: identity → billing, notifications → reporting
82
+ ```
83
+
84
+ - **Stable module ids.** Kebab-case, chosen once, never renamed mid-initiative. Specs, plans, and downstream commands select work by these ids instead of guessing which spec is active.
85
+ - **Dependency direction, no cycles.** Arrows point one way. If two modules each need the other, they are one module.
86
+ - **Interfaces live at the boundary.** The map records that `billing` depends on `identity`; the contract between them belongs in the provider module's spec (see `api-and-interface-design` for designing it).
87
+
88
+ **The map is gated like every phase.** The human reviews module boundaries, dependency direction, and build order before any module spec is written. Getting the map wrong is expensive; reviewing ten lines is not.
89
+
90
+ **Then recurse per module.** Run Specify → Plan → Tasks → Implement for each module in dependency order. Each module gets its own spec, scoped to that module's objective, boundaries, and success criteria. Save the approved map in the same spec directory the Output Convention above resolves to (default `docs/prds/{area}/`), as `CAPABILITY-MAP-{topic}.md`, and give each module its own PRD under the project's normal naming with the module id as the `{topic}` slug. The map, not filename guessing, is the index of what exists.
91
+
92
+ ### Phase 1: Specify
93
+
94
+ **Gather context first.** Before writing any spec content, identify and read the sources the spec will build on:
95
+
96
+ - Existing documentation (README, architecture docs, ADRs)
97
+ - Related or prior specs — the new spec should explicitly link them (see `Related Specs` below)
98
+ - Code paths the change will touch, for implementation-oriented specs
99
+ - External artifacts the spec references (contract, design doc, ticket, research notes)
100
+
101
+ Writing a spec without reading what already exists leads to duplication, contradiction, and invented detail. If a source is missing or inaccessible, record it as an open question rather than guessing.
102
+
103
+ Then start with a high-level vision. Ask the human clarifying questions until requirements are concrete.
104
+
105
+ **Grilling (required before locking the spec):** Read the shared internal helper at [`../_internal/grilling.md`](../_internal/grilling.md). Skip anything already explicit in chat, prompt, PRD, or rules — do not re-confirm it. Grill every remaining unconfirmed design choice (multiple valid ways, contradiction, competing code patterns) one question at a time, with a recommended option. Fold each answer into Success Criteria, Boundaries, Proposed decisions, or Open Questions. If nothing is open, note that grilling found no unspecified forks and continue.
106
+
107
+ **Surface assumptions immediately.** Before writing any spec content, classify what you would otherwise assume:
108
+
109
+ - Already explicit in chat, prompt, or rules → do not re-ask.
110
+ - Confirmed in code, tests, or trusted docs (e.g. PostgreSQL because the Prisma schema is already Postgres) → do not re-ask; mark Confirmed.
111
+ - Load-bearing and still open (native vs web, cookies vs JWT when neither is mandated) → grill per the helper above and **wait**. Do not dump a list and proceed unless corrected.
112
+
113
+ Don't silently fill in ambiguous requirements. The spec's entire purpose is to surface misunderstandings *before* code gets written — assumptions are the most dangerous form of misunderstanding.
114
+
115
+ **Ground every claim.** Every statement in the spec must fall into exactly one of these four categories, and the category should be clear to the reader:
116
+
117
+ - **Confirmed** — verified in code, tests, runtime, or trusted documentation. Safe to build on.
118
+ - **Target** — what we intend to build. Marked explicitly so it's not confused with current behavior.
119
+ - **Proposed** — a design decision that hasn't been approved yet. Must be reviewed before implementation.
120
+ - **Inferred** — a reasonable guess from available evidence, labeled as such. Ask to confirm if it load-bears a decision.
121
+
122
+ If a claim doesn't fit any of these categories, it belongs in **Open Questions**, not in the spec body. Mixing confirmed facts with proposals is how specs quietly become fiction.
123
+
124
+ **Do not invent.** Do not fabricate APIs, schemas, libraries, endpoints, file paths, environment variables, or commands. If the spec needs something that doesn't exist in the codebase or documentation yet, mark it as Proposed or add it to Open Questions. A spec that invents details becomes a source of bugs — downstream code gets written against things that were never real.
125
+
126
+ **Write a spec document covering these six core areas:**
127
+
128
+ 1. **Objective** — What are we building and why? Who is the user? What does success look like?
129
+
130
+ 2. **Commands** — Full executable commands with flags, not just tool names.
131
+ ```
132
+ Build: npm run build
133
+ Test: npm test -- --coverage
134
+ Lint: npm run lint --fix
135
+ Dev: npm run dev
136
+ ```
137
+
138
+ 3. **Project Structure** — Where source code lives, where tests go, where docs belong.
139
+ ```
140
+ src/ → Application source code
141
+ src/components → React components
142
+ src/lib → Shared utilities
143
+ tests/ → Unit and integration tests
144
+ e2e/ → End-to-end tests
145
+ docs/ → Documentation
146
+ ```
147
+
148
+ 4. **Code Style** — One real code snippet showing your style beats three paragraphs describing it. Include naming conventions, formatting rules, and examples of good output.
149
+
150
+ 5. **Testing Strategy** — What framework, where tests live, coverage expectations, which test levels for which concerns.
151
+
152
+ 6. **Boundaries** — Three-tier system:
153
+ - **Always do:** Run tests before commits, follow naming conventions, validate inputs
154
+ - **Ask first:** Database schema changes, adding dependencies, changing CI config
155
+ - **Never do:** Commit secrets, edit vendor directories, remove failing tests without approval
156
+
157
+ **Spec template:**
158
+
159
+ ```markdown
160
+ # Spec: [Project/Feature Name]
161
+
162
+ ## Objective
163
+ [What we're building and why. User stories or acceptance criteria.]
164
+
165
+ ## Related Specs
166
+ - Refines: [path/to/prior-spec.md]
167
+ - Supersedes: [path/to/old-spec.md]
168
+ - Related: [path/to/adjacent-spec.md]
169
+
170
+ ## Tech Stack
171
+ [Framework, language, key dependencies with versions]
172
+
173
+ ## Commands
174
+ [Build, test, lint, dev — full commands]
175
+
176
+ ## Project Structure
177
+ [Directory layout with descriptions]
178
+
179
+ ## Code Style
180
+ [Example snippet + key conventions]
181
+
182
+ ## Testing Strategy
183
+ [Framework, test locations, coverage requirements, test levels]
184
+
185
+ ## Boundaries
186
+ - Always: [...]
187
+ - Ask first: [...]
188
+ - Never: [...]
189
+
190
+ ## Success Criteria
191
+ [How we'll know this is done — specific, testable conditions]
192
+
193
+ ## Open Questions
194
+ [Anything unresolved that needs human input]
195
+ ```
196
+
197
+ **Reframe instructions as success criteria.** When receiving vague requirements, translate them into concrete conditions:
198
+
199
+ ```
200
+ REQUIREMENT: "Make the dashboard faster"
201
+
202
+ REFRAMED SUCCESS CRITERIA:
203
+ - Dashboard LCP < 2.5s on 4G connection
204
+ - Initial data load completes in < 500ms
205
+ - No layout shift during load (CLS < 0.1)
206
+ → Are these the right targets?
207
+ ```
208
+
209
+ This lets you loop, retry, and problem-solve toward a clear goal rather than guessing what "faster" means.
210
+
211
+ ### Phase 2: Plan
212
+
213
+ With the validated spec, generate a technical implementation plan:
214
+
215
+ 1. Identify the major components and their dependencies
216
+ 2. Determine the implementation order (what must be built first)
217
+ 3. Note risks and mitigation strategies
218
+ 4. Identify what can be built in parallel vs. what must be sequential
219
+ 5. Define verification checkpoints between phases
220
+
221
+ > Follow `planning-and-task-breakdown` for the dependency-graph mapping and vertical-slicing mechanics behind these steps; it is the canonical source. The bullets above are a lightweight summary; if they ever diverge, `planning-and-task-breakdown` takes precedence.
222
+
223
+ The plan should be reviewable: the human should be able to read it and say "yes, that's the right approach" or "no, change X."
224
+
225
+ ### Phase 3: Tasks
226
+
227
+ Break the plan into discrete, implementable tasks:
228
+
229
+ - Each task should be completable in a single focused session
230
+ - Each task has explicit acceptance criteria
231
+ - Each task includes a verification step (test, build, manual check)
232
+ - Tasks are ordered by dependency, not by perceived importance
233
+ - No task should require changing more than ~5 files
234
+
235
+ > Follow `planning-and-task-breakdown` for the full task-sizing and dependency-ordering mechanics; it is the canonical source. The template below is a lightweight inline form; if they ever diverge, `planning-and-task-breakdown` takes precedence.
236
+
237
+ **Task template:**
238
+ ```markdown
239
+ - [ ] Task: [Description]
240
+ - Acceptance: [What must be true when done]
241
+ - Verify: [How to confirm — test command, build, manual check]
242
+ - Files: [Which files will be touched]
243
+ ```
244
+
245
+ ### Phase 4: Implement
246
+
247
+ Execute tasks one at a time following `skills/incremental-implementation/SKILL.md` (`incremental-implementation`) and `skills/test-driven-development/SKILL.md` (`test-driven-development`). Use `skills/context-engineering/SKILL.md` (`context-engineering`) to load the right spec sections and source files at each step rather than flooding the agent with the entire spec.
248
+
249
+ ## Keeping the Spec Alive
250
+
251
+ The spec is a living document, not a one-time artifact:
252
+
253
+ - **Update when decisions change** — If you discover the data model needs to change, update the spec first, then implement.
254
+ - **Update when scope changes** — Features added or cut should be reflected in the spec.
255
+ - **Commit the spec** — The spec belongs in version control alongside the code.
256
+ - **Reference the spec in PRs** — Link back to the spec section that each PR implements.
257
+
258
+ ## Common Rationalizations
259
+
260
+ | Rationalization | Reality |
261
+ |---|---|
262
+ | "This is simple, I don't need a spec" | Simple tasks don't need *long* specs, but they still need acceptance criteria. A two-line spec is fine. |
263
+ | "I'll write the spec after I code it" | That's documentation, not specification. The spec's value is in forcing clarity *before* code. |
264
+ | "The spec will slow us down" | A 15-minute spec prevents hours of rework. Waterfall in 15 minutes beats debugging in 15 hours. |
265
+ | "Requirements will change anyway" | That's why the spec is a living document. An outdated spec is still better than no spec. |
266
+ | "The user knows what they want" | Even clear requests have implicit assumptions. The spec surfaces those assumptions. |
267
+ | "It's one big feature; splitting it is overhead" | If acceptance criteria cluster into independently testable groups, a monolithic spec forces every downstream task to reason over the whole contract. A ten-line capability map is the cheap alternative. |
268
+ | "I'll decompose during planning" | Planning slices tasks within a spec. By then the oversized artifact already exists — module boundaries and dependency direction must be decided before the spec is written, not after. |
269
+
270
+ ## Red Flags
271
+
272
+ - Starting to write code without any written requirements
273
+ - Asking "should I just start building?" before clarifying what "done" means
274
+ - Implementing features not mentioned in any spec or task list
275
+ - Making architectural decisions without documenting them
276
+ - Skipping the spec because "it's obvious what to build"
277
+ - Re-asking a requirement already explicit in chat, prompt, or rules
278
+ - Locking a spec that silently picks among several valid approaches
279
+ - One spec whose requirements span several independently testable capabilities
280
+ - Module boundaries or build order decided implicitly during implementation because no capability map was approved up front
281
+
282
+ ## Verification
283
+
284
+ Before proceeding to implementation, confirm:
285
+
286
+ - [ ] The spec covers all six core areas
287
+ - [ ] The human has reviewed and approved the spec
288
+ - [ ] Grilling ran before the spec was locked (inventory of load-bearing decisions)
289
+ - [ ] Already-stated requirements (chat, prompt, rules) were not re-asked
290
+ - [ ] Each remaining load-bearing decision is recorded as accepted, rejected, or deferred
291
+ - [ ] Success criteria are specific and testable
292
+ - [ ] Boundaries (Always/Ask First/Never) are defined
293
+ - [ ] The spec is saved to its output location (see Output Location)
294
+ - [ ] If the request bundles several independently testable capabilities, a capability map (module ids, dependency direction, build order) was approved before any module spec was written
295
+ - [ ] Every module spec traces to a module id in the approved map
@@ -0,0 +1,198 @@
1
+ ---
2
+ name: using-agent-skills
3
+ description: Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.
4
+ ---
5
+
6
+ # Using Agent Fleet
7
+
8
+ ## Overview
9
+
10
+ Agent Fleet is a collection of engineering workflow skills organized by development phase. Each skill encodes a specific process that senior engineers follow. This meta-skill helps you discover and apply the right skill for your current task.
11
+
12
+ ## Skill Discovery
13
+
14
+ When a task arrives, identify the development phase and apply the corresponding skill:
15
+
16
+ ```
17
+ Task arrives
18
+ │
19
+ ├── Don't know what you want yet? ──────→ interview-me
20
+ ├── Have a rough concept, need variants or stress-test? → idea-refine
21
+ ├── New project/feature/change? ──→ spec-driven-development
22
+ ├── No quality bar written down? ──→ constraint-driven-development
23
+ ├── Have a spec, need tasks or plan grilling? → planning-and-task-breakdown
24
+ ├── Implementing code? ────────────→ incremental-implementation
25
+ │ ├── UI work? ─────────────────→ frontend-ui-engineering
26
+ │ ├── API work? ────────────────→ api-and-interface-design
27
+ │ ├── Need better context? ─────→ context-engineering
28
+ │ ├── Need doc-verified code? ───→ source-driven-development
29
+ │ └── Stakes high / unfamiliar code? ──→ doubt-driven-development
30
+ ├── Writing/running tests? ────────→ test-driven-development
31
+ │ └── Browser-based? ───────────→ browser-testing-with-devtools
32
+ ├── Something broke? ──────────────→ debugging-and-error-recovery
33
+ ├── Reviewing code? ───────────────→ code-review-and-quality
34
+ │ ├── Too complex? ─────────────→ code-simplification
35
+ │ ├── Security concerns? ───────→ security-and-hardening
36
+ │ └── Performance concerns? ────→ performance-optimization
37
+ ├── Committing/branching? ─────────→ git-workflow-and-versioning
38
+ ├── CI/CD pipeline work? ──────────→ ci-cd-and-automation
39
+ ├── Deprecating/migrating? ────────→ deprecation-and-migration
40
+ ├── Writing docs/ADRs? ───────────→ documentation-and-adrs
41
+ ├── Adding logs/metrics/alerts? ───→ observability-and-instrumentation
42
+ ├── Orchestrating a multi-agent team? → orchestration-verification
43
+ │ └── "Make X behave like Y"? ──→ orchestration-verification (parity inventory)
44
+ ├── Session ending with lessons worth keeping? → compound-learning
45
+ ├── Authoring a new skill/persona? ─→ designing-agents
46
+ └── Deploying/launching? ─────────→ shipping-and-launch
47
+ ```
48
+
49
+ ## Core Operating Behaviors
50
+
51
+ These behaviors apply at all times, across all skills. They are non-negotiable.
52
+
53
+ ### 1. Surface Assumptions — grill unspecified forks
54
+
55
+ Whenever a decision must be taken — planning **or** implementation — follow [`../_internal/grilling.md`](../_internal/grilling.md):
56
+
57
+ - **Already stated** in chat, prompt, PRD, spec, plan, or rules → do not re-ask. Treat as accepted.
58
+ - **Unspecified and load-bearing** (multiple valid ways, contradiction, competing code patterns) → grill one question at a time, with a recommended option, and **wait**. Do not "proceed unless corrected."
59
+ - **Non-load-bearing working detail** (which test file to open first) → state it and continue unless redirected.
60
+
61
+ Don't silently fill in ambiguous requirements. The most common failure mode is making wrong assumptions and running with them unchecked. Surface uncertainty early — it's cheaper than rework.
62
+
63
+ ### 2. Manage Confusion Actively
64
+
65
+ When you encounter inconsistencies, conflicting requirements, or unclear specifications:
66
+
67
+ 1. **STOP.** Do not proceed with a guess.
68
+ 2. Name the specific confusion.
69
+ 3. Present the tradeoff or ask the clarifying question.
70
+ 4. Wait for resolution before continuing.
71
+
72
+ **Bad:** Silently picking one interpretation and hoping it's right.
73
+ **Good:** "I see X in the spec but Y in the existing code. Which takes precedence?"
74
+
75
+ ### 3. Push Back When Warranted
76
+
77
+ You are not a yes-machine. When an approach has clear problems:
78
+
79
+ - Point out the issue directly
80
+ - Explain the concrete downside (quantify when possible — "this adds ~200ms latency" not "this might be slower")
81
+ - Propose an alternative
82
+ - Accept the human's decision if they override with full information
83
+
84
+ Sycophancy is a failure mode. "Of course!" followed by implementing a bad idea helps no one. Honest technical disagreement is more valuable than false agreement.
85
+
86
+ ### 4. Enforce Simplicity
87
+
88
+ Your natural tendency is to overcomplicate. Actively resist it.
89
+
90
+ Before finishing any implementation, ask:
91
+ - Can this be done in fewer lines?
92
+ - Are these abstractions earning their complexity?
93
+ - Would a staff engineer look at this and say "why didn't you just..."?
94
+
95
+ If you build 1000 lines and 100 would suffice, you have failed. Prefer the boring, obvious solution. Cleverness is expensive.
96
+
97
+ ### 5. Maintain Scope Discipline
98
+
99
+ Touch only what you're asked to touch.
100
+
101
+ Do NOT:
102
+ - Remove comments you don't understand
103
+ - "Clean up" code orthogonal to the task
104
+ - Refactor adjacent systems as a side effect
105
+ - Delete code that seems unused without explicit approval
106
+ - Add features not in the spec because they "seem useful"
107
+
108
+ Your job is surgical precision, not unsolicited renovation.
109
+
110
+ ### 6. Verify, Don't Assume
111
+
112
+ Every skill includes a verification step. A task is not complete until verification passes. "Seems right" is never sufficient — there must be evidence (passing tests, build output, runtime data).
113
+
114
+ Per-skill verification is the local check. The project-wide bar that applies to *every* change, regardless of which skill is active, is the Definition of Done: tests pass, no regressions, behavior verified at runtime, docs updated. See `../../references/definition-of-done.md`. It complements each task's acceptance criteria rather than replacing them.
115
+
116
+ ## Failure Modes to Avoid
117
+
118
+ These are the subtle errors that look like productivity but create problems:
119
+
120
+ 1. Making wrong assumptions without checking
121
+ 2. Not managing your own confusion — plowing ahead when lost
122
+ 3. Not surfacing inconsistencies you notice
123
+ 4. Not presenting tradeoffs on non-obvious decisions
124
+ 5. Re-asking a requirement that was already explicit in chat, PRD, or rules
125
+ 6. Silently picking among several valid approaches or existing code patterns
126
+ 7. Being sycophantic ("Of course!") to approaches with clear problems
127
+ 8. Overcomplicating code and APIs
128
+ 9. Modifying code or comments orthogonal to the task
129
+ 10. Removing things you don't fully understand
130
+ 11. Building without a spec because "it's obvious"
131
+ 12. Skipping verification because "it looks right"
132
+
133
+ ## Skill Rules
134
+
135
+ 1. **Check for an applicable skill before starting work.** Skills encode processes that prevent common mistakes.
136
+
137
+ 2. **Skills are workflows, not suggestions.** Follow the steps in order. Don't skip verification steps.
138
+
139
+ 3. **Multiple skills can apply.** A feature implementation might involve `idea-refine` → `spec-driven-development` → `planning-and-task-breakdown` → `incremental-implementation` → `test-driven-development` → `code-review-and-quality` → `code-simplification` → `shipping-and-launch` in sequence.
140
+
141
+ 4. **When in doubt, start with a spec.** If the task is non-trivial and there's no spec, begin with `spec-driven-development`.
142
+
143
+ ## Lifecycle Sequence
144
+
145
+ For a complete feature, the typical skill sequence is:
146
+
147
+ ```
148
+ 1. interview-me → Extract what the user actually wants
149
+ 2. idea-refine → Refine vague ideas
150
+ 3. spec-driven-development → Define what we're building
151
+ 4. planning-and-task-breakdown → Break into verifiable chunks
152
+ 5. context-engineering → Load the right context
153
+ 6. source-driven-development → Verify against official docs
154
+ 7. incremental-implementation → Build slice by slice
155
+ 8. observability-and-instrumentation → Instrument as you build (runs parallel with 7-9, not after)
156
+ 9. doubt-driven-development → Cross-examine non-trivial decisions in-flight
157
+ 10. test-driven-development → Prove each slice works
158
+ 11. code-review-and-quality → Review before merge
159
+ 12. code-simplification → Reduce unnecessary complexity while preserving behavior
160
+ 13. git-workflow-and-versioning → Clean commit history
161
+ 14. documentation-and-adrs → Document decisions
162
+ 15. deprecation-and-migration → Retire old systems and move users safely when needed
163
+ 16. shipping-and-launch → Deploy safely
164
+ 17. compound-learning → Capture the session's lessons into the project's rules/docs
165
+ ```
166
+
167
+ Not every task needs every skill. A bug fix might only need: `debugging-and-error-recovery` → `test-driven-development` → `code-review-and-quality`.
168
+
169
+ ## Quick Reference
170
+
171
+ | Phase | Skill | One-Line Summary |
172
+ |-------|-------|-----------------|
173
+ | Define | interview-me | Surface what the user actually wants before any plan, spec, or code exists |
174
+ | Define | idea-refine | Refine ideas through structured divergent and convergent thinking |
175
+ | Define | spec-driven-development | Requirements and acceptance criteria before code |
176
+ | Plan | planning-and-task-breakdown | Decompose into small, verifiable tasks |
177
+ | Build | incremental-implementation | Thin vertical slices, test each before expanding |
178
+ | Build | source-driven-development | Verify against official docs before implementing |
179
+ | Build | doubt-driven-development | Adversarial fresh-context review of every non-trivial decision |
180
+ | Build | context-engineering | Right context at the right time |
181
+ | Build | frontend-ui-engineering | Production-quality UI with accessibility |
182
+ | Build | api-and-interface-design | Stable interfaces with clear contracts |
183
+ | Verify | test-driven-development | Failing test first, then make it pass |
184
+ | Verify | browser-testing-with-devtools | Chrome DevTools MCP for runtime verification |
185
+ | Verify | debugging-and-error-recovery | Reproduce → localize → fix → guard |
186
+ | Review | code-review-and-quality | Five-axis review with quality gates |
187
+ | Review | code-simplification | Preserve behavior while reducing unnecessary complexity |
188
+ | Review | security-and-hardening | OWASP prevention, input validation, least privilege |
189
+ | Review | performance-optimization | Measure first, optimize only what matters |
190
+ | Ship | git-workflow-and-versioning | Atomic commits, clean history |
191
+ | Ship | ci-cd-and-automation | Automated quality gates on every change |
192
+ | Ship | deprecation-and-migration | Remove old systems and migrate users safely |
193
+ | Ship | documentation-and-adrs | Document the why, not just the what |
194
+ | Ship | observability-and-instrumentation | Structured logs, RED metrics, traces, symptom-based alerts |
195
+ | Ship | shipping-and-launch | Pre-launch checklist, monitoring, rollback plan |
196
+ | Orchestrate | orchestration-verification | Acceptance assertions, parity inventory, structured returns |
197
+ | Learn | compound-learning | Session lessons → deduped, capped diffs on the project's rules/docs |
198
+ | Author | designing-agents | Author a persona, workflow skill, or pi harness |
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2025 Addy Osmani
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.