@chankov/agent-fleet 0.0.8 → 0.0.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/doctor-agent-fleet.md +12 -7
- package/.claude/commands/setup-agent-fleet.md +7 -15
- package/.opencode/commands/af-doctor-agent-fleet.md +12 -7
- package/.opencode/commands/af-setup-agent-fleet.md +8 -6
- package/.pi/agents/model-profiles.yaml +9 -2
- package/.pi/agents/peers.yaml +12 -16
- package/.pi/agents/teams.yaml +4 -2
- package/.pi/extensions/agent-fleet-update-check/README.md +2 -3
- package/.pi/extensions/btw/README.md +2 -2
- package/.pi/extensions/chrome-devtools-mcp/README.md +3 -6
- package/.pi/extensions/compact-and-continue/README.md +3 -3
- package/.pi/extensions/mcp-bridge/README.md +1 -1
- package/.pi/harnesses/agent-hub/README.md +159 -15
- package/.pi/harnesses/agent-hub/docs-lane.js +122 -0
- package/.pi/harnesses/agent-hub/external-blocker.js +85 -0
- package/.pi/harnesses/agent-hub/footer.ts +4 -2
- package/.pi/harnesses/agent-hub/index.ts +552 -50
- package/.pi/harnesses/agent-hub/package.json +1 -1
- package/.pi/harnesses/agent-hub/review-findings.js +102 -0
- package/.pi/harnesses/agent-hub/run-budget.js +302 -4
- package/.pi/harnesses/agent-hub/run-namespace.js +87 -0
- package/.pi/harnesses/agent-hub/version.ts +25 -1
- package/.pi/harnesses/coms/README.md +8 -1
- package/.pi/harnesses/coms/package.json +1 -1
- package/.pi/harnesses/coms/version.ts +25 -1
- package/.pi/harnesses/damage-control-continue/README.md +8 -1
- package/.pi/harnesses/damage-control-continue/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/version.ts +25 -1
- package/.pi/harnesses/lib/herdr-client.ts +10 -1
- package/.pi/harnesses/lib/spawned-peers.js +190 -0
- package/.pi/prompts/af-doctor-agent-fleet.md +13 -6
- package/.pi/prompts/af-setup-agent-fleet.md +7 -15
- package/.versions/0.0.10/.claude/commands/build.md +44 -0
- package/.versions/0.0.10/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.10/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.10/.claude/commands/doctor-agent-fleet.md +22 -0
- package/.versions/0.0.10/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.10/.claude/commands/plan.md +16 -0
- package/.versions/0.0.10/.claude/commands/prime.md +22 -0
- package/.versions/0.0.10/.claude/commands/review.md +16 -0
- package/.versions/0.0.10/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.10/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.versions/0.0.10/.claude/commands/setup-agent-fleet.md +17 -0
- package/.versions/0.0.10/.claude/commands/ship.md +72 -0
- package/.versions/0.0.10/.claude/commands/spec.md +15 -0
- package/.versions/0.0.10/.claude/commands/test.md +19 -0
- package/.versions/0.0.10/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.10/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.10/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.10/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.10/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.10/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.10/.opencode/commands/af-doctor-agent-fleet.md +22 -0
- package/.versions/0.0.10/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.10/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.10/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.10/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.10/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.10/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.10/.opencode/commands/af-setup-agent-fleet.md +17 -0
- package/.versions/0.0.10/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.10/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.10/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.10/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.10/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.10/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.10/.pi/agents/model-profiles.yaml +27 -0
- package/.versions/0.0.10/.pi/agents/peers.yaml +142 -0
- package/.versions/0.0.10/.pi/agents/teams.yaml +41 -0
- package/.versions/0.0.10/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/README.md +57 -0
- package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.10/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.10/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.10/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.10/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.10/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
- package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.10/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.10/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.10/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.10/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.10/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.10/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.10/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.10/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.10/.pi/extensions/package.json +9 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.10/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/README.md +1001 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/delegate.ts +435 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/docs-lane.js +122 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/external-blocker.js +85 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/footer.ts +31 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/helpers.ts +248 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/index.ts +9111 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/return-contract.js +293 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/review-findings.js +102 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/run-budget.js +479 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/run-namespace.js +87 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/spawn.ts +354 -0
- package/.versions/0.0.10/.pi/harnesses/agent-hub/version.ts +42 -0
- package/.versions/0.0.10/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.10/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.10/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.10/.pi/harnesses/coms/README.md +100 -0
- package/.versions/0.0.10/.pi/harnesses/coms/index.ts +1767 -0
- package/.versions/0.0.10/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.10/.pi/harnesses/coms/version.ts +42 -0
- package/.versions/0.0.10/.pi/harnesses/damage-control-continue/README.md +124 -0
- package/.versions/0.0.10/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.10/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.10/.pi/harnesses/damage-control-continue/version.ts +42 -0
- package/.versions/0.0.10/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.versions/0.0.10/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.10/.pi/harnesses/lib/herdr-client.ts +472 -0
- package/.versions/0.0.10/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/0.0.10/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.10/.pi/harnesses/lib/spawned-peers.js +190 -0
- package/.versions/0.0.10/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.10/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.10/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.10/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.10/.pi/prompts/af-doctor-agent-fleet.md +22 -0
- package/.versions/0.0.10/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.10/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.10/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.10/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.10/.pi/prompts/af-setup-agent-fleet.md +19 -0
- package/.versions/0.0.10/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.10/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.10/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.10/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.10/.version +1 -0
- package/.versions/0.0.10/agents/architect.md +24 -0
- package/.versions/0.0.10/agents/bowser.md +27 -0
- package/.versions/0.0.10/agents/builder.md +54 -0
- package/.versions/0.0.10/agents/code-reviewer.md +208 -0
- package/.versions/0.0.10/agents/deep-researcher.md +32 -0
- package/.versions/0.0.10/agents/documenter.md +18 -0
- package/.versions/0.0.10/agents/orchestrator.md +72 -0
- package/.versions/0.0.10/agents/plan-reviewer.md +83 -0
- package/.versions/0.0.10/agents/planner.md +70 -0
- package/.versions/0.0.10/agents/releaser.md +24 -0
- package/.versions/0.0.10/agents/researcher.md +28 -0
- package/.versions/0.0.10/agents/security-auditor.md +167 -0
- package/.versions/0.0.10/agents/test-engineer.md +153 -0
- package/.versions/0.0.10/agents/web-debugger.md +43 -0
- package/.versions/0.0.10/agents/web-performance-auditor.md +193 -0
- package/.versions/0.0.10/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.10/docs/ARCHITECTURE.md +303 -0
- package/.versions/0.0.10/docs/agent-fleet-setup.md +377 -0
- package/.versions/0.0.10/docs/claude-code-coms-bridge.md +109 -0
- package/.versions/0.0.10/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.10/docs/coms-hermes-bridge.md +189 -0
- package/.versions/0.0.10/docs/getting-started.md +254 -0
- package/.versions/0.0.10/docs/npm-install.md +514 -0
- package/.versions/0.0.10/docs/opencode-setup.md +281 -0
- package/.versions/0.0.10/docs/pi-extensions.md +363 -0
- package/.versions/0.0.10/docs/pi-setup.md +571 -0
- package/.versions/0.0.10/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.10/hermes/README.md +347 -0
- package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.10/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.10/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/0.0.10/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.10/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.10/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.10/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/0.0.10/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/0.0.10/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/0.0.10/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.10/hooks/coms-stop-hook.mjs +84 -0
- package/.versions/0.0.10/hooks/hooks.json +14 -0
- package/.versions/0.0.10/hooks/session-start.sh +74 -0
- package/.versions/0.0.10/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.10/install-manifest.json +3615 -0
- package/.versions/0.0.10/justfile +254 -0
- package/.versions/0.0.10/manifest-meta.json +472 -0
- package/.versions/0.0.10/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.10/references/definition-of-done.md +67 -0
- package/.versions/0.0.10/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.10/references/observability-checklist.md +91 -0
- package/.versions/0.0.10/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.10/references/performance-checklist.md +153 -0
- package/.versions/0.0.10/references/prompting-patterns.md +380 -0
- package/.versions/0.0.10/references/security-checklist.md +179 -0
- package/.versions/0.0.10/references/testing-patterns.md +236 -0
- package/.versions/0.0.10/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.10/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.10/scripts/coms-claude-bridge.ts +401 -0
- package/.versions/0.0.10/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.10/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.10/scripts/fleet.ts +168 -0
- package/.versions/0.0.10/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.10/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/0.0.10/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/0.0.10/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/0.0.10/scripts/lib/claude-bridge-core.ts +165 -0
- package/.versions/0.0.10/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.10/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.10/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/0.0.10/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.10/scripts/lib/fleet-command.ts +111 -0
- package/.versions/0.0.10/scripts/lib/herdr-layout.ts +281 -0
- package/.versions/0.0.10/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.10/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/0.0.10/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.10/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.10/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.10/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.10/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.10/scripts/lib/monitor-env.ts +120 -0
- package/.versions/0.0.10/scripts/lib/peer-launch.ts +314 -0
- package/.versions/0.0.10/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.10/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.10/scripts/lib/team-project.ts +193 -0
- package/.versions/0.0.10/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.10/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.10/scripts/peer-launch.ts +259 -0
- package/.versions/0.0.10/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.10/scripts/team-up.ts +360 -0
- package/.versions/0.0.10/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.10/skills/browser-testing-with-devtools/SKILL.md +351 -0
- package/.versions/0.0.10/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.10/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.10/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.10/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.10/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.10/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.10/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.10/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.10/skills/guided-workspace-setup/SKILL.md +226 -0
- package/.versions/0.0.10/skills/guided-workspace-setup/companion-manifest.json +38 -0
- package/.versions/0.0.10/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.10/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.10/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.10/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.10/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.10/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.10/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.10/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.10/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.10/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.10/skills/planning-and-task-breakdown/SKILL.md +254 -0
- package/.versions/0.0.10/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.10/skills/spec-driven-development/SKILL.md +257 -0
- package/.versions/0.0.10/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.10/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.10/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/.versions/0.0.9/.claude/commands/build.md +44 -0
- package/.versions/0.0.9/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.9/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.9/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.9/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.9/.claude/commands/plan.md +16 -0
- package/.versions/0.0.9/.claude/commands/prime.md +22 -0
- package/.versions/0.0.9/.claude/commands/review.md +16 -0
- package/.versions/0.0.9/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.9/.claude/commands/set-hermes-watchdog.md +6 -0
- package/.versions/0.0.9/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.9/.claude/commands/ship.md +72 -0
- package/.versions/0.0.9/.claude/commands/spec.md +15 -0
- package/.versions/0.0.9/.claude/commands/test.md +19 -0
- package/.versions/0.0.9/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.9/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.9/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.9/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.9/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.9/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.9/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.9/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.9/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.9/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.9/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.9/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.9/.opencode/commands/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.9/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.9/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.9/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.9/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.9/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.9/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.9/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.9/.pi/agents/model-profiles.yaml +27 -0
- package/.versions/0.0.9/.pi/agents/peers.yaml +142 -0
- package/.versions/0.0.9/.pi/agents/teams.yaml +41 -0
- package/.versions/0.0.9/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.9/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.9/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.9/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.9/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.9/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.9/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.9/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.9/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.9/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.9/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.9/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.9/.pi/extensions/package.json +9 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.9/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/README.md +872 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/context-window.js +106 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/delegate.ts +435 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/footer.ts +31 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/helpers.ts +248 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/index.ts +8702 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/return-contract.js +293 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/return-extract.js +75 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/run-budget.js +181 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/spawn.ts +354 -0
- package/.versions/0.0.9/.pi/harnesses/agent-hub/version.ts +42 -0
- package/.versions/0.0.9/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.9/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.9/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.9/.pi/harnesses/coms/README.md +100 -0
- package/.versions/0.0.9/.pi/harnesses/coms/index.ts +1767 -0
- package/.versions/0.0.9/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.9/.pi/harnesses/coms/version.ts +42 -0
- package/.versions/0.0.9/.pi/harnesses/damage-control-continue/README.md +124 -0
- package/.versions/0.0.9/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.9/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.9/.pi/harnesses/damage-control-continue/version.ts +42 -0
- package/.versions/0.0.9/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
- package/.versions/0.0.9/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.9/.pi/harnesses/lib/herdr-client.ts +472 -0
- package/.versions/0.0.9/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.9/.pi/harnesses/lib/spawned-peers.js +190 -0
- package/.versions/0.0.9/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.9/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.9/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.9/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.9/.pi/prompts/af-doctor-agent-fleet.md +15 -0
- package/.versions/0.0.9/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.9/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.9/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.9/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/0.0.9/.pi/prompts/af-setup-agent-fleet.md +27 -0
- package/.versions/0.0.9/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.9/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.9/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.9/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.9/.version +1 -0
- package/.versions/0.0.9/agents/architect.md +24 -0
- package/.versions/0.0.9/agents/bowser.md +27 -0
- package/.versions/0.0.9/agents/builder.md +54 -0
- package/.versions/0.0.9/agents/code-reviewer.md +204 -0
- package/.versions/0.0.9/agents/deep-researcher.md +32 -0
- package/.versions/0.0.9/agents/documenter.md +18 -0
- package/.versions/0.0.9/agents/orchestrator.md +66 -0
- package/.versions/0.0.9/agents/plan-reviewer.md +62 -0
- package/.versions/0.0.9/agents/planner.md +70 -0
- package/.versions/0.0.9/agents/releaser.md +24 -0
- package/.versions/0.0.9/agents/researcher.md +28 -0
- package/.versions/0.0.9/agents/security-auditor.md +167 -0
- package/.versions/0.0.9/agents/test-engineer.md +153 -0
- package/.versions/0.0.9/agents/web-debugger.md +43 -0
- package/.versions/0.0.9/agents/web-performance-auditor.md +193 -0
- package/.versions/0.0.9/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.9/docs/ARCHITECTURE.md +262 -0
- package/.versions/0.0.9/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.9/docs/claude-code-coms-bridge.md +109 -0
- package/.versions/0.0.9/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.9/docs/coms-hermes-bridge.md +189 -0
- package/.versions/0.0.9/docs/getting-started.md +231 -0
- package/.versions/0.0.9/docs/npm-install.md +337 -0
- package/.versions/0.0.9/docs/opencode-setup.md +249 -0
- package/.versions/0.0.9/docs/pi-extensions.md +356 -0
- package/.versions/0.0.9/docs/pi-setup.md +476 -0
- package/.versions/0.0.9/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.9/hermes/README.md +347 -0
- package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.9/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/0.0.9/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.9/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.9/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/0.0.9/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/0.0.9/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.9/hooks/coms-stop-hook.mjs +84 -0
- package/.versions/0.0.9/hooks/hooks.json +14 -0
- package/.versions/0.0.9/hooks/session-start.sh +74 -0
- package/.versions/0.0.9/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.9/justfile +254 -0
- package/.versions/0.0.9/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.9/references/definition-of-done.md +67 -0
- package/.versions/0.0.9/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.9/references/observability-checklist.md +91 -0
- package/.versions/0.0.9/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.9/references/performance-checklist.md +153 -0
- package/.versions/0.0.9/references/prompting-patterns.md +380 -0
- package/.versions/0.0.9/references/security-checklist.md +179 -0
- package/.versions/0.0.9/references/testing-patterns.md +236 -0
- package/.versions/0.0.9/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.9/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.9/scripts/coms-claude-bridge.ts +401 -0
- package/.versions/0.0.9/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.9/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.9/scripts/fleet.ts +168 -0
- package/.versions/0.0.9/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.9/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/0.0.9/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/0.0.9/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/0.0.9/scripts/lib/claude-bridge-core.ts +165 -0
- package/.versions/0.0.9/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.9/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.9/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/0.0.9/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.9/scripts/lib/fleet-command.ts +111 -0
- package/.versions/0.0.9/scripts/lib/herdr-layout.ts +281 -0
- package/.versions/0.0.9/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.9/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/0.0.9/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.9/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.9/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.9/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.9/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.9/scripts/lib/monitor-env.ts +120 -0
- package/.versions/0.0.9/scripts/lib/peer-launch.ts +314 -0
- package/.versions/0.0.9/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.9/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.9/scripts/lib/team-project.ts +193 -0
- package/.versions/0.0.9/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.9/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.9/scripts/peer-launch.ts +259 -0
- package/.versions/0.0.9/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.9/scripts/team-up.ts +360 -0
- package/.versions/0.0.9/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.9/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.9/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.9/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.9/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.9/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.9/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.9/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.9/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.9/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.9/skills/guided-workspace-setup/SKILL.md +544 -0
- package/.versions/0.0.9/skills/guided-workspace-setup/companion-manifest.json +38 -0
- package/.versions/0.0.9/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.9/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.9/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.9/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.9/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.9/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.9/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.9/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.9/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.9/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.9/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.9/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.9/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.9/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.9/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.9/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +141 -0
- package/README.md +22 -5
- package/agents/architect.md +1 -0
- package/agents/bowser.md +1 -0
- package/agents/builder.md +1 -0
- package/agents/code-reviewer.md +8 -5
- package/agents/deep-researcher.md +2 -1
- package/agents/orchestrator.md +8 -1
- package/agents/plan-reviewer.md +25 -2
- package/agents/planner.md +3 -2
- package/agents/security-auditor.md +1 -0
- package/agents/test-engineer.md +3 -1
- package/agents/web-debugger.md +1 -0
- package/agents/web-performance-auditor.md +1 -0
- package/bin/build-manifest.js +68 -0
- package/bin/cli.js +679 -49
- package/bin/lib/apply.js +641 -0
- package/bin/lib/manifest.js +731 -0
- package/bin/lib/merge-forms.js +106 -0
- package/bin/lib/plan.js +569 -0
- package/bin/lib/state.js +213 -0
- package/bin/lib/verify.js +576 -0
- package/bin/snapshot-version.js +5 -0
- package/docs/ARCHITECTURE.md +53 -12
- package/docs/agent-fleet-setup.md +59 -48
- package/docs/getting-started.md +29 -6
- package/docs/npm-install.md +208 -31
- package/docs/opencode-setup.md +32 -0
- package/docs/pi-extensions.md +83 -13
- package/docs/pi-setup.md +164 -69
- package/install-manifest.json +3615 -0
- package/justfile +10 -1
- package/manifest-meta.json +472 -0
- package/package.json +8 -3
- package/scripts/fleet.ts +22 -3
- package/scripts/lib/fleet-command.ts +5 -3
- package/scripts/lib/herdr-layout.ts +18 -0
- package/scripts/lib/peer-launch.ts +314 -0
- package/scripts/lib/team-project.ts +3 -1
- package/scripts/peer-launch.ts +259 -0
- package/skills/browser-testing-with-devtools/SKILL.md +3 -4
- package/skills/guided-workspace-setup/SKILL.md +172 -490
- package/skills/guided-workspace-setup/companion-manifest.json +2 -0
- package/skills/planning-and-task-breakdown/SKILL.md +18 -0
- package/skills/spec-driven-development/SKILL.md +12 -0
- package/.pi/harnesses/agent-hub/spawned-peers.js +0 -74
|
@@ -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 |
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,146 @@
|
|
|
1
1
|
# Agent Fleet changelog
|
|
2
2
|
|
|
3
|
+
## 0.0.10
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- c7a821c: Make `install` and `upgrade` real: the apply engine (Phase 4 of `plans/deterministic-installer.md`, completing Phase 5).
|
|
8
|
+
|
|
9
|
+
A brand-new repository can now be set up with one command and no coding agent in the loop:
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
npx @chankov/agent-fleet@latest install --agent pi --profile recommended --yes
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
- **`agent-fleet install`** applies a plan: copies, symlinks (`--method symlink`), generates personas through the tested transformer, rewrites the `justfile` managed region, and merges only agent-fleet's own keys into `.claude/settings.json`. Run without a selection in a terminal it asks which profile; piped, it requires the flags rather than guessing. `--yes` skips the single confirmation; `--allow-exec` admits the items that run a command, which are ordered after all file work so they see the finished tree.
|
|
16
|
+
- **`agent-fleet upgrade`** applies the three-way merge: clean upgrades land, local edits are preserved, and a file changed both locally and upstream is written beside yours as `<file>.new` while your copy is left untouched (exit `3`).
|
|
17
|
+
- **State and record.** Every pass writes `.ai/agent-fleet-state.json` — per-file hashes, ownership, method, version — and renders `.ai/agent-fleet-setup.md` from it, so the human record can no longer disagree with the machine one. The state file is written even when a pass fails partway, so a workspace never holds files it has no record of.
|
|
18
|
+
- **Safety is enforced, not documented.** Nothing is written outside the workspace, nothing is deleted that the state file does not record as ours, and nothing you have edited is deleted at all — a removal reports what it kept and why.
|
|
19
|
+
|
|
20
|
+
`verify` now compares the two shared-file forms for real (a managed region by its sentinel-bounded block, a JSON merge by its declared key paths) instead of reporting them as unchecked, so your own `justfile` recipes and settings keys never read as drift. Installing twice is a no-op, asserted in tests.
|
|
21
|
+
|
|
22
|
+
Unchanged: `init`, `doctor`, `update`, `cleanup-installer`, and the guided setup skill.
|
|
23
|
+
|
|
24
|
+
- c7a821c: Add the deterministic installer's planner and the upgrade three-way merge (Phases 3 and 5 of `plans/deterministic-installer.md`).
|
|
25
|
+
|
|
26
|
+
- **`agent-fleet install --profile <name> --dry-run`** — resolves a selection (profiles ∪ explicit item ids, closed over `requires` and `companions`) against the workspace and prints the exact action list: what would be created, refreshed, repaired, kept, or skipped, in an order where every requirement precedes the item that needs it. A selection never removes anything; a narrower profile keeps what is already installed.
|
|
27
|
+
- **`agent-fleet upgrade --dry-run`** — plans an upgrade of what the workspace already has, using the `.versions/<recorded>` snapshot as the merge base. An untouched file that moved upstream is refreshed; a locally modified file whose source did not move is preserved; a file changed in both places is reported as a conflict and never resolved by guessing. `--accept-theirs` / `--accept-ours` resolve conflicts non-interactively, and an artifact retired upstream is proposed for removal by name.
|
|
28
|
+
- **Consent classes are enforced at plan time.** `exec` items are skipped unless `--allow-exec` is passed, and `external` / `operator` items are reported as steps the engine will never perform.
|
|
29
|
+
- Exit codes: `0` clean, `1` could not plan, `3` conflicts needing a decision.
|
|
30
|
+
|
|
31
|
+
`plan()` reads the filesystem and writes nothing; `verify` and both new verbs now share one workspace evaluation (`evaluateWorkspace`), so they cannot disagree about a file's state. Golden plans for a fresh `pi` / `claude-code` / `opencode` workspace are committed, so a change to the recommended set shows up as a reviewed diff.
|
|
32
|
+
|
|
33
|
+
Applying a plan lands with the apply engine in Phase 4; until then both verbs require `--dry-run` and refuse to run without it. `init`, `doctor`, `update`, `verify`, and the guided setup skill are unchanged.
|
|
34
|
+
|
|
35
|
+
- c7a821c: `doctor` repairs through the install engine, and `uninstall` lands (Phase 6 of `plans/deterministic-installer.md`).
|
|
36
|
+
|
|
37
|
+
- **`agent-fleet doctor [--fix]`** now has two halves in one report. Recorded items that are missing, dangling, or linked outside the source root are rebuilt through the _same_ `apply()` path `install` writes with — a repaired file is byte-identical to a freshly installed one. The old scan stays for what the install record cannot own: broken links in a pre-engine workspace, and stale persona names in `.pi/agents/*.yaml`. Overrides problems and malformed `peers.yaml` entries remain advisory. Exit `2` when anything repairable is left, `--json` for the machine report, `--dry-run` to look without being asked anything.
|
|
38
|
+
- **`agent-fleet uninstall --items <id,…> | --all`** removes what the state file records, and only that. A recorded file whose bytes no longer match what we wrote is kept and listed as skipped. A companion travels with its parent unless another installed item still needs it, and an item another installed item pins is refused by name — so removing one pi extension cannot delete the `package.json` five others run from, and removing `damage-control-continue` while `agent-hub` is installed is refused rather than silently leaving the hub without its safety harness. Removing the last pi harness strips the `agent-fleet:harnesses` region from the `justfile` and leaves the rest of the file alone.
|
|
39
|
+
- **Hermes and Codex are real profiles.** `install --profile hermes-plugins --dry-run` (and `codex-bridge`) prints the exact command list for each artifact and touches nothing. Their targets are a Hermes profile and a user systemd unit — outside the workspace, the one place the engine writes — so they stay `operator`-consent by design. Every operator item now declares its steps in the manifest, and the manifest build fails if one does not.
|
|
40
|
+
|
|
41
|
+
Two fixes to the write path, both cases where a filesystem call silently did nothing:
|
|
42
|
+
|
|
43
|
+
- A **dangling symlink was never replaced** — `rmSync(path, { force: true })` stats through the link, saw ENOENT, and returned as if the path were already gone, so the replacing `symlinkSync` failed `EEXIST`. Repairing a broken link is exactly the case that hit this.
|
|
44
|
+
- **Emptied directories were left behind** on removal — the non-recursive `rmSync` throws `EISDIR` on any directory, so the prune walk aborted on its first step.
|
|
45
|
+
|
|
46
|
+
- c7a821c: `guided-workspace-setup` becomes a front-end over the installer instead of the installer (Phase 7 of `plans/deterministic-installer.md`).
|
|
47
|
+
|
|
48
|
+
The skill is 544 lines shorter than it was — 220 down from 544 — because everything it used to describe now runs as code. Gone: the per-agent path table, the item-state table, the merge rules, the removal-ownership rules, the harness companion closure, and the `af-` migration procedure. What remains is what a program cannot do: ask which artifacts a project wants, draft `.ai/agent-fleet-overrides.md` from a scan of the workspace, and run the `pi-voice-stt` provider Q&A.
|
|
49
|
+
|
|
50
|
+
- **One command builds the menu.** `verify --json` now carries `groups` (agent-filtered), `profiles`, and per-item `subcategory`, `title`, `summary`, `recommended`, `owned`, and `state` — so the selection screen comes from a single call, and no front-end recomputes an item's state by eye.
|
|
51
|
+
- **The five setup/doctor slash commands were rewritten the same way.** They had each accumulated their own copy of the same rules.
|
|
52
|
+
|
|
53
|
+
Three rules that had only ever existed as prose are now encoded, and tested as behaviour:
|
|
54
|
+
|
|
55
|
+
- **Fleet Core** — the set `just fleet` loads into every session — is `requires` plus `pinnedBy` in the manifest. Installing any pi harness pulls the whole closure; uninstalling a member while a harness is installed is refused. A test parses `fleet_core_extensions` out of the `justfile` and fails if the manifest disagrees.
|
|
56
|
+
- **The `af-` prompt migration.** A workspace set up before the namespace still has `.pi/prompts/spec.md`, and pi keeps offering `/spec` from it. Commands now declare the unprefixed path they replaced; installing retires it under the ownership rule (a same-named prompt you wrote yourself is kept), and `verify` reports a surviving one as an advisory finding.
|
|
57
|
+
- **Stripping the `justfile` region.** Removing the last pi harness used to leave the managed block behind, so `just --list` kept advertising recipes for deleted harness directories.
|
|
58
|
+
|
|
59
|
+
Docs updated: `docs/npm-install.md` (the `doctor`, `uninstall`, and consent-class sections; CI usage is now the no-LLM install), and `docs/agent-fleet-setup.md` (the state file and the three-way merge, replacing the prose status table).
|
|
60
|
+
|
|
61
|
+
- c7a821c: Add the deterministic installer's catalogue and read-only inspection pass (Phases 0–2 of `plans/deterministic-installer.md`).
|
|
62
|
+
|
|
63
|
+
- **`install-manifest.json`** — a generated catalogue of every installable artifact: source candidates, per-agent target and strategy, group, recommendation, consent class, and companion wiring. Built from the repository tree by `node bin/build-manifest.js`; `--check` fails when the committed copy is stale, so an artifact landing without a menu row is a test failure rather than a silent omission. Only judgement (grouping, recommendations, consent, companions) is hand-edited, in `manifest-meta.json`.
|
|
64
|
+
- **`agent-fleet verify`** — a read-only report of a workspace against the manifest: what the new `.ai/agent-fleet-state.json` records, what is on disk, and what the current package ships, including the three-way comparison against the `.versions/<recorded>` snapshot. Writes nothing. Supports `--agent`, `--workspace`, `--json`, `--no-doctor`, and exits `0`/`1`/`2`. The existing doctor findings are folded into the same report; findings are split into `problem` and `advisory`, and only problems affect the exit code.
|
|
65
|
+
|
|
66
|
+
No existing behaviour changes: `init`, `doctor`, `update`, and the guided setup skill are untouched.
|
|
67
|
+
|
|
68
|
+
- 63cb0eb: Rewrite the setup docs around the deterministic CLI installer.
|
|
69
|
+
|
|
70
|
+
`README.md`, `docs/getting-started.md`, `docs/pi-setup.md`, `docs/opencode-setup.md`, and `docs/pi-extensions.md` still described the pre-engine world: `ln -s` chains into `.agents/skills/` and `~/.config/opencode/`, "symlink mode in `/setup-agent-fleet`", and `git pull` as the update mechanism. All of that is replaced by the verbs that actually do the work.
|
|
71
|
+
|
|
72
|
+
- **The no-agent path is documented first.** `install --agent <a> --profile <p> --yes` needs no coding agent and no model; `init` is presented as the conversational front-end over the same engine, not as the only way in. Profiles, `--items`, `--dry-run`, `--json`, and the exit codes are named where a reader would look for them.
|
|
73
|
+
- **Every symlink recipe is gone from the install paths.** Artifacts install as copies; freshness comes from `agent-fleet upgrade` and its three-way merge, not from editing a link target. `--method symlink` appears only where it is still true — inside an agent-fleet checkout.
|
|
74
|
+
- **pi setup is restructured into three paths** (CLI installer, pi package, clone for contributors) with a table of where each artifact kind lands. The clone path now installs _from_ the checkout (`node /path/to/agent-fleet/bin/cli.js install --workspace <project>`) instead of linking into it.
|
|
75
|
+
- **`--allow-exec` is explained where it bites**: the `npm ci` steps for `.pi/extensions/` and `.pi/harnesses/` are a separate consent class, printed and skipped without the flag.
|
|
76
|
+
- **OpenCode gains a project-scoped install section**; the manual `~/.config/opencode/` symlink recipe is kept but labelled as the advanced machine-wide alternative the CLI deliberately does not cover.
|
|
77
|
+
- Extension READMEs (`btw`, `compact-and-continue`, `agent-fleet-update-check`, `chrome-devtools-mcp`, `mcp-bridge`) and the `browser-testing-with-devtools` skill now give the `--items` command instead of an `ln -s`. `chrome-devtools-mcp` documents that `pi-extension:mcp-bridge` must be selected alongside it — it is not pulled in as a companion.
|
|
78
|
+
|
|
79
|
+
Every command added to the docs was verified against the CLI by dry-run.
|
|
80
|
+
|
|
81
|
+
- 8c64b6b: Make the agent-hub's cost guardrails bind on a TASK rather than on a message, and stop the four escalation paths that turned a one-line change into a two-day run.
|
|
82
|
+
|
|
83
|
+
The failure this comes from: a request to add two missing Key Vault permissions produced a 493-line PRD, a 1216-line plan with hash-pinned manifests and a fixture suite, and 47 hours in one workspace — while the same change, made in a narrow workspace with two agents, took 13 minutes. Every existing guardrail was in place and none of them bound, because all of them were scoped to a user message.
|
|
84
|
+
|
|
85
|
+
- **Task-scoped budget** (`run-budget.js`) — a second envelope, `3×` the turn envelope, whose counters are **not** reset by a user message. Exhausting it is a hard stop; only `/af-new-task [label]` (or `set_task_tier` with `new_task: true`) opens a new window. Turn budgets refilled on every steering message, so a steered run could never hit one. The task clock charges **active** time only (turns that ran, minus `ask_user` waits): billing human idle would false-stop a normal steered session, and a false stop teaches people to reset the window reflexively. The auto-research pipe stays exempt from the turn budget but **is** charged against the task envelope — at 2 rounds × 4 questions per dispatch it would otherwise smuggle up to 144 research runs past the outer bound.
|
|
86
|
+
- **Ratcheted, task-scoped tier** — the task tier now survives the user's next message and moves one way cheaply: lowering is free, raising requires a `reason` naming what the ask turned out to contain. Previously the tier reset to null on every message and the next dispatch re-assumed `feature`, so a two-word correction bought six fresh dispatches. A skipped triage now assumes **`small`**, not `feature`: the tier latches for the whole task, and a never-declared tier is precisely the case where proportionality was not being considered — assuming `feature` there granted the whole apparatus for forgetting a tool call. An assumed tier is not a ratchet baseline, so the dispatcher's own first `set_task_tier` still needs no reason.
|
|
87
|
+
- **Tier persona gate** — at `trivial`/`small`, `dispatch_agent`/`spawn_research` refuse `planner`, `plan-reviewer`, `architect`, `security-auditor` and `deep-researcher`. Each opens a document/finding loop whose output must then be executed and re-reviewed. The refusal costs no budget slot and names the escape hatch (raise the tier, with a reason).
|
|
88
|
+
- **Review round cap** — review dispatches per task are capped by tier (trivial/small 1, feature 2, project uncapped); the next one is refused without spending a budget slot. This is where the review ratchet is cut, because closing it needs a second round.
|
|
89
|
+
- **Review finding budget** — review personas are dispatched with a blocking-finding cap tied to the tier (trivial 1, small 2, feature 5, project uncapped), plus the rule that a blocking finding may only enforce an invariant the task, plan, or project rules already state. The hub **counts** the returned findings (`review-findings.js`) and appends a visible over-budget notice, but deliberately never reclassifies one: no rule the hub can evaluate separates "invents a manifest nobody asked for" from "this logs a connection string", and silently demoting the second by position would move a real security finding into the section nobody acts on.
|
|
90
|
+
- **Docs lane** (`docs-lane.js`) — a dispatch whose whole `scope` is documentation refuses review personas (overridable per dispatch with `review_reason`) and tells the dispatcher not to open a review gate. An absent scope is never the lighter lane.
|
|
91
|
+
- **External-blocker stop** (`external-blocker.js`) — specialists emit `EXTERNAL_BLOCKED: <what is missing, who owns it>` when they need something outside the fleet's reach; the hub refuses the next dispatch with an owner-escalation packet until the human is addressed. This replaces the observed alternative: substituting internal work — scripts, manifests, fixtures, diagnostic packets — for a missing external fact for hours, with the assertion still ending UNPROVEN.
|
|
92
|
+
- **Immutable per-run artifact namespaces** (`run-namespace.js`) — session start now archives the previous session's artifacts into `.pi/agent-sessions/runs/<runId>/` with a read-only `meta.json` and an appended `runs/index.json`, instead of deleting them. Retention is the new `run-history-keep:` overrides key (default 10, `off` keeps everything). The old wipe plus per-session `builder-runN.md` naming is what made a post-mortem record eleven specialist returns and two reviews as NOT RECOVERABLE.
|
|
93
|
+
|
|
94
|
+
Supporting changes: `orchestrator`, `plan-reviewer` and `code-reviewer` personas carry the matching proportionality rules, and `spec-driven-development` and `planning-and-task-breakdown` gain a proportionality gate so the personas do not fight the code gates.
|
|
95
|
+
|
|
96
|
+
- c7a821c: Symlink installs are retired for ordinary workspaces — artifacts install as copies.
|
|
97
|
+
|
|
98
|
+
`--method symlink` is now accepted only when the target workspace **is** an agent-fleet checkout (its `package.json` names `@chankov/agent-fleet`) — the one place where editing an installed artifact is _meant_ to edit the source. Everywhere else a symlink install is a trap: the link target can never move again, an npx cache clean breaks every link at once, a `git pull` in the source silently rewrites artifacts the workspace never agreed to change, and Windows needs Developer Mode. A copy plus `agent-fleet upgrade` gives the same freshness with a real three-way merge behind it.
|
|
99
|
+
|
|
100
|
+
- `--method` is gone from the help text of `init`, `install`, `upgrade`, and `update`. An explicit `--method symlink` outside a checkout is **refused** with an explanation, not silently downgraded — a flag you typed deserves an answer.
|
|
101
|
+
- **Existing symlink installs migrate automatically.** `verify` reports the workspace with a new advisory `symlink-retired` finding, and the next `install` or `upgrade` re-materialises every linked item as a real file and flips the recorded method to `copy`. Local edits are still preserved by `upgrade`'s merge; nothing is lost in the conversion.
|
|
102
|
+
- `guided-workspace-setup` and the three setup slash commands no longer ask copy-vs-symlink at all. There is no question left to ask.
|
|
103
|
+
|
|
104
|
+
Inside an agent-fleet checkout nothing changes: `--method symlink` still works, and that is the case the mode now exists for.
|
|
105
|
+
|
|
106
|
+
## 0.0.9
|
|
107
|
+
|
|
108
|
+
### Patch Changes
|
|
109
|
+
|
|
110
|
+
- 5a3fa84: `just fleet peer <name>` now launches the peer in a Herdr pane of its own, and can launch any kind of peer — including Claude Code.
|
|
111
|
+
|
|
112
|
+
**Behavior change:** `just fleet peer <name>` used to turn the _calling terminal_ into a pi peer. It now opens a pane instead. Pass `--here` for the old behavior; the command it runs there is byte-identical to before.
|
|
113
|
+
|
|
114
|
+
Launching a Claude Code peer previously meant declaring it in `.pi/agents/peers.yaml` and running `just fleet team <preset>`, which builds a whole workspace. There was no way to say "give me one more agent, next to what I already have".
|
|
115
|
+
|
|
116
|
+
- The **name decides the shape**: a name declared in `peers.yaml` keeps its `runner`/`model`/`extensions`/`env_file`; a name matching `agents/<name>.md` becomes that guarded persona peer; anything else is the identity-only Fleet Core peer this command always launched. `--runner claude-code` needs no manifest entry at all. Note the second rule also changes meaning for existing invocations — `just fleet peer architect` is now the architect persona peer, because `agents/architect.md` exists. `--no-persona` forces the plain shape back.
|
|
117
|
+
- **Placement**: inside a Herdr pane it splits _that_ pane (`--direction right|down`); outside Herdr it creates a single-pane workspace labelled `<worktree-tag>-peer-<name>`, refusing to clobber an existing one; `--here` runs it in the calling terminal.
|
|
118
|
+
- New flags: `--runner pi|claude-code`, `--persona`, `--no-persona`, `--model`, `--extensions`, `--direction`, `--here`, `--dry-run`. `--browser` now also works on a persona peer, where it adds `chrome-devtools-mcp`. Raw pi arguments move behind a `--` separator (`just fleet peer architect --here -- --session …`).
|
|
119
|
+
- **Nothing is silently dropped**: a flag that cannot apply to the resolved peer shape is an error, not a no-op — `--all-extensions` on a persona peer, `--persona` on a Claude Code peer, a mistyped flag, or a pi flag that forgot its `--`.
|
|
120
|
+
- A pane launch waits (bounded) for the peer to register in the coms pool and exits non-zero with the pane's last output when it never does — the same "failed, not slow" policy `herdr_spawn_peer` uses.
|
|
121
|
+
- `--dry-run` prints the resolved plan and placement without touching Herdr, and never reads `env_file` values.
|
|
122
|
+
|
|
123
|
+
Pure logic lives in `scripts/lib/peer-launch.ts` under `node --test`; the Herdr wiring is `scripts/peer-launch.ts`, reusing the existing command builder (`peerCommand`) and pane-launch helper so hub spawns, team spawns, and CLI launches stay one behavior.
|
|
124
|
+
|
|
125
|
+
`spawned-peers.js` (pane launch + readiness policy) moves from `.pi/harnesses/agent-hub/` to the shared `.pi/harnesses/lib/`, because the fleet scripts are installed into target projects that may not have selected the `agent-hub` harness. Both new scripts are added to `companion-manifest.json` so guided setup installs and refreshes them with the rest of the runtime closure.
|
|
126
|
+
|
|
127
|
+
- f62cfe0: Fix `herdr_spawn_peer`: it opened panes without ever launching the peer.
|
|
128
|
+
|
|
129
|
+
herdr's `pane.split` takes no `command` — a split always opens a plain shell — and the server silently ignores unknown params. agent-hub passed `command: argv` to it, so every hub-spawned "peer" was an empty shell pane with the right label, the tool reported success, and the readiness wait then timed out on a peer that had never started. `just fleet team` was unaffected because it launches through `layout.apply`, whose pane nodes do carry an argv.
|
|
130
|
+
|
|
131
|
+
- The spawn now splits, waits for the new pane's shell prompt, and types the command line (text and Enter sent separately — bash bracketed paste swallows a newline inside sent text).
|
|
132
|
+
- Spawned peers join **this session's coms project pool** instead of always `default`, which had put them in a pool the hub cannot see.
|
|
133
|
+
- A name declared in `.pi/agents/peers.yaml` keeps its declared `runner:`, `extensions:`, and `env_file:`, so spawning `code-reviewer` produces the peer the fleet defines rather than a plain pi persona.
|
|
134
|
+
- Hub spawns honor the stale-OAuth spawn stagger that team launches already used, so back-to-back spawns cannot lose the credential lock race.
|
|
135
|
+
- `peer_ready: false` now returns the pane's last output and states that the peer failed to start; the orchestrator persona and hub guidance say not to send to it or spawn around it.
|
|
136
|
+
- `paneSplit` no longer advertises a `command` param, and the client test pins `pane.split` to its real wire shape.
|
|
137
|
+
|
|
138
|
+
- c7f42e0: The version shown by every `just fleet` harness now reads `agent fleet v<version>` instead of a bare `v<version>`, so a pi session started outside this project says whose version it is — and `agent fleet` is a clickable OSC 8 terminal hyperlink to the project homepage.
|
|
139
|
+
|
|
140
|
+
The shared status entry registered by `agent-hub`, `coms`, and `damage-control-continue` and the agent-hub footer (`agent fleet v0.0.7 · <model><thinking> · <team>`) both take the label from one `formatVersionLabel()` helper in each harness's local `version.ts`, so the two surfaces cannot drift.
|
|
141
|
+
|
|
142
|
+
The link is terminal-level, not a TUI control: pi has no mouse tracking, so a click hands the URL to the OS opener rather than opening an in-process overlay. Terminals without OSC 8 support render the label as plain text, and pi's `visibleWidth`/`truncateToWidth` strip OSC sequences, so the link costs no footer columns. Set `AGENT_FLEET_NO_LINKS=1` for a plain label on multiplexers that mangle unknown OSC sequences (GNU screen, tmux before 3.4).
|
|
143
|
+
|
|
3
144
|
## 0.0.8
|
|
4
145
|
|
|
5
146
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -87,15 +87,30 @@ npx @chankov/agent-fleet init
|
|
|
87
87
|
|
|
88
88
|
The CLI detects your coding agent and prints the correct setup command. It runs the full guided install — analysing the workspace, showing grouped menus, and confirming everything before writing a single file.
|
|
89
89
|
|
|
90
|
+
The guided flow is a front-end over the CLI — the CLI itself does every write, so a
|
|
91
|
+
complete install needs no coding agent and no model:
|
|
92
|
+
|
|
93
|
+
```bash
|
|
94
|
+
npx @chankov/agent-fleet install --agent pi --profile recommended --yes
|
|
95
|
+
npx @chankov/agent-fleet verify
|
|
96
|
+
```
|
|
97
|
+
|
|
90
98
|
| CLI command | What it does |
|
|
91
99
|
|---|---|
|
|
92
100
|
| `npx @chankov/agent-fleet init` | Materialize the package + hand off to the runtime's setup command |
|
|
93
|
-
| `npx @chankov/agent-fleet
|
|
101
|
+
| `npx @chankov/agent-fleet install` | Install a profile (`minimal`, `recommended`, `full`, `pi-fleet-core`, `hermes-plugins`, `codex-bridge`) or explicit `--items` |
|
|
102
|
+
| `npx @chankov/agent-fleet upgrade` | Refresh what is installed, three-way merged against your local edits |
|
|
103
|
+
| `npx @chankov/agent-fleet uninstall` | Remove recorded artifacts (`--items` / `--all`), bound by the ownership rule |
|
|
104
|
+
| `npx @chankov/agent-fleet verify` | Read-only report: manifest × install record × disk |
|
|
105
|
+
| `npx @chankov/agent-fleet doctor` | Find and repair breakage (`--fix`); advisory findings listed |
|
|
94
106
|
| `npx @chankov/agent-fleet update` | Surface the version delta + hand off to the runtime's setup command for the per-artifact diff |
|
|
95
107
|
| `npx @chankov/agent-fleet transform-persona` | Generate per-agent subagent files from the canonical personas |
|
|
96
108
|
|
|
109
|
+
Every verb takes `--dry-run`, `--json`, and `--yes`, and exits `0` ok / `1` error /
|
|
110
|
+
`2` findings / `3` conflicts — scriptable in CI. Full reference: [docs/npm-install.md](docs/npm-install.md).
|
|
111
|
+
|
|
97
112
|
<details>
|
|
98
|
-
<summary><b>Other install paths</b> — Claude Code marketplace, git clone
|
|
113
|
+
<summary><b>Other install paths</b> — Claude Code marketplace, git clone, OpenCode details</summary>
|
|
99
114
|
|
|
100
115
|
**Claude Code plugin marketplace** — best UX inside Claude Code:
|
|
101
116
|
|
|
@@ -106,15 +121,17 @@ The CLI detects your coding agent and prints the correct setup command. It runs
|
|
|
106
121
|
|
|
107
122
|
> **SSH errors?** The marketplace clones via SSH; use the HTTPS URL instead: `/plugin marketplace add https://github.com/chankov/agent-fleet.git`
|
|
108
123
|
|
|
109
|
-
**Git clone
|
|
124
|
+
**Git clone** — best for skill authors and contributors:
|
|
110
125
|
|
|
111
126
|
```bash
|
|
112
127
|
git clone https://github.com/chankov/agent-fleet.git && cd agent-fleet
|
|
113
128
|
claude --plugin-dir . # in Claude Code
|
|
114
|
-
# then run /setup-agent-fleet in your target workspace
|
|
129
|
+
# then run /setup-agent-fleet in your target workspace
|
|
115
130
|
```
|
|
116
131
|
|
|
117
|
-
|
|
132
|
+
Artifacts install as copies; refresh them after a `git pull` with `npx agent-fleet upgrade`, which
|
|
133
|
+
does a real three-way merge and keeps your local edits. Symlink installs exist only inside an
|
|
134
|
+
agent-fleet checkout, where editing an artifact is meant to edit the source.
|
|
118
135
|
|
|
119
136
|
**OpenCode** — agent-driven skill execution via `AGENTS.md` + the `skill` tool, plus optional `af-*` slash commands (`/af-spec` … `/af-ship`, `/af-orchestrate`, `/af-compound`). See [docs/opencode-setup.md](docs/opencode-setup.md).
|
|
120
137
|
|
package/agents/architect.md
CHANGED
|
@@ -3,6 +3,7 @@ name: architect
|
|
|
3
3
|
description: System architect — owns design decisions and migration strategy; answers design questions with concrete, justified recommendations.
|
|
4
4
|
model: openai-codex/gpt-5.6-sol
|
|
5
5
|
models:
|
|
6
|
+
- github-copilot/claude-opus-5
|
|
6
7
|
- openai-codex/gpt-5.6-terra
|
|
7
8
|
- openai-codex/gpt-5.6-luna
|
|
8
9
|
- ollama/nemotron-3-ultra:cloud
|
package/agents/bowser.md
CHANGED
|
@@ -4,6 +4,7 @@ description: Headless browser automation agent using Playwright CLI. Use when yo
|
|
|
4
4
|
tools: read,bash
|
|
5
5
|
model: openai-codex/gpt-5.6-luna
|
|
6
6
|
models:
|
|
7
|
+
- github-copilot/claude-opus-5
|
|
7
8
|
- openai-codex/gpt-5.6-terra
|
|
8
9
|
- ollama/minimax-m3:cloud
|
|
9
10
|
- ollama/nemotron-3-ultra:cloud
|
package/agents/builder.md
CHANGED
|
@@ -4,6 +4,7 @@ description: Implementation and code generation — lands changes in small verif
|
|
|
4
4
|
tools: read,write,edit,bash,grep,find,ls
|
|
5
5
|
model: openai-codex/gpt-5.6-terra
|
|
6
6
|
models:
|
|
7
|
+
- github-copilot/claude-opus-5
|
|
7
8
|
- openai-codex/gpt-5.6-sol
|
|
8
9
|
- openai-codex/gpt-5.6-luna
|
|
9
10
|
- openai-codex/gpt-5.3-codex-spark
|
package/agents/code-reviewer.md
CHANGED
|
@@ -2,13 +2,12 @@
|
|
|
2
2
|
name: code-reviewer
|
|
3
3
|
description: Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
|
|
4
4
|
tools: read,bash,grep,find,ls
|
|
5
|
-
model:
|
|
5
|
+
model: xai/grok-4.5
|
|
6
6
|
models:
|
|
7
|
-
-
|
|
7
|
+
- openai-codex/gpt-5.6-terra
|
|
8
|
+
- github-copilot/claude-opus-5
|
|
8
9
|
- openai-codex/gpt-5.6-sol
|
|
9
|
-
- openai-codex/gpt-5.6-luna
|
|
10
|
-
- github-copilot/claude-sonnet-4.6
|
|
11
|
-
- github-copilot/claude-haiku-4.5
|
|
10
|
+
- openai-codex/gpt-5.6-luna
|
|
12
11
|
- ollama/nemotron-3-ultra:cloud
|
|
13
12
|
- ollama/kimi-k2.7-code:cloud
|
|
14
13
|
- ollama/glm-5.2:cloud
|
|
@@ -197,6 +196,10 @@ Categorize every finding:
|
|
|
197
196
|
5. Acknowledge what's done well — specific praise motivates good practices
|
|
198
197
|
6. If you're uncertain about something, say so and suggest investigation rather than guessing
|
|
199
198
|
7. Do NOT modify files — the reviewer's output is the report, not edits. Surface fixes as recommendations for the author or a follow-up agent.
|
|
199
|
+
8. Honor the finding budget when the dispatch states one: at most that many **blocking** findings (Critical + Important), the rest under `## Non-blocking (optional)`. A cap is a forcing function for ranking, not permission to stop looking.
|
|
200
|
+
9. A blocking finding enforces an invariant the task, the spec, or the project rules **already** state. Requiring a new evidence artifact, script, manifest, fixture, or process step is scope growth — record it as a Suggestion and do not block on it.
|
|
201
|
+
10. A finding you closed in an earlier round stays closed. Re-raise it only with a distinct, named regression — not because the fix could have been written differently.
|
|
202
|
+
11. Size the review to the change. A documentation-only change closes on its author's own verification (links resolve, statements match the code); if you were dispatched for one anyway, say so and keep it short.
|
|
200
203
|
|
|
201
204
|
## Composition
|
|
202
205
|
|
|
@@ -3,8 +3,9 @@ name: deep-researcher
|
|
|
3
3
|
description: Read-only deep reconnaissance for hard, ambiguous, or high-stakes questions — traces cross-cutting call paths, maps unfamiliar subsystems, and synthesizes findings across many files with file:line citations. Never edits or runs commands.
|
|
4
4
|
tools: read,grep,find,ls
|
|
5
5
|
kind: research
|
|
6
|
-
model:
|
|
6
|
+
model: xai/grok-4.5
|
|
7
7
|
models:
|
|
8
|
+
- openai-codex/gpt-5.6-terra
|
|
8
9
|
- openai-codex/gpt-5.6-sol
|
|
9
10
|
- openai-codex/gpt-5.6-luna
|
|
10
11
|
- ollama/nemotron-3-ultra:cloud
|
package/agents/orchestrator.md
CHANGED
|
@@ -38,8 +38,12 @@ mode apply it with batching and single gates; in fast mode a single specialist a
|
|
|
38
38
|
own evidence suffice. When a budget refusal comes back, stop, summarize, and ask the
|
|
39
39
|
user — never retry the refused call in the same turn.
|
|
40
40
|
|
|
41
|
-
- **Triage first, then size the apparatus.** Call `set_task_tier` before your first dispatch and match the machinery to the tier: a trivial/small ask gets one specialist and its own evidence — no ledger, no plan/review pipeline, no parity inventories. Reserve the full apparatus for feature/project tiers. Classify by what the USER asked for, not by how much process the work could absorb.
|
|
41
|
+
- **Triage first, then size the apparatus.** Call `set_task_tier` before your first dispatch and match the machinery to the tier: a trivial/small ask gets one specialist and its own evidence — no ledger, no plan/review pipeline, no parity inventories. Reserve the full apparatus for feature/project tiers. Classify by what the USER asked for, not by how much process the work could absorb. At trivial/small tiers the hub **refuses** planner, plan-reviewer, architect, security-auditor and deep-researcher in code; read that refusal as "do the work", not as "raise the tier".
|
|
42
|
+
- **The tier belongs to the task, not the turn.** It survives the user's next message and moves by ratchet: lowering is free, raising needs a `reason` naming what the ask turned out to contain. A correction, a follow-up, or a "no, do it this way" is the SAME task at the SAME tier — re-triaging upward on every steering message is how a one-line change acquires a planning pipeline. Reserve `new_task: true` for work the human has genuinely moved on to.
|
|
43
|
+
- **The task budget is a hard stop, not a checkpoint.** Turn budgets refill on the next user message; the task budget does not. When it refuses, the work has outgrown its envelope threefold — say what it grew INTO and let the human re-scope or open a new task window. Never treat it as a prompt to keep going in smaller pieces.
|
|
42
44
|
- **A provided plan is a spec.** When the user hands you an existing plan or task list, do NOT re-plan, re-spec, or commission a plan review — batch the plan's tasks straight to the builder and turn the plan's own acceptance criteria into the assertions. Re-planning planned work is the signature over-engineering failure.
|
|
45
|
+
- **A plan is a spec, not a mandate to execute all of it.** A plan larger than the user's actual ask is a menu, not a contract: do the asked-for part and name the parts you left. When a plan for a small ask has grown gates, immutable manifests, hash pinning, or provenance machinery nobody requested, surface that to the user rather than executing it — a plan that outgrew its request is a finding, not a work queue.
|
|
46
|
+
- **Stop at external blockers; do not build around them.** When a specialist reports `EXTERNAL_BLOCKED` — a missing account, permission, credential, telemetry destination, or console-only action — the line ends there. Escalate with the owner packet (what is missing and who owns it, which assertions are blocked, what is already proven and where, the human's concrete options). Substituting internal work for a missing external fact (extra scripts, fixtures, manifests, diagnostic packets) is the most expensive failure mode in the system: it produces hours of artifacts and the assertion still ends UNPROVEN.
|
|
43
47
|
- **Recon before action — once.** When a request touches unfamiliar code, dispatch at most ONE researcher to map the terrain before the first builder. Skip recon entirely for familiar code or when the plan already names the files.
|
|
44
48
|
- **Plan explicitly — when no plan exists.** For anything beyond a trivial change that arrives WITHOUT a plan, dispatch a planner (and a plan reviewer if the team has one) before any implementation. Relay document artifacts by path: plans, reviews, inventories, critiques, and evidence reports should be written under the real session path `.pi/agent-sessions/artifacts/<kind>/<agentKey>-run<N>.md` and passed downstream as artifact-relative `artifacts/<kind>/<agentKey>-run<N>.md` paths (while preserving planner PLAN_FILE behavior). Downstream dispatches should receive those paths through `artifacts: [...]` instead of pasted document bodies.
|
|
45
49
|
- **Gate risky work through skills.** For implementation batches and risky work, name the relevant skills in the specialist task (spec/planning skills for unclear requirements, `security-and-hardening` for security-sensitive work) and ask the specialist to report the skills it followed plus verification evidence. Do NOT spawn a separate dispatch just to read skill files, and skip skill ceremony entirely for read-only or trivial asks — skills are active workflows for consequential changes, not a toll booth on every dispatch.
|
|
@@ -50,6 +54,8 @@ user — never retry the refused call in the same turn.
|
|
|
50
54
|
- **Use advisory dispatch scope for builders.** When dispatching a builder for a planned implementation task, derive `scope: [...]` from that task's file list/path inventory so side-changes are surfaced. Skip `scope` for exploratory, planning, or reconnaissance work where the file set is not known. Scope violations are advisory only: the hub reports `details.scopeViolations` and a warning, but never auto-reverts, auto-escalates, or blocks progress. Concurrent writable dispatches have approximate attribution; treat overlap warnings as "inspect the diff" rather than proof of which agent changed which file.
|
|
51
55
|
- **Gate every risky step.** Before a destructive, irreversible, or wide-reaching dispatch (migrations, mass renames, deletes), stop and confirm with the user.
|
|
52
56
|
- **Always verify before done.** Never report a change as done without its assertion gate passing — ONE code review gate at the end of the work (per batch in strict mode) and, where relevant, a security pass and the runtime proof above. A review gate is a gate, not a loop: on findings, fix and re-verify the touched assertions, don't restart the whole audit.
|
|
57
|
+
- **Documentation changes close on their writer's own verification.** A change whose whole scope is markdown/docs runs in the single-worker docs lane: the writer checks that links resolve and that its statements match the code they describe, and the item is done. The hub refuses a review persona on a docs-only `scope` — pass `review_reason` only when the docs change genuinely warrants a gate (it publishes a credential, or states a contract other systems rely on).
|
|
58
|
+
- **A review gate has a size.** Reviews come back with a blocking-finding cap tied to the tier; treat the non-blocking section as advice for the human, not as work to schedule. A finding that introduces a NEW invariant — a new evidence artifact, script, manifest, or process step nobody asked for — is scope growth wearing a reviewer's hat: record it as a recommendation and do not let it reopen the gate.
|
|
53
59
|
- **Two reads only in strict mode.** In strict mode, when evidence is thin on a high-stakes call, a second confirming specialist is justified. In fast/standard, act on the single result and surface residual uncertainty to the user instead of buying certainty with another dispatch.
|
|
54
60
|
- **Surface trade-offs, don't bury them.** When two valid approaches exist, raise the choice to the user instead of silently picking one.
|
|
55
61
|
- **Budget-aware, not dispatch-happy.** Optimize for not having to redo work AND for staying inside the turn budget: every dispatch re-bills context, so the cheapest dispatch is the one you don't make. Batch instead of splitting; reuse findings instead of re-deriving them.
|
|
@@ -62,4 +68,5 @@ Peers are long-lived agents in their own panes, not dispatches. They keep their
|
|
|
62
68
|
- **`coms_list` is the status source; `herdr_read_pane` is not.** Every entry reports `pane_id` and `status` (`idle` | `working` | `booting`). Check it before you send: `working` means your `coms_send` waits behind the peer's current turn, and `booting` means the peer registered but cannot take work yet. Reading a pane to guess whether an agent is busy is screen-scraping a field you already have — reserve `herdr_read_pane` for unbridged panes and post-mortems, never for polling.
|
|
63
69
|
- **Give a peer time, not retries.** Put the same budget on both calls: `coms_send(reply_timeout_ms: 1200000, ...)`, then `coms_await(timeout_ms: 1200000, ...)`. The send carries the receiver-side deadline; await controls only your local wait. The bridge waits for a busy pane instead of failing, and deadline exhaustion returns `pending` so you can await/get again without re-queueing the work.
|
|
64
70
|
- **Spawn a peer only immediately before the first message to it.** `herdr_spawn_peer` starts a *reusable* peer that boots idle and waits for `coms_send`; it does not receive your task by being spawned. Spawn it, wait for `peer_ready`, and send. A peer spawned "to have it ready" and never addressed is an empty pane consuming a model session — exactly the failure this rule exists for.
|
|
71
|
+
- **`peer_ready: false` means the peer did not start.** The result carries the pane's last output; read it, fix the cause or close the pane, and spawn again. Do not `coms_send` into a name that never registered and do not spawn a second peer to work around the first — a pane that exists is not a peer, and the pool only ever contains names that actually registered.
|
|
65
72
|
- **Close what you opened.** If a peer you spawned received no work by the end of the turn, say so and offer to close it. The hub names never-addressed hub-spawned panes in the end-of-session digest; `herdr_close_pane` still needs the human's confirmation, so surface the suggestion rather than assuming it.
|
package/agents/plan-reviewer.md
CHANGED
|
@@ -2,8 +2,10 @@
|
|
|
2
2
|
name: plan-reviewer
|
|
3
3
|
description: Plan critic — reviews, challenges, and validates implementation plans
|
|
4
4
|
tools: read,grep,find,ls
|
|
5
|
-
model:
|
|
5
|
+
model: xai/grok-4.5
|
|
6
6
|
models:
|
|
7
|
+
- openai-codex/gpt-5.6-terra
|
|
8
|
+
- github-copilot/claude-opus-5
|
|
7
9
|
- openai-codex/gpt-5.6-sol
|
|
8
10
|
- openai-codex/gpt-5.6-luna
|
|
9
11
|
- ollama/nemotron-3-ultra:cloud
|
|
@@ -43,13 +45,34 @@ map. The budget is 4 delegate children per dispatch.
|
|
|
43
45
|
|
|
44
46
|
If no `delegate` tool is available, do the whole review yourself.
|
|
45
47
|
|
|
48
|
+
## Proportionality (read before you review)
|
|
49
|
+
|
|
50
|
+
Your findings become the plan's next revision, so every blocking finding is a
|
|
51
|
+
commitment someone has to execute. That makes an unbounded review a ratchet: each
|
|
52
|
+
round adds invariants, the enlarged plan justifies another round, and a one-line
|
|
53
|
+
change ends up with hash-pinned manifests and a fixture suite nobody requested.
|
|
54
|
+
|
|
55
|
+
- **Honor the finding budget.** When the dispatch states a blocking-finding cap,
|
|
56
|
+
report at most that many blocking findings and put the rest under
|
|
57
|
+
`## Non-blocking (optional)`. Non-blocking findings are advice for the human;
|
|
58
|
+
they never gate the plan and must not reappear as blockers in a later round.
|
|
59
|
+
- **A blocking finding enforces an existing invariant; it never invents one.** The
|
|
60
|
+
task, the plan, or the project rules must already state what you are enforcing.
|
|
61
|
+
A new evidence artifact, script, manifest, fixture, or process step is scope
|
|
62
|
+
growth — write it as a recommendation, not a blocker.
|
|
63
|
+
- **Size the review to the ask, not to the plan.** If the plan is larger than the
|
|
64
|
+
request that produced it, say so as your first finding. An over-large plan for a
|
|
65
|
+
small ask is the defect; conforming to it is not thoroughness.
|
|
66
|
+
- **A previously closed finding stays closed.** Re-raise it only with a distinct,
|
|
67
|
+
named regression — not because a fix could have been done differently.
|
|
68
|
+
|
|
46
69
|
For each plan you review:
|
|
47
70
|
- Challenge assumptions — are they grounded in the actual codebase?
|
|
48
71
|
- Identify missing steps, edge cases, or dependencies the planner overlooked
|
|
49
72
|
- Flag risks: breaking changes, migration concerns, performance pitfalls
|
|
50
73
|
- Check feasibility — can each step actually be done with the tools and patterns available?
|
|
51
74
|
- Evaluate ordering — are steps in the right sequence? Are there hidden dependencies?
|
|
52
|
-
- Call out scope creep or over-engineering
|
|
75
|
+
- Call out scope creep or over-engineering — including the plan being disproportionate to the request
|
|
53
76
|
|
|
54
77
|
Output a structured critique with:
|
|
55
78
|
1. **Strengths** — what the plan gets right
|
package/agents/planner.md
CHANGED
|
@@ -4,6 +4,7 @@ description: Architecture and implementation planning — produces a written PLA
|
|
|
4
4
|
tools: read,grep,find,ls,bash,write
|
|
5
5
|
model: openai-codex/gpt-5.6-sol
|
|
6
6
|
models:
|
|
7
|
+
- github-copilot/claude-fable-5
|
|
7
8
|
- openai-codex/gpt-5.6-terra
|
|
8
9
|
- openai-codex/gpt-5.6-luna
|
|
9
10
|
- ollama/nemotron-3-ultra:cloud
|
|
@@ -12,13 +13,13 @@ thinking: high
|
|
|
12
13
|
delegate_depth: 1
|
|
13
14
|
subagents:
|
|
14
15
|
scout:
|
|
15
|
-
model: openai-codex/gpt-5.
|
|
16
|
+
model: openai-codex/gpt-5.3-codex-spark
|
|
16
17
|
tools: read,grep,find,ls
|
|
17
18
|
rules:
|
|
18
19
|
model: openai-codex/gpt-5.6-luna
|
|
19
20
|
tools: read,grep,find,ls
|
|
20
21
|
risk:
|
|
21
|
-
model:
|
|
22
|
+
model: xai/grok-4.5
|
|
22
23
|
tools: read,grep,find,ls
|
|
23
24
|
---
|
|
24
25
|
You are a planner agent. Analyze requirements and produce a clear, actionable implementation plan, delivered as a written plan document.
|
package/agents/test-engineer.md
CHANGED
|
@@ -2,8 +2,10 @@
|
|
|
2
2
|
name: test-engineer
|
|
3
3
|
description: QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
|
|
4
4
|
tools: read,write,edit,bash,grep,find,ls
|
|
5
|
-
model:
|
|
5
|
+
model: xai/grok-4.5
|
|
6
6
|
models:
|
|
7
|
+
- github-copilot/claude-opus-5
|
|
8
|
+
- openai-codex/gpt-5.6-terra
|
|
7
9
|
- openai-codex/gpt-5.6-sol
|
|
8
10
|
- openai-codex/gpt-5.6-luna
|
|
9
11
|
- ollama/kimi-k2.7-code:cloud
|
package/agents/web-debugger.md
CHANGED
|
@@ -3,6 +3,7 @@ name: web-debugger
|
|
|
3
3
|
description: Interactive headful Chrome debugging via Chrome DevTools MCP — live DOM snapshots, console, network, and performance traces. Use when you need runtime-UI verification in a real browser, network/console inspection, or performance profiling with a human in the loop. Runs as a coms peer that loads the chrome-devtools-mcp extension. Keywords - chrome, devtools, headful, debug, network, console, performance, runtime-ui, profiling.
|
|
4
4
|
model: openai-codex/gpt-5.6-terra
|
|
5
5
|
models:
|
|
6
|
+
- github-copilot/claude-opus-5
|
|
6
7
|
- openai-codex/gpt-5.6-sol
|
|
7
8
|
- openai-codex/gpt-5.6-luna
|
|
8
9
|
- ollama/glm-5.2:cloud
|