@chankov/agent-fleet 0.0.6 → 0.0.8
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.
- package/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.pi/harnesses/agent-hub/README.md +75 -16
- package/.pi/harnesses/agent-hub/artifacts.js +56 -2
- package/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.pi/harnesses/agent-hub/delegate.ts +58 -9
- package/.pi/harnesses/agent-hub/drift-watchdog.js +54 -8
- package/.pi/harnesses/agent-hub/helpers.ts +34 -0
- package/.pi/harnesses/agent-hub/index.ts +723 -159
- package/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +2 -2
- package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -11
- package/.pi/harnesses/agent-hub/package.json +1 -1
- package/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.pi/harnesses/agent-hub/return-contract.js +78 -0
- package/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.pi/harnesses/agent-hub/run-budget.js +29 -3
- package/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.pi/harnesses/agent-hub/spawn.ts +109 -1
- package/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
- package/.pi/harnesses/coms/README.md +4 -3
- package/.pi/harnesses/coms/index.ts +80 -58
- package/.pi/harnesses/coms/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/package.json +1 -1
- package/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.pi/harnesses/lib/herdr-client.ts +7 -2
- package/.pi/harnesses/lib/herdr-presence.ts +141 -30
- package/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.pi/harnesses/lib/hermes-monitor-registry.ts +1 -1
- package/.pi/harnesses/lib/hermes-monitor-socket.ts +47 -2
- package/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.claude/commands/build.md +44 -0
- package/.versions/0.0.7/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.7/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.7/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.7/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.7/.claude/commands/plan.md +16 -0
- package/.versions/0.0.7/.claude/commands/prime.md +22 -0
- package/.versions/0.0.7/.claude/commands/review.md +16 -0
- package/.versions/0.0.7/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.7/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.7/.claude/commands/ship.md +72 -0
- package/.versions/0.0.7/.claude/commands/spec.md +15 -0
- package/.versions/0.0.7/.claude/commands/test.md +19 -0
- package/.versions/0.0.7/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.7/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.7/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.7/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.7/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.7/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.7/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.7/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.7/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.7/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.7/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.7/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.7/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.7/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.7/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.7/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.7/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.7/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.7/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.7/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.7/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.7/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.7/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.7/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.7/.pi/extensions/package.json +9 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.7/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/README.md +857 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/delegate.ts +435 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/helpers.ts +248 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/index.ts +8609 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/return-contract.js +293 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/run-budget.js +181 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/spawn.ts +354 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
- package/.versions/0.0.7/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.7/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.7/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.7/.pi/harnesses/coms/README.md +93 -0
- package/.versions/0.0.7/.pi/harnesses/coms/index.ts +1767 -0
- package/.versions/0.0.7/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.7/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.7/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.versions/0.0.7/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.7/.pi/harnesses/lib/herdr-client.ts +463 -0
- package/.versions/0.0.7/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/0.0.7/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.7/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.7/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.7/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.7/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.7/.pi/prompts/af-doctor-agent-fleet.md +15 -0
- package/.versions/0.0.7/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.7/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.7/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.7/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.7/.pi/prompts/af-setup-agent-fleet.md +27 -0
- package/.versions/0.0.7/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.7/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.7/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.7/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.7/.version +1 -0
- package/.versions/0.0.7/agents/architect.md +23 -0
- package/.versions/0.0.7/agents/bowser.md +26 -0
- package/.versions/0.0.7/agents/builder.md +53 -0
- package/.versions/0.0.7/agents/code-reviewer.md +205 -0
- package/.versions/0.0.7/agents/deep-researcher.md +31 -0
- package/.versions/0.0.7/agents/documenter.md +18 -0
- package/.versions/0.0.7/agents/orchestrator.md +65 -0
- package/.versions/0.0.7/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.7/agents/planner.md +69 -0
- package/.versions/0.0.7/agents/releaser.md +24 -0
- package/.versions/0.0.7/agents/researcher.md +28 -0
- package/.versions/0.0.7/agents/security-auditor.md +166 -0
- package/.versions/0.0.7/agents/test-engineer.md +151 -0
- package/.versions/0.0.7/agents/web-debugger.md +42 -0
- package/.versions/0.0.7/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.7/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.7/docs/ARCHITECTURE.md +262 -0
- package/.versions/0.0.7/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.7/docs/claude-code-coms-bridge.md +109 -0
- package/.versions/0.0.7/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.7/docs/coms-hermes-bridge.md +189 -0
- package/.versions/0.0.7/docs/getting-started.md +231 -0
- package/.versions/0.0.7/docs/npm-install.md +337 -0
- package/.versions/0.0.7/docs/opencode-setup.md +249 -0
- package/.versions/0.0.7/docs/pi-extensions.md +293 -0
- package/.versions/0.0.7/docs/pi-setup.md +476 -0
- package/.versions/0.0.7/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.7/hermes/README.md +347 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.7/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.7/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/0.0.7/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.7/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.7/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.7/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/0.0.7/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/0.0.7/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/0.0.7/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.7/hooks/coms-stop-hook.mjs +84 -0
- package/.versions/0.0.7/hooks/hooks.json +14 -0
- package/.versions/0.0.7/hooks/session-start.sh +74 -0
- package/.versions/0.0.7/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.7/justfile +245 -0
- package/.versions/0.0.7/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.7/references/definition-of-done.md +67 -0
- package/.versions/0.0.7/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.7/references/observability-checklist.md +91 -0
- package/.versions/0.0.7/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.7/references/performance-checklist.md +153 -0
- package/.versions/0.0.7/references/prompting-patterns.md +380 -0
- package/.versions/0.0.7/references/security-checklist.md +179 -0
- package/.versions/0.0.7/references/testing-patterns.md +236 -0
- package/.versions/0.0.7/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.7/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.7/scripts/coms-claude-bridge.ts +401 -0
- package/.versions/0.0.7/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.7/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.7/scripts/fleet.ts +149 -0
- package/.versions/0.0.7/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.7/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/0.0.7/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/0.0.7/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/0.0.7/scripts/lib/claude-bridge-core.ts +165 -0
- package/.versions/0.0.7/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.7/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.7/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/0.0.7/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.7/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.7/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.7/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.7/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.7/scripts/lib/monitor-env.ts +120 -0
- package/.versions/0.0.7/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.7/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.7/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.7/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.7/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.7/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.7/scripts/team-up.ts +360 -0
- package/.versions/0.0.7/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.7/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.7/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.7/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.7/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.7/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.7/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.7/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.7/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.7/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.7/skills/guided-workspace-setup/SKILL.md +544 -0
- package/.versions/0.0.7/skills/guided-workspace-setup/companion-manifest.json +35 -0
- package/.versions/0.0.7/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.7/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.7/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.7/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.7/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.7/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.7/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.7/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.7/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.7/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.7/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.7/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.7/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.7/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.7/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.7/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/.versions/0.0.8/.claude/commands/build.md +44 -0
- package/.versions/0.0.8/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.8/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.8/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.8/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.8/.claude/commands/plan.md +16 -0
- package/.versions/0.0.8/.claude/commands/prime.md +22 -0
- package/.versions/0.0.8/.claude/commands/review.md +16 -0
- package/.versions/0.0.8/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.8/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.versions/0.0.8/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.8/.claude/commands/ship.md +72 -0
- package/.versions/0.0.8/.claude/commands/spec.md +15 -0
- package/.versions/0.0.8/.claude/commands/test.md +19 -0
- package/.versions/0.0.8/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.8/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.8/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.8/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.8/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.8/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.8/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.8/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.8/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.8/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.8/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.8/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.8/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.8/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.8/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.8/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.8/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.8/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.8/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.8/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.8/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.8/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.8/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.8/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.8/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.8/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.8/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.8/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.8/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.8/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.8/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.8/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.8/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.8/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.8/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.8/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.8/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.8/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.8/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.8/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.8/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.8/.pi/extensions/package.json +9 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.8/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/README.md +857 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/delegate.ts +435 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/helpers.ts +248 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/index.ts +8609 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/return-contract.js +293 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/run-budget.js +181 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/spawn.ts +354 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/spawned-peers.js +74 -0
- package/.versions/0.0.8/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.8/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.8/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.8/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.8/.pi/harnesses/coms/README.md +93 -0
- package/.versions/0.0.8/.pi/harnesses/coms/index.ts +1767 -0
- package/.versions/0.0.8/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.8/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.8/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.8/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.8/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.8/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.8/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.versions/0.0.8/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.8/.pi/harnesses/lib/herdr-client.ts +463 -0
- package/.versions/0.0.8/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/0.0.8/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/0.0.8/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.8/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/0.0.8/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.8/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/0.0.8/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.8/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.8/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.8/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.8/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.8/.pi/prompts/af-doctor-agent-fleet.md +15 -0
- package/.versions/0.0.8/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.8/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.8/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.8/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.8/.pi/prompts/af-setup-agent-fleet.md +27 -0
- package/.versions/0.0.8/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.8/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.8/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.8/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.8/.version +1 -0
- package/.versions/0.0.8/agents/architect.md +23 -0
- package/.versions/0.0.8/agents/bowser.md +26 -0
- package/.versions/0.0.8/agents/builder.md +53 -0
- package/.versions/0.0.8/agents/code-reviewer.md +205 -0
- package/.versions/0.0.8/agents/deep-researcher.md +31 -0
- package/.versions/0.0.8/agents/documenter.md +18 -0
- package/.versions/0.0.8/agents/orchestrator.md +65 -0
- package/.versions/0.0.8/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.8/agents/planner.md +69 -0
- package/.versions/0.0.8/agents/releaser.md +24 -0
- package/.versions/0.0.8/agents/researcher.md +28 -0
- package/.versions/0.0.8/agents/security-auditor.md +166 -0
- package/.versions/0.0.8/agents/test-engineer.md +151 -0
- package/.versions/0.0.8/agents/web-debugger.md +42 -0
- package/.versions/0.0.8/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.8/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.8/docs/ARCHITECTURE.md +262 -0
- package/.versions/0.0.8/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.8/docs/claude-code-coms-bridge.md +109 -0
- package/.versions/0.0.8/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.8/docs/coms-hermes-bridge.md +189 -0
- package/.versions/0.0.8/docs/getting-started.md +231 -0
- package/.versions/0.0.8/docs/npm-install.md +337 -0
- package/.versions/0.0.8/docs/opencode-setup.md +249 -0
- package/.versions/0.0.8/docs/pi-extensions.md +293 -0
- package/.versions/0.0.8/docs/pi-setup.md +476 -0
- package/.versions/0.0.8/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.8/hermes/README.md +347 -0
- package/.versions/0.0.8/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/0.0.8/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/0.0.8/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.8/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.8/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/0.0.8/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.8/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.8/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.8/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/0.0.8/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/0.0.8/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/0.0.8/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.8/hooks/coms-stop-hook.mjs +84 -0
- package/.versions/0.0.8/hooks/hooks.json +14 -0
- package/.versions/0.0.8/hooks/session-start.sh +74 -0
- package/.versions/0.0.8/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.8/justfile +245 -0
- package/.versions/0.0.8/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.8/references/definition-of-done.md +67 -0
- package/.versions/0.0.8/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.8/references/observability-checklist.md +91 -0
- package/.versions/0.0.8/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.8/references/performance-checklist.md +153 -0
- package/.versions/0.0.8/references/prompting-patterns.md +380 -0
- package/.versions/0.0.8/references/security-checklist.md +179 -0
- package/.versions/0.0.8/references/testing-patterns.md +236 -0
- package/.versions/0.0.8/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.8/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.8/scripts/coms-claude-bridge.ts +401 -0
- package/.versions/0.0.8/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.8/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.8/scripts/fleet.ts +149 -0
- package/.versions/0.0.8/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.8/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/0.0.8/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/0.0.8/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/0.0.8/scripts/lib/claude-bridge-core.ts +165 -0
- package/.versions/0.0.8/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.8/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.8/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/0.0.8/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.8/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.8/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.8/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.8/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/0.0.8/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.8/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.8/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.8/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.8/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.8/scripts/lib/monitor-env.ts +120 -0
- package/.versions/0.0.8/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.8/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.8/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.8/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.8/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.8/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.8/scripts/team-up.ts +360 -0
- package/.versions/0.0.8/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.8/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.8/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.8/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.8/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.8/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.8/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.8/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.8/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.8/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.8/skills/guided-workspace-setup/SKILL.md +544 -0
- package/.versions/0.0.8/skills/guided-workspace-setup/companion-manifest.json +36 -0
- package/.versions/0.0.8/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.8/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.8/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.8/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.8/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.8/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.8/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.8/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.8/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.8/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.8/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.8/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.8/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.8/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.8/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.8/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +140 -0
- package/README.md +175 -18
- package/agents/code-reviewer.md +2 -2
- package/agents/orchestrator.md +11 -0
- package/agents/plan-reviewer.md +1 -1
- package/agents/planner.md +1 -1
- package/agents/security-auditor.md +1 -1
- package/bin/cli.js +40 -1
- package/bin/lib/hermes-profile-artifact.js +144 -0
- package/bin/lib/set-hermes-watchdog.js +173 -0
- package/bin/set-hermes-watchdog.js +26 -0
- package/docs/ARCHITECTURE.md +64 -12
- package/docs/agent-fleet-setup.md +2 -2
- package/docs/claude-code-coms-bridge.md +7 -1
- package/docs/coms-hermes-bridge.md +10 -0
- package/docs/getting-started.md +48 -0
- package/docs/hermes-watchdog-supervisor.md +140 -0
- package/hermes/README.md +135 -19
- package/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/dist/index.js +10 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/hooks/coms-stop-hook.mjs +12 -1
- package/package.json +11 -2
- package/scripts/coms-claude-bridge.ts +154 -39
- package/scripts/fleet.ts +9 -1
- package/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/scripts/lib/claude-bridge-core.ts +65 -0
- package/scripts/lib/coms-envelope.ts +44 -1
- package/scripts/lib/hermes-monitor-events.ts +1 -0
- package/scripts/lib/monitor-env.ts +120 -0
- package/scripts/team-snapshot.ts +1 -1
- package/scripts/team-up.ts +10 -1
- package/skills/guided-workspace-setup/companion-manifest.json +1 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -15
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -19
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -13
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -11
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -9
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -17
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -34
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -39
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -12
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -22
|
@@ -0,0 +1,191 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: using-agent-skills
|
|
3
|
+
description: Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Using Agent Skills
|
|
7
|
+
|
|
8
|
+
## Overview
|
|
9
|
+
|
|
10
|
+
Agent Skills 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? → idea-refine
|
|
21
|
+
├── New project/feature/change? ──→ spec-driven-development
|
|
22
|
+
├── Have a spec, need tasks? ──────→ planning-and-task-breakdown
|
|
23
|
+
├── Implementing code? ────────────→ incremental-implementation
|
|
24
|
+
│ ├── UI work? ─────────────────→ frontend-ui-engineering
|
|
25
|
+
│ ├── API work? ────────────────→ api-and-interface-design
|
|
26
|
+
│ ├── Need better context? ─────→ context-engineering
|
|
27
|
+
│ ├── Need doc-verified code? ───→ source-driven-development
|
|
28
|
+
│ └── Stakes high / unfamiliar code? ──→ doubt-driven-development
|
|
29
|
+
├── Writing/running tests? ────────→ test-driven-development
|
|
30
|
+
│ └── Browser-based? ───────────→ browser-testing-with-devtools
|
|
31
|
+
├── Something broke? ──────────────→ debugging-and-error-recovery
|
|
32
|
+
├── Reviewing code? ───────────────→ code-review-and-quality
|
|
33
|
+
│ ├── Too complex? ─────────────→ code-simplification
|
|
34
|
+
│ ├── Security concerns? ───────→ security-and-hardening
|
|
35
|
+
│ └── Performance concerns? ────→ performance-optimization
|
|
36
|
+
├── Committing/branching? ─────────→ git-workflow-and-versioning
|
|
37
|
+
├── CI/CD pipeline work? ──────────→ ci-cd-and-automation
|
|
38
|
+
├── Deprecating/migrating? ────────→ deprecation-and-migration
|
|
39
|
+
├── Writing docs/ADRs? ───────────→ documentation-and-adrs
|
|
40
|
+
├── Adding logs/metrics/alerts? ───→ observability-and-instrumentation
|
|
41
|
+
└── Deploying/launching? ─────────→ shipping-and-launch
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
## Core Operating Behaviors
|
|
45
|
+
|
|
46
|
+
These behaviors apply at all times, across all skills. They are non-negotiable.
|
|
47
|
+
|
|
48
|
+
### 1. Surface Assumptions
|
|
49
|
+
|
|
50
|
+
Before implementing anything non-trivial, explicitly state your assumptions:
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
ASSUMPTIONS I'M MAKING:
|
|
54
|
+
1. [assumption about requirements]
|
|
55
|
+
2. [assumption about architecture]
|
|
56
|
+
3. [assumption about scope]
|
|
57
|
+
→ Correct me now or I'll proceed with these.
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
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.
|
|
61
|
+
|
|
62
|
+
### 2. Manage Confusion Actively
|
|
63
|
+
|
|
64
|
+
When you encounter inconsistencies, conflicting requirements, or unclear specifications:
|
|
65
|
+
|
|
66
|
+
1. **STOP.** Do not proceed with a guess.
|
|
67
|
+
2. Name the specific confusion.
|
|
68
|
+
3. Present the tradeoff or ask the clarifying question.
|
|
69
|
+
4. Wait for resolution before continuing.
|
|
70
|
+
|
|
71
|
+
**Bad:** Silently picking one interpretation and hoping it's right.
|
|
72
|
+
**Good:** "I see X in the spec but Y in the existing code. Which takes precedence?"
|
|
73
|
+
|
|
74
|
+
### 3. Push Back When Warranted
|
|
75
|
+
|
|
76
|
+
You are not a yes-machine. When an approach has clear problems:
|
|
77
|
+
|
|
78
|
+
- Point out the issue directly
|
|
79
|
+
- Explain the concrete downside (quantify when possible — "this adds ~200ms latency" not "this might be slower")
|
|
80
|
+
- Propose an alternative
|
|
81
|
+
- Accept the human's decision if they override with full information
|
|
82
|
+
|
|
83
|
+
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.
|
|
84
|
+
|
|
85
|
+
### 4. Enforce Simplicity
|
|
86
|
+
|
|
87
|
+
Your natural tendency is to overcomplicate. Actively resist it.
|
|
88
|
+
|
|
89
|
+
Before finishing any implementation, ask:
|
|
90
|
+
- Can this be done in fewer lines?
|
|
91
|
+
- Are these abstractions earning their complexity?
|
|
92
|
+
- Would a staff engineer look at this and say "why didn't you just..."?
|
|
93
|
+
|
|
94
|
+
If you build 1000 lines and 100 would suffice, you have failed. Prefer the boring, obvious solution. Cleverness is expensive.
|
|
95
|
+
|
|
96
|
+
### 5. Maintain Scope Discipline
|
|
97
|
+
|
|
98
|
+
Touch only what you're asked to touch.
|
|
99
|
+
|
|
100
|
+
Do NOT:
|
|
101
|
+
- Remove comments you don't understand
|
|
102
|
+
- "Clean up" code orthogonal to the task
|
|
103
|
+
- Refactor adjacent systems as a side effect
|
|
104
|
+
- Delete code that seems unused without explicit approval
|
|
105
|
+
- Add features not in the spec because they "seem useful"
|
|
106
|
+
|
|
107
|
+
Your job is surgical precision, not unsolicited renovation.
|
|
108
|
+
|
|
109
|
+
### 6. Verify, Don't Assume
|
|
110
|
+
|
|
111
|
+
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).
|
|
112
|
+
|
|
113
|
+
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.
|
|
114
|
+
|
|
115
|
+
## Failure Modes to Avoid
|
|
116
|
+
|
|
117
|
+
These are the subtle errors that look like productivity but create problems:
|
|
118
|
+
|
|
119
|
+
1. Making wrong assumptions without checking
|
|
120
|
+
2. Not managing your own confusion — plowing ahead when lost
|
|
121
|
+
3. Not surfacing inconsistencies you notice
|
|
122
|
+
4. Not presenting tradeoffs on non-obvious decisions
|
|
123
|
+
5. Being sycophantic ("Of course!") to approaches with clear problems
|
|
124
|
+
6. Overcomplicating code and APIs
|
|
125
|
+
7. Modifying code or comments orthogonal to the task
|
|
126
|
+
8. Removing things you don't fully understand
|
|
127
|
+
9. Building without a spec because "it's obvious"
|
|
128
|
+
10. Skipping verification because "it looks right"
|
|
129
|
+
|
|
130
|
+
## Skill Rules
|
|
131
|
+
|
|
132
|
+
1. **Check for an applicable skill before starting work.** Skills encode processes that prevent common mistakes.
|
|
133
|
+
|
|
134
|
+
2. **Skills are workflows, not suggestions.** Follow the steps in order. Don't skip verification steps.
|
|
135
|
+
|
|
136
|
+
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.
|
|
137
|
+
|
|
138
|
+
4. **When in doubt, start with a spec.** If the task is non-trivial and there's no spec, begin with `spec-driven-development`.
|
|
139
|
+
|
|
140
|
+
## Lifecycle Sequence
|
|
141
|
+
|
|
142
|
+
For a complete feature, the typical skill sequence is:
|
|
143
|
+
|
|
144
|
+
```
|
|
145
|
+
1. interview-me → Extract what the user actually wants
|
|
146
|
+
2. idea-refine → Refine vague ideas
|
|
147
|
+
3. spec-driven-development → Define what we're building
|
|
148
|
+
4. planning-and-task-breakdown → Break into verifiable chunks
|
|
149
|
+
5. context-engineering → Load the right context
|
|
150
|
+
6. source-driven-development → Verify against official docs
|
|
151
|
+
7. incremental-implementation → Build slice by slice
|
|
152
|
+
8. observability-and-instrumentation → Instrument as you build (runs parallel with 7-9, not after)
|
|
153
|
+
9. doubt-driven-development → Cross-examine non-trivial decisions in-flight
|
|
154
|
+
10. test-driven-development → Prove each slice works
|
|
155
|
+
11. code-review-and-quality → Review before merge
|
|
156
|
+
12. code-simplification → Reduce unnecessary complexity while preserving behavior
|
|
157
|
+
13. git-workflow-and-versioning → Clean commit history
|
|
158
|
+
14. documentation-and-adrs → Document decisions
|
|
159
|
+
15. deprecation-and-migration → Retire old systems and move users safely when needed
|
|
160
|
+
16. shipping-and-launch → Deploy safely
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
Not every task needs every skill. A bug fix might only need: `debugging-and-error-recovery` → `test-driven-development` → `code-review-and-quality`.
|
|
164
|
+
|
|
165
|
+
## Quick Reference
|
|
166
|
+
|
|
167
|
+
| Phase | Skill | One-Line Summary |
|
|
168
|
+
|-------|-------|-----------------|
|
|
169
|
+
| Define | interview-me | Surface what the user actually wants before any plan, spec, or code exists |
|
|
170
|
+
| Define | idea-refine | Refine ideas through structured divergent and convergent thinking |
|
|
171
|
+
| Define | spec-driven-development | Requirements and acceptance criteria before code |
|
|
172
|
+
| Plan | planning-and-task-breakdown | Decompose into small, verifiable tasks |
|
|
173
|
+
| Build | incremental-implementation | Thin vertical slices, test each before expanding |
|
|
174
|
+
| Build | source-driven-development | Verify against official docs before implementing |
|
|
175
|
+
| Build | doubt-driven-development | Adversarial fresh-context review of every non-trivial decision |
|
|
176
|
+
| Build | context-engineering | Right context at the right time |
|
|
177
|
+
| Build | frontend-ui-engineering | Production-quality UI with accessibility |
|
|
178
|
+
| Build | api-and-interface-design | Stable interfaces with clear contracts |
|
|
179
|
+
| Verify | test-driven-development | Failing test first, then make it pass |
|
|
180
|
+
| Verify | browser-testing-with-devtools | Chrome DevTools MCP for runtime verification |
|
|
181
|
+
| Verify | debugging-and-error-recovery | Reproduce → localize → fix → guard |
|
|
182
|
+
| Review | code-review-and-quality | Five-axis review with quality gates |
|
|
183
|
+
| Review | code-simplification | Preserve behavior while reducing unnecessary complexity |
|
|
184
|
+
| Review | security-and-hardening | OWASP prevention, input validation, least privilege |
|
|
185
|
+
| Review | performance-optimization | Measure first, optimize only what matters |
|
|
186
|
+
| Ship | git-workflow-and-versioning | Atomic commits, clean history |
|
|
187
|
+
| Ship | ci-cd-and-automation | Automated quality gates on every change |
|
|
188
|
+
| Ship | deprecation-and-migration | Remove old systems and migrate users safely |
|
|
189
|
+
| Ship | documentation-and-adrs | Document the why, not just the what |
|
|
190
|
+
| Ship | observability-and-instrumentation | Structured logs, RED metrics, traces, symptom-based alerts |
|
|
191
|
+
| Ship | shipping-and-launch | Pre-launch checklist, monitoring, rollback plan |
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:incremental-implementation skill alongside agent-fleet:test-driven-development.
|
|
6
|
+
|
|
7
|
+
## Modes
|
|
8
|
+
|
|
9
|
+
- **`/build`** — implement the *next* pending task, then stop (careful, one slice at a time).
|
|
10
|
+
- **`/build auto`** — generate the plan if needed, get a single approval, then implement *every* task without stopping between them.
|
|
11
|
+
|
|
12
|
+
`$ARGUMENTS` selects the mode. Treat `auto` (canonical) or `all` as autonomous mode; anything else (or empty) is the default single-task mode. Note: autonomous mode is not faster *per task* — it runs the same test-driven loop — it only removes the human stepping *between* tasks.
|
|
13
|
+
|
|
14
|
+
## Default: one task
|
|
15
|
+
|
|
16
|
+
Pick the next pending task from the plan. Then:
|
|
17
|
+
|
|
18
|
+
1. Read the task's acceptance criteria
|
|
19
|
+
2. Load relevant context (existing code, patterns, types)
|
|
20
|
+
3. Write a failing test for the expected behavior (RED)
|
|
21
|
+
4. Implement the minimum code to pass the test (GREEN)
|
|
22
|
+
5. Run the full test suite to check for regressions
|
|
23
|
+
6. Run the build to verify compilation
|
|
24
|
+
7. Commit with a descriptive message
|
|
25
|
+
8. Mark the task complete and stop
|
|
26
|
+
|
|
27
|
+
## Autonomous: the whole plan (`/build auto`)
|
|
28
|
+
|
|
29
|
+
Use this once a spec exists and you want to collapse plan + build into one run. It removes the manual stepping between tasks — **not** the verification. Every task still earns a passing test and its own commit.
|
|
30
|
+
|
|
31
|
+
1. **Require a spec.** Look only for a spec at a known path: `SPEC.md` at the repo root, `docs/SPEC.md`, or a file under `spec/`. A README or arbitrary doc does **not** count. If none exists, stop and tell the user to run `/spec` first — do not invent requirements.
|
|
32
|
+
2. **Establish a clean baseline.** Run `git status --porcelain`. If there are uncommitted changes outside the expected planning artifacts (`SPEC.md`, `docs/SPEC.md`, `spec/*`, `tasks/plan.md`, `tasks/todo.md`), stop and ask the user to commit, stash, or confirm how to handle them. Autonomous per-task commits must not absorb unrelated local work, or the clean-rollback guarantee breaks.
|
|
33
|
+
3. **Plan if needed.** If there is no `tasks/plan.md`, invoke agent-fleet:planning-and-task-breakdown to generate one.
|
|
34
|
+
4. **Single checkpoint.** Present the full plan and wait for an unambiguous affirmative (e.g. "approve", "go", "yes"). Treat hedged responses ("looks reasonable", "I guess") as **not** approved. This is the only human gate — after approval, run autonomously. If you generated `tasks/plan.md`, commit it as a single preparatory commit now so it doesn't bleed into the first task's commit.
|
|
35
|
+
5. **Execute every task in dependency order.** Use each task's declared dependencies; if they aren't explicit, execute in the order the plan lists them. For each task, run the full default loop above (RED → GREEN → regression → build → commit → mark complete). Stage only the files that task touched plus its task-status update — never `git add -A` blindly — and make one commit per task so any point is a clean rollback.
|
|
36
|
+
6. **Stop and ask the user** (do not push through) when:
|
|
37
|
+
- a test can't be made to pass or the build breaks without an obvious fix → follow agent-fleet:debugging-and-error-recovery
|
|
38
|
+
- the spec is ambiguous, or a task needs a decision the spec doesn't cover
|
|
39
|
+
- a task is high-risk or irreversible — auth/permission changes, destructive data migrations, payments, deletions, deploys, anything touching secrets, **or anything you can't undo with `git revert`** → follow agent-fleet:doubt-driven-development and get explicit sign-off before continuing
|
|
40
|
+
|
|
41
|
+
After the user resolves a blocker, they re-invoke `/build auto` — it resumes from the next pending task.
|
|
42
|
+
7. **Summarize at the end:** tasks completed, tests added, commits made, and anything skipped, flagged, or left for the user.
|
|
43
|
+
|
|
44
|
+
If any step fails, follow the agent-fleet:debugging-and-error-recovery skill.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Simplify code for clarity and maintainability — reduce complexity without changing behavior
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:code-simplification skill.
|
|
6
|
+
|
|
7
|
+
Simplify recently changed code (or the specified scope) while preserving exact behavior:
|
|
8
|
+
|
|
9
|
+
1. Read CLAUDE.md and study project conventions
|
|
10
|
+
2. Identify the target code — recent changes unless a broader scope is specified
|
|
11
|
+
3. Understand the code's purpose, callers, edge cases, and test coverage before touching it
|
|
12
|
+
4. Scan for simplification opportunities:
|
|
13
|
+
- Deep nesting → guard clauses or extracted helpers
|
|
14
|
+
- Long functions → split by responsibility
|
|
15
|
+
- Nested ternaries → if/else or switch
|
|
16
|
+
- Generic names → descriptive names
|
|
17
|
+
- Duplicated logic → shared functions
|
|
18
|
+
- Dead code → remove after confirming
|
|
19
|
+
5. Apply each simplification incrementally — run tests after each change
|
|
20
|
+
6. Verify all tests pass, the build succeeds, and the diff is clean
|
|
21
|
+
|
|
22
|
+
If tests fail after a simplification, revert that change and reconsider. Use `code-review-and-quality` to review the result.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Design and write a new agent persona (agents/), workflow skill (skills/), or pi harness (.pi/harnesses/)
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:designing-agents skill.
|
|
6
|
+
|
|
7
|
+
Begin by understanding what the user wants to author:
|
|
8
|
+
1. Is this a **persona** (a role/lens the agent adopts, e.g. a reviewer or auditor), a **skill** (a repeatable workflow with gated steps and verification), or a **pi harness** (a TypeScript pi extension that reshapes the session — footer, tool-call gate, new command, or orchestrator)?
|
|
9
|
+
2. The one-sentence purpose and when it should be invoked
|
|
10
|
+
3. The framework or steps — dimensions evaluated (persona), ordered workflow (skill), or session surface and events hooked (harness)
|
|
11
|
+
4. Explicit non-goals and scope limits
|
|
12
|
+
5. Output shape — what a typical invocation should produce
|
|
13
|
+
|
|
14
|
+
Then scan the target location (`agents/`, `skills/`, or `.pi/harnesses/`) for overlap, draft the artifact using the matching template — four-block persona structure, the section order from `docs/skill-anatomy.md`, or the harness pattern in `skills/designing-agents/pi-harness-authoring.md` — verify the draft against `references/prompting-patterns.md`, and confirm with the user before writing the file(s).
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the Doctor scan from the `agent-fleet:guided-workspace-setup` skill — Step 5 (the preflight scan) — without running the rest of the install flow. Use this when the user wants the repair pass on its own; the full `/setup-agent-fleet` flow runs the same scan automatically as soon as it detects prior install state.
|
|
6
|
+
|
|
7
|
+
Walk every install-target directory the chosen coding agent uses (`agents/`, `.claude/agents/`, `.opencode/agent/` (+ legacy `.opencode/agents/`), `.pi/agents/`, `.claude/skills/`, `.opencode/skills/`, `.pi/skills/`, `.agents/skills`, `.claude/commands/`, `.opencode/commands/`, `.pi/prompts/`, `.claude/references/`, `.claude/hooks/`). For each broken symlink, resolve where it pointed, look for a canonical replacement in the source `agents/` and `skills/` trees, and offer to repair or delete (persona links under `.claude/agents/` and `.opencode/agent(s)/` are repaired by regenerating a transformed copy via `transform-persona`, not by re-symlinking the raw source). Common stale names from the pre-merge persona layout: `reviewer` → `code-reviewer`, `red-team` → `security-auditor`.
|
|
8
|
+
|
|
9
|
+
Also flag and offer to rewrite any remaining YAML configs (`teams.yaml`, `peers.yaml`, etc.) that still reference removed persona names.
|
|
10
|
+
|
|
11
|
+
Also flag malformed peer entries in `.pi/agents/peers.yaml`: field lines (`persona:`, `model:`, ...) that sit under a team heading before any `- name: ...` list item. The team-up launcher's minimal parser silently drops such lines, so the peer never spawns and nothing errors — the usual cause is a `- name:` line lost in an edit. These findings are advisory only: report them with the missing `- name: <peer>` suggestion, never rewrite the file.
|
|
12
|
+
|
|
13
|
+
Also validate `.ai/agent-fleet-overrides.md` when it exists, against the schema in `docs/agent-fleet-setup.md`: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed `agent-hub` keys, missing `rules:` folders and `docs:` entry points, and `## env` `required:` names that are neither set nor declared in the root `.env`. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
|
|
14
|
+
|
|
15
|
+
Present the findings per the skill's Step 1 interaction contract: print a short text summary (counts per kind, advisory findings as report-only text), then ask one `AskUserQuestion` multi-select — *"Which fixes should I apply now?"* — each option titled `<path> — <issue>` with the proposed fix as its description, chunked at ≤ 4 options per question; an empty selection applies nothing.
|
|
16
|
+
|
|
17
|
+
Never overwrite a regular file — only act on symlinks whose target is missing. Report `repaired`, `deleted`, and `skipped` counts, and append a `## doctor-runs` line to `.ai/agent-fleet-setup.md` with the date, agent, phase (`standalone`), and counts.
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Orchestrate a config-defined team of subagents — route planner/builder (and more) as a runtime roster, handling NEEDS_RESEARCH and PLAN_FILE handoffs
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
You are the **orchestrator**. The primary agent drives a team of installed Claude Code
|
|
6
|
+
subagents to deliver the task in `$ARGUMENTS`. Subagents cannot nest — **all dispatching is
|
|
7
|
+
yours**.
|
|
8
|
+
|
|
9
|
+
## Roles
|
|
10
|
+
|
|
11
|
+
| Role | What it does |
|
|
12
|
+
|---|---|
|
|
13
|
+
| `researcher` | Always-available read-only recon. Cites `file:line`. Never edits. |
|
|
14
|
+
| `planner` | Writes a plan doc only; ends with `PLAN_FILE: <path>` or pauses on `NEEDS_RESEARCH:`. |
|
|
15
|
+
| `builder` | Implements in small increments; may pause on `NEEDS_RESEARCH:`. |
|
|
16
|
+
| `plan-reviewer` / `code-reviewer` | Read-only; their whole result is findings (no handoff marker). |
|
|
17
|
+
|
|
18
|
+
## Step 0 — Resolve the team
|
|
19
|
+
|
|
20
|
+
1. Read `.claude/orchestrate-teams.yaml` (a map of team-name → ordered persona list).
|
|
21
|
+
2. Resolve team + task from `$ARGUMENTS`:
|
|
22
|
+
- Treat the **first token** as a team name **only** when it is a bare single word that
|
|
23
|
+
exactly matches a config key **and** is followed by the rest of the task. To force a
|
|
24
|
+
team explicitly, the user writes `/orchestrate team=<name> <task>`. Otherwise the
|
|
25
|
+
team is the first key (`default`) and all of `$ARGUMENTS` is the task.
|
|
26
|
+
- **Fallbacks:** if the config is **absent / empty / fails to parse**, fall back to the
|
|
27
|
+
built-in `planner` + `builder` default and **say which fallback fired** (don't proceed
|
|
28
|
+
silently). If a named team is requested but not found, list the available team keys and
|
|
29
|
+
ask rather than guessing.
|
|
30
|
+
3. **Validate personas:** each persona in the resolved team must exist in `.claude/agents/`.
|
|
31
|
+
Skip-with-warning any that don't. If every persona is missing, fall back to the built-in
|
|
32
|
+
default.
|
|
33
|
+
4. List the resolved team back to the user before dispatching.
|
|
34
|
+
|
|
35
|
+
`researcher` / `deep-researcher` are **always available** even when not listed in the team.
|
|
36
|
+
|
|
37
|
+
## Step 1 — The team is a roster, not a fixed pipeline
|
|
38
|
+
|
|
39
|
+
The persona list is the set of specialists you may route to; **you decide the order at
|
|
40
|
+
runtime from the task state** (the listed order is only a sensible starting default). So:
|
|
41
|
+
|
|
42
|
+
- **Skip `planner`** when a usable plan already exists (the user passed a `PLAN_FILE` or
|
|
43
|
+
pointed at one) — go straight to `builder`.
|
|
44
|
+
- **Re-dispatch `researcher` at any point** — after `planner`, mid-build — whenever a
|
|
45
|
+
specialist needs a fact checked, not only as a first step.
|
|
46
|
+
- **Loop back to `planner`** if `builder` surfaces that the plan is wrong.
|
|
47
|
+
|
|
48
|
+
Do **not** enforce a hard `researcher → planner → builder` sequence.
|
|
49
|
+
|
|
50
|
+
## The Verification Contract (applies across every step)
|
|
51
|
+
|
|
52
|
+
Read `skills/orchestration-verification/SKILL.md` before non-trivial work and hold its
|
|
53
|
+
contract for the whole run. Subagents here cannot persist a shared ledger, so **you** keep
|
|
54
|
+
the acceptance assertions in your own working notes and refuse "done" until each is proven.
|
|
55
|
+
|
|
56
|
+
- **Build the assertions first.** Before dispatching `builder` for any non-trivial task,
|
|
57
|
+
convert the request into numbered, tagged assertions (`test` | `runtime-ui` | `code-grep`
|
|
58
|
+
| `manual`, one checkable pass condition each). Pass the relevant assertions **verbatim**
|
|
59
|
+
into each dispatch and advance only on assertions that come back *proven with named
|
|
60
|
+
evidence* — propagation in prose is not verification.
|
|
61
|
+
- **Inventory parity for "behave like X" requests.** When the request is "make X behave like
|
|
62
|
+
existing Y", dispatch `researcher` / `deep-researcher` **first** to enumerate every site
|
|
63
|
+
where the exemplar is special-cased (flags, branches, display, validation, translations,
|
|
64
|
+
fixtures, tests), and turn each site into an assertion covering the *whole* set — otherwise
|
|
65
|
+
the exemplar ships and its siblings are missed.
|
|
66
|
+
- **Require runtime proof for UI assertions.** A `runtime-ui` assertion (visibility,
|
|
67
|
+
placement, "appears in the table") is closed only by an actual runtime observation via
|
|
68
|
+
`browser-testing-with-devtools`, never a static review.
|
|
69
|
+
- **Accept assertion status, not verdicts.** Treat specialist returns as `assertions_proven`
|
|
70
|
+
/ `assertions_unproven` / `assertions_failed`; demote any "approved" claim with no named
|
|
71
|
+
evidence to unproven and re-dispatch it.
|
|
72
|
+
- **Reset on "wrong again".** When the user reports a delivered requirement is wrong again,
|
|
73
|
+
treat prior summaries as suspect, rebuild the affected assertions from the **latest**
|
|
74
|
+
correction (re-running the parity inventory for "behave like" cases), then re-dispatch.
|
|
75
|
+
|
|
76
|
+
## Step 2 — Route to specialists, honouring handoff markers
|
|
77
|
+
|
|
78
|
+
State the chosen next step (and why) before each dispatch, so routing is visible.
|
|
79
|
+
|
|
80
|
+
- `planner` → read its `PLAN_FILE: <path>` and load the plan.
|
|
81
|
+
- `builder` → loop over the plan's `## Task List`, **one task per dispatch**, checking each
|
|
82
|
+
task's acceptance criteria **and the relevant acceptance assertions** before moving on.
|
|
83
|
+
- **Marker-less personas** (`plan-reviewer` / `code-reviewer`) emit no handoff marker —
|
|
84
|
+
their returned report **is** the result; "done" = the report came back, nothing to wait
|
|
85
|
+
for. Fold findings forward; if a `code-reviewer` raised must-fix issues, loop back to
|
|
86
|
+
`builder`.
|
|
87
|
+
|
|
88
|
+
## Step 3 — NEEDS_RESEARCH dispatch (core)
|
|
89
|
+
|
|
90
|
+
Whenever any persona's result contains one or more `NEEDS_RESEARCH: <question>` lines:
|
|
91
|
+
|
|
92
|
+
1. Pause that track.
|
|
93
|
+
2. Dispatch `researcher` (read-only) once per question — in parallel when independent.
|
|
94
|
+
3. Collect the findings.
|
|
95
|
+
4. Resume the paused persona by re-dispatching it with the **original task plus the
|
|
96
|
+
findings inlined**.
|
|
97
|
+
|
|
98
|
+
**Never** answer a `NEEDS_RESEARCH` by guessing.
|
|
99
|
+
|
|
100
|
+
## Step 4 — Reviewer only if present
|
|
101
|
+
|
|
102
|
+
The `default` roster has **no reviewer**. After the final builder task's acceptance criteria
|
|
103
|
+
pass, report completion and **state explicitly that review/verification was not run** and
|
|
104
|
+
which acceptance assertions therefore remain unproven (the user can pick the `full` team or
|
|
105
|
+
run `/review`). When the active team *does* include a reviewer, run it as a normal step and
|
|
106
|
+
require it to report parity across sibling cases, not just the exemplar.
|
|
107
|
+
|
|
108
|
+
## Step 5 — Report
|
|
109
|
+
|
|
110
|
+
Report crisply: **active team**, what changed, which acceptance assertions are **proven (with
|
|
111
|
+
evidence)**, which remain **unproven or failed**, and what's next. Never report "done" while a
|
|
112
|
+
relevant assertion is unproven.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Break work into small verifiable tasks with acceptance criteria and dependency ordering
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:planning-and-task-breakdown skill.
|
|
6
|
+
|
|
7
|
+
Read the existing spec (SPEC.md or equivalent) and the relevant codebase sections. Then:
|
|
8
|
+
|
|
9
|
+
1. Enter plan mode — read only, no code changes
|
|
10
|
+
2. Identify the dependency graph between components
|
|
11
|
+
3. Slice work vertically (one complete path per task, not horizontal layers)
|
|
12
|
+
4. Write tasks with acceptance criteria and verification steps
|
|
13
|
+
5. Add checkpoints between phases
|
|
14
|
+
6. Present the plan for human review
|
|
15
|
+
|
|
16
|
+
Save the plan to the location the `planning-and-task-breakdown` skill defines (default `docs/plans/{area}/PLAN-{prd-name}-{phase}.md`, with the task list embedded — no separate todo file; overridable per project via `.ai/agent-fleet-overrides.md`). Match the project's existing `docs`/`Docs` capitalization.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Load foundational context for the agent-fleet repository
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Purpose
|
|
6
|
+
|
|
7
|
+
Orient yourself in **agent-fleet** — a collection of production-grade engineering skills
|
|
8
|
+
for AI coding agents, plus pi extensions, specialist agent personas, and lifecycle
|
|
9
|
+
commands that map to the software development lifecycle.
|
|
10
|
+
|
|
11
|
+
## Workflow
|
|
12
|
+
|
|
13
|
+
1. Run `git ls-files` to see the full project file tree
|
|
14
|
+
2. Read `README.md` and `CLAUDE.md` for the project overview and conventions
|
|
15
|
+
3. Read `docs/skill-anatomy.md` to learn the required skill format
|
|
16
|
+
4. Skim `skills/*/SKILL.md` — the core skills, grouped by lifecycle phase
|
|
17
|
+
(Define → Plan → Build → Verify → Review → Ship)
|
|
18
|
+
5. Read `agents/*.md` — the specialist review personas
|
|
19
|
+
6. Read `docs/pi-extensions.md`, `.pi/extensions/*/README.md` (always-on utilities), and `.pi/harnesses/*/README.md` (selectable session harnesses)
|
|
20
|
+
7. Summarize your understanding: purpose, structure, key files, and entry points
|
|
21
|
+
|
|
22
|
+
Do this directly — read the files yourself rather than delegating to subagents.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Conduct a five-axis code review — correctness, readability, architecture, security, performance
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:code-review-and-quality skill.
|
|
6
|
+
|
|
7
|
+
Review the current changes (staged or recent commits) across all five axes:
|
|
8
|
+
|
|
9
|
+
1. **Correctness** — Does it match the spec? Edge cases handled? Tests adequate?
|
|
10
|
+
2. **Readability** — Clear names? Straightforward logic? Well-organized?
|
|
11
|
+
3. **Architecture** — Follows existing patterns? Clean boundaries? Right abstraction level?
|
|
12
|
+
4. **Security** — Input validated? Secrets safe? Auth checked? (Use security-and-hardening skill)
|
|
13
|
+
5. **Performance** — No N+1 queries? No unbounded ops? (Use performance-optimization skill)
|
|
14
|
+
|
|
15
|
+
Categorize findings as Critical, Important, or Suggestion.
|
|
16
|
+
Output a structured review with specific file:line references and fix recommendations.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Install/status the Hermes liaison or turn its Telegram ask_user bridge on/off
|
|
3
|
+
argument-hint: "<install|status|on|off> [telegram-id] [--profile NAME] [--force] [--restart]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Run the deterministic Agent Fleet controller with the arguments from `$ARGUMENTS`. Supported forms are:
|
|
7
|
+
|
|
8
|
+
```text
|
|
9
|
+
set-hermes-telegram install [--profile NAME] [--force] [--restart]
|
|
10
|
+
set-hermes-telegram status [--profile NAME]
|
|
11
|
+
set-hermes-telegram on <telegram-id[:topic-id]> [--profile NAME]
|
|
12
|
+
set-hermes-telegram off <telegram-id[:topic-id]> [--profile NAME]
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
Use `node bin/cli.js set-hermes-telegram ...` when the checkout-local CLI exists; otherwise use `npx --no-install agent-fleet set-hermes-telegram ...`. Pass parsed values as separately quoted shell arguments. If neither CLI exists, report that Agent Fleet must be installed or updated. Do not reproduce installation or Herdr lifecycle with ad-hoc commands, do not bypass a `--force` refusal, and do not send a test Telegram message. Return the controller output verbatim.
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Inspect or safely install the fail-closed Hermes watchdog
|
|
3
|
+
argument-hint: "<status|install|update|uninstall> [--profile NAME] [--force] [--dry-run]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Ask for confirmation before install, update, uninstall, or force. Use only the deterministic Agent Fleet watchdog controller with the supplied separately quoted arguments. `status` is read-only; `--dry-run` writes nothing. Never start/restart a gateway or watcher, change tools, send a message, initiate a watch, or infer Gate O/origin routing. The packaged skill remains journal-only/dormant until independently reviewed live Gate O evidence exists.
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:guided-workspace-setup skill.
|
|
6
|
+
|
|
7
|
+
Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask for it. Detect the running coding agent and confirm it with the user.
|
|
8
|
+
|
|
9
|
+
Analyse the workspace. If prior install state is found (`.ai/agent-fleet-setup.md` or a populated agent directory), run the **Doctor preflight** first (Step 5) — scan for broken symlinks and stale persona references, present findings as a table, and apply the fixes the user picks before continuing.
|
|
10
|
+
|
|
11
|
+
The Skills group draws from **two roots**: fleet-native `skills/` and the vendored upstream import `vendor/agent-skills-upstream/skills/` (see `docs/UPSTREAM-SKILLS.md`). On a name collision the native copy wins — never offer the vendored duplicate as a separate row.
|
|
12
|
+
|
|
13
|
+
Then present the install menu per the skill's Step 1 interaction contract — drive every decision through `AskUserQuestion`, never a printed table awaiting a free-text reply. Open with the **Express question** (fresh workspace: `Recommended ★` / `Everything` / `Custom — group by group` / `Nothing`; existing: `Keep as-is` / `Apply updates` / `Keep + add recommended ★` / `Custom`) — any answer but `Custom` skips all group screens. On `Custom`, run the **7 groups** (4 shared: Skills, Agent personas, Commands/prompts, References & Hooks; 3 pi-only — a claude-code workspace sees just the 4 shared groups): each opens as a single-select quick screen (`Recommended ★ (n)` / `Everything (m)` / `Customise` / `Skip group`, or the installed-state variants with `Remove some…`), and multi-select drill-ins appear only behind `Customise`, chunked by sub-category (lifecycle phase for Skills, `rw`/`ro` for personas, …) at ≤ 4 options per question. Option titles carry `name ★ [st]` (`ok`/`upd`/`mod`/`cflt`/`gone`/`new`/`—`/`brk`); descriptions carry the purpose plus the state in plain words (`mod` → warn that refreshing overwrites local edits). There is **no pre-checking** — installed state shows as counts on quick screens and words in descriptions; leaving an installed item unselected in a drill-in keeps it as-is. `recommended` adds `★` items on top of what is installed — it never removes; cancel = keep-as-is/skip. `cflt` rows are resolved only by showing the three-way diff and asking per row — never by Express or `Apply updates`. Never offer `setup`, `doctor`, or `guided-workspace-setup` — those are installer-only and live in the source agent-fleet repo.
|
|
14
|
+
|
|
15
|
+
Removal happens **only** on an explicit `Remove some…` multi-select (empty selection = remove nothing), and it is scoped: the screen lists only items whose name is in the agent-fleet inventory **and** that are recorded in `## install-status` (or are symlinks resolving into the source repo). User-authored skills, custom commands, third-party plugins, and unrelated settings/env keys are left untouched and logged as "Skipped — not owned by agent-fleet".
|
|
16
|
+
|
|
17
|
+
**No cross-tool substitution.** Each row is offered only when the source file the chosen agent needs already exists — for `pi`, that means `.pi/prompts/<name>.md`, `.pi/extensions/<name>/`, etc. Never fall back to `.claude/commands/` (or another agent's tree) to satisfy a pi prompt request; items missing their per-agent source are filtered out of the menu entirely.
|
|
18
|
+
|
|
19
|
+
**Personas are generated for non-pi targets.** The personas group lists the full availability roster from `node <source-root>/bin/cli.js transform-persona --list --agent <agent>` (pi-only personas — `bowser`, `orchestrator` — appear only when the agent is `pi`). For `claude-code`/`opencode` the apply step installs personas via `transform-persona --agent <agent> --workspace <workspace> <name…>` — always a generated copy, even in symlink mode — and records the rows with `transformed: true`; status checks diff against the generated output, not the raw canonical source.
|
|
20
|
+
|
|
21
|
+
**pi harness companions.** When the agent is `pi`, installing/refreshing/removing any harness also refreshes its companions — the `justfile` launch recipes, the `team-up`/`coms-net` scripts, the peer/team YAML, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json`. `agent-hub` requires only `damage-control-continue` and `ask-user-remote`; auto-include both. Refresh the `justfile` from the current source (rewriting only the `agent-fleet:harnesses` managed region so user recipes survive) so retired-harness recipes are pruned and new ones added. Treat the retired `damage-control` hard-stop directory as `gone`: remove it only when recorded and unchanged against the recorded snapshot, or when it is a symlink into the source root (including a broken retirement link). Preserve every user-modified or unowned copy.
|
|
22
|
+
|
|
23
|
+
**No mid-apply overwrite prompts.** The `mod` description already warns that refreshing overwrites local edits. The user's selection is the consent; the Step 9 confirmation is the single gate. During apply, refresh selected items unconditionally — never pause to ask "should I overwrite this file?". Genuine errors (permission denied, missing source) still stop and report.
|
|
24
|
+
|
|
25
|
+
Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis (print each draft, then `Accept` / `Edit` / `Skip` per section), and record what was installed in `.ai/agent-fleet-setup.md`. Print the plan as compact action-grouped lines (Add / Refresh / Remove / Keep-count / Records / Method), then confirm with one question whose options are `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel` — write nothing until an Apply is chosen. Then perform the setup, re-scan for any new breakage, and report what changed.
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:shipping-and-launch skill.
|
|
6
|
+
|
|
7
|
+
`/ship` is a **fan-out orchestrator**. It runs three specialist personas in parallel against the current change, then merges their reports into a single go/no-go decision with a rollback plan. The personas operate independently — no shared state, no ordering — which is what makes parallel execution safe and useful here.
|
|
8
|
+
|
|
9
|
+
## Phase A — Parallel fan-out
|
|
10
|
+
|
|
11
|
+
Spawn three subagents concurrently using the Agent tool. **Issue all three Agent tool calls in a single assistant turn so they execute in parallel** — sequential calls defeat the purpose of this command.
|
|
12
|
+
|
|
13
|
+
In Claude Code, each call passes `subagent_type` matching the persona's `name` field:
|
|
14
|
+
|
|
15
|
+
1. **`code-reviewer`** — Run a five-axis review (correctness, readability, architecture, security, performance) on the staged changes or recent commits. Output the standard review template.
|
|
16
|
+
2. **`security-auditor`** — Run a vulnerability and threat-model pass. Check OWASP Top 10, secrets handling, auth/authz, dependency CVEs. Output the standard audit report.
|
|
17
|
+
3. **`test-engineer`** — Analyze test coverage for the change. Identify gaps in happy path, edge cases, error paths, and concurrency scenarios. Output the standard coverage analysis.
|
|
18
|
+
|
|
19
|
+
In other harnesses without an Agent tool, invoke each persona's system prompt sequentially and treat their outputs as if returned in parallel — the merge phase still works.
|
|
20
|
+
|
|
21
|
+
Constraints (from Claude Code's subagent model):
|
|
22
|
+
- Subagents cannot spawn other subagents — do not let one persona delegate to another.
|
|
23
|
+
- Each subagent gets its own context window and returns only its report to this main session.
|
|
24
|
+
- If you need teammates that talk to each other instead of just reporting back, use Claude Code Agent Teams and reference these personas as teammate types (see `references/orchestration-patterns.md`).
|
|
25
|
+
|
|
26
|
+
**Persona resolution.** If you've defined your own `code-reviewer`, `security-auditor`, or `test-engineer` in `.claude/agents/` or `~/.claude/agents/`, those take precedence over this plugin's versions — `/ship` picks up your customizations automatically. This is intentional: plugin subagents sit at the bottom of Claude Code's scope priority table, so user-level definitions win by design.
|
|
27
|
+
|
|
28
|
+
## Phase B — Merge in main context
|
|
29
|
+
|
|
30
|
+
Once all three reports are back, the main agent (not a sub-persona) synthesizes them:
|
|
31
|
+
|
|
32
|
+
1. **Code Quality** — Aggregate Critical/Important findings from `code-reviewer` and any failing tests, lint, or build output. Resolve duplicates between reviewers.
|
|
33
|
+
2. **Security** — Promote any Critical/High `security-auditor` findings to launch blockers. Cross-reference with `code-reviewer`'s security axis.
|
|
34
|
+
3. **Performance** — Pull from `code-reviewer`'s performance axis; cross-check Core Web Vitals if applicable.
|
|
35
|
+
4. **Accessibility** — Verify keyboard nav, screen reader support, contrast (not covered by the three personas — handle directly here, or invoke the accessibility checklist).
|
|
36
|
+
5. **Infrastructure** — Env vars, migrations, monitoring, feature flags. Verify directly.
|
|
37
|
+
6. **Documentation** — README, ADRs, changelog. Verify directly.
|
|
38
|
+
|
|
39
|
+
## Phase C — Decision and rollback
|
|
40
|
+
|
|
41
|
+
Produce a single output:
|
|
42
|
+
|
|
43
|
+
```markdown
|
|
44
|
+
## Ship Decision: GO | NO-GO
|
|
45
|
+
|
|
46
|
+
### Blockers (must fix before ship)
|
|
47
|
+
- [Source persona: Critical finding + file:line]
|
|
48
|
+
|
|
49
|
+
### Recommended fixes (should fix before ship)
|
|
50
|
+
- [Source persona: Important finding + file:line]
|
|
51
|
+
|
|
52
|
+
### Acknowledged risks (shipping anyway)
|
|
53
|
+
- [Risk + mitigation]
|
|
54
|
+
|
|
55
|
+
### Rollback plan
|
|
56
|
+
- Trigger conditions: [what signals would prompt rollback]
|
|
57
|
+
- Rollback procedure: [exact steps]
|
|
58
|
+
- Recovery time objective: [target]
|
|
59
|
+
|
|
60
|
+
### Specialist reports (full)
|
|
61
|
+
- [code-reviewer report]
|
|
62
|
+
- [security-auditor report]
|
|
63
|
+
- [test-engineer report]
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
## Rules
|
|
67
|
+
|
|
68
|
+
1. The three Phase A personas run in parallel — never sequentially.
|
|
69
|
+
2. Personas do not call each other. The main agent merges in Phase B.
|
|
70
|
+
3. The rollback plan is mandatory before any GO decision.
|
|
71
|
+
4. If any persona returns a Critical finding, the default verdict is NO-GO unless the user explicitly accepts the risk.
|
|
72
|
+
5. **Skip the fan-out only if all of the following are true:** the change touches 2 files or fewer, the diff is under 50 lines, and it does not touch auth, payments, data access, or config/env. Otherwise, default to fan-out. `/ship` is designed for production-bound changes — when the blast radius is non-trivial, run the parallel review even if the diff looks small.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Start spec-driven development — write a structured specification before writing code
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:spec-driven-development skill.
|
|
6
|
+
|
|
7
|
+
Begin by understanding what the user wants to build. Ask clarifying questions about:
|
|
8
|
+
1. The objective and target users
|
|
9
|
+
2. Core features and acceptance criteria
|
|
10
|
+
3. Tech stack preferences and constraints
|
|
11
|
+
4. Known boundaries (what to always do, ask first about, and never do)
|
|
12
|
+
|
|
13
|
+
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
|
|
14
|
+
|
|
15
|
+
Save the spec to the location the `spec-driven-development` skill defines (default `docs/prds/{area}/PRD{n}-{topic}.md`; overridable per project via `.ai/agent-fleet-overrides.md`). Confirm with the user before proceeding.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:test-driven-development skill.
|
|
6
|
+
|
|
7
|
+
For new features:
|
|
8
|
+
1. Write tests that describe the expected behavior (they should FAIL)
|
|
9
|
+
2. Implement the code to make them pass
|
|
10
|
+
3. Refactor while keeping tests green
|
|
11
|
+
|
|
12
|
+
For bug fixes (Prove-It pattern):
|
|
13
|
+
1. Write a test that reproduces the bug (must FAIL)
|
|
14
|
+
2. Confirm the test fails
|
|
15
|
+
3. Implement the fix
|
|
16
|
+
4. Confirm the test passes
|
|
17
|
+
5. Run the full test suite for regressions
|
|
18
|
+
|
|
19
|
+
For browser-related issues, also invoke agent-fleet:browser-testing-with-devtools to verify with Chrome DevTools MCP.
|