@chankov/agent-fleet 0.0.2 → 0.0.4
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 +1 -1
- package/.claude/commands/setup-agent-fleet.md +5 -5
- package/.opencode/commands/af-doctor-agent-fleet.md +2 -0
- package/.opencode/commands/af-setup-agent-fleet.md +1 -1
- package/.pi/agents/peers.yaml +4 -0
- package/.pi/agents/teams.yaml +2 -2
- package/.pi/harnesses/agent-hub/README.md +254 -18
- package/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.pi/harnesses/agent-hub/delegate.ts +32 -9
- package/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.pi/harnesses/agent-hub/helpers.ts +49 -0
- package/.pi/harnesses/agent-hub/index.ts +1269 -322
- package/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.pi/harnesses/agent-hub/package.json +5 -4
- package/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.pi/harnesses/agent-hub/spawn.ts +161 -94
- package/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.pi/harnesses/ask-user-remote/README.md +2 -0
- package/.pi/harnesses/coms/README.md +21 -0
- package/.pi/harnesses/coms/index.ts +2 -0
- package/.pi/harnesses/coms/package.json +5 -4
- package/.pi/harnesses/coms/version.ts +18 -0
- package/.pi/harnesses/damage-control-continue/README.md +32 -31
- package/.pi/harnesses/damage-control-continue/index.ts +23 -9
- package/.pi/harnesses/damage-control-continue/package.json +5 -4
- package/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.pi/harnesses/{damage-control/shared.ts → lib/damage-control-shared.ts} +20 -6
- package/.pi/prompts/doctor-agent-fleet.md +1 -1
- package/.pi/prompts/setup-agent-fleet.md +5 -5
- package/.versions/0.0.4/.claude/commands/build.md +44 -0
- package/.versions/0.0.4/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.4/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.4/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.4/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.4/.claude/commands/plan.md +16 -0
- package/.versions/0.0.4/.claude/commands/prime.md +22 -0
- package/.versions/0.0.4/.claude/commands/review.md +16 -0
- package/.versions/0.0.4/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.4/.claude/commands/ship.md +72 -0
- package/.versions/0.0.4/.claude/commands/spec.md +15 -0
- package/.versions/0.0.4/.claude/commands/test.md +19 -0
- package/.versions/0.0.4/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.4/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.4/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.4/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.4/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.4/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.4/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.4/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.4/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.4/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.4/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.4/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.4/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.4/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/{.pi/harnesses/damage-control → .versions/0.0.4/.pi/extensions/agent-fleet-update-check}/package.json +1 -1
- package/.versions/0.0.4/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.4/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.4/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.4/.pi/extensions/package.json +9 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/README.md +18 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/index.ts +293 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.4/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.4/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.4/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.4/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.4/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.4/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.4/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.4/.pi/prompts/build.md +24 -0
- package/.versions/0.0.4/.pi/prompts/code-simplify.md +22 -0
- package/.versions/0.0.4/.pi/prompts/doctor-agent-fleet.md +15 -0
- package/.versions/0.0.4/.pi/prompts/plan.md +16 -0
- package/.versions/0.0.4/.pi/prompts/review.md +16 -0
- package/.versions/0.0.4/.pi/prompts/setup-agent-fleet.md +27 -0
- package/.versions/0.0.4/.pi/prompts/ship.md +17 -0
- package/.versions/0.0.4/.pi/prompts/spec.md +15 -0
- package/.versions/0.0.4/.pi/prompts/test.md +19 -0
- package/.versions/0.0.4/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.4/.version +1 -0
- package/.versions/0.0.4/agents/architect.md +23 -0
- package/.versions/0.0.4/agents/bowser.md +26 -0
- package/.versions/0.0.4/agents/builder.md +53 -0
- package/.versions/0.0.4/agents/code-reviewer.md +205 -0
- package/.versions/0.0.4/agents/deep-researcher.md +31 -0
- package/.versions/0.0.4/agents/documenter.md +18 -0
- package/.versions/0.0.4/agents/orchestrator.md +54 -0
- package/.versions/0.0.4/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.4/agents/planner.md +69 -0
- package/.versions/0.0.4/agents/releaser.md +24 -0
- package/.versions/0.0.4/agents/researcher.md +28 -0
- package/.versions/0.0.4/agents/security-auditor.md +166 -0
- package/.versions/0.0.4/agents/test-engineer.md +151 -0
- package/.versions/0.0.4/agents/web-debugger.md +42 -0
- package/.versions/0.0.4/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.4/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.4/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.4/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.4/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.4/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.4/docs/coms-hermes-bridge.md +121 -0
- package/.versions/0.0.4/docs/getting-started.md +183 -0
- package/.versions/0.0.4/docs/npm-install.md +337 -0
- package/.versions/0.0.4/docs/opencode-setup.md +248 -0
- package/.versions/0.0.4/docs/pi-extensions.md +288 -0
- package/.versions/0.0.4/docs/pi-setup.md +463 -0
- package/.versions/0.0.4/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.4/hermes/README.md +228 -0
- package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/.versions/0.0.4/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.4/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.4/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.4/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.4/hooks/hooks.json +14 -0
- package/.versions/0.0.4/hooks/session-start.sh +74 -0
- package/.versions/0.0.4/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.4/justfile +256 -0
- package/.versions/0.0.4/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.4/references/definition-of-done.md +67 -0
- package/.versions/0.0.4/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.4/references/observability-checklist.md +91 -0
- package/.versions/0.0.4/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.4/references/performance-checklist.md +153 -0
- package/.versions/0.0.4/references/prompting-patterns.md +380 -0
- package/.versions/0.0.4/references/security-checklist.md +179 -0
- package/.versions/0.0.4/references/testing-patterns.md +236 -0
- package/.versions/0.0.4/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.4/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.4/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.4/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.4/scripts/coms-hermes-bridge.ts +403 -0
- package/.versions/0.0.4/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.4/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.4/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.4/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.4/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.4/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.4/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.4/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.4/scripts/lib/hermes-bridge-core.ts +238 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.4/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.4/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.4/scripts/lib/team-project.ts +184 -0
- package/.versions/0.0.4/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.4/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.4/scripts/team-snapshot.ts +238 -0
- package/.versions/0.0.4/scripts/team-up.ts +333 -0
- package/.versions/0.0.4/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.4/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.4/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.4/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.4/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.4/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.4/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.4/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.4/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.4/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.4/skills/guided-workspace-setup/SKILL.md +535 -0
- package/.versions/0.0.4/skills/guided-workspace-setup/companion-manifest.json +33 -0
- package/.versions/0.0.4/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.4/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.4/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.4/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.4/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.4/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.4/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.4/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.4/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.4/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.4/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.4/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.4/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.4/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.4/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +53 -0
- package/README.md +103 -541
- package/agents/architect.md +1 -1
- package/agents/builder.md +1 -1
- package/agents/code-reviewer.md +1 -1
- package/agents/deep-researcher.md +3 -3
- package/agents/orchestrator.md +20 -11
- package/agents/plan-reviewer.md +3 -3
- package/agents/planner.md +1 -1
- package/agents/security-auditor.md +1 -1
- package/agents/test-engineer.md +11 -4
- package/bin/lib/validate-overrides.js +19 -0
- package/bin/snapshot-version.js +17 -1
- package/bin/sync-harness-versions.js +94 -0
- package/codex/CONDUCTOR.md +148 -0
- package/docs/ARCHITECTURE.md +210 -0
- package/docs/agent-fleet-setup.md +11 -0
- package/docs/claude-code-coms-bridge.md +10 -0
- package/docs/codex-remote-conductor.md +170 -0
- package/docs/coms-hermes-bridge.md +121 -0
- package/docs/getting-started.md +14 -0
- package/docs/npm-install.md +2 -0
- package/docs/pi-extensions.md +49 -14
- package/docs/pi-setup.md +12 -4
- package/hermes/README.md +228 -0
- package/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/dist/index.js +10 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/justfile +106 -23
- package/package.json +17 -5
- package/scripts/codex-conductor.ts +41 -0
- package/scripts/codex-remote-control.ts +167 -0
- package/scripts/coms-cli.ts +311 -199
- package/scripts/coms-hermes-bridge.ts +2 -2
- package/scripts/lib/codex-conductor.ts +88 -0
- package/scripts/lib/codex-remote-control.ts +480 -0
- package/scripts/lib/coms-envelope.ts +51 -6
- package/scripts/lib/fake-herdr-server.ts +88 -0
- package/scripts/lib/herdr-layout.ts +18 -3
- package/scripts/lib/hermes-bridge-core.ts +4 -4
- package/scripts/lib/hermes-monitor-herdr.ts +28 -0
- package/scripts/lib/hermes-monitor-model.ts +9 -0
- package/scripts/lib/hermes-monitor-registry.ts +6 -0
- package/scripts/lib/hermes-monitor-socket.ts +118 -0
- package/scripts/lib/hermes-monitor-store.ts +31 -0
- package/scripts/lib/team-project.ts +85 -1
- package/scripts/team-up.ts +77 -18
- package/skills/designing-agents/SKILL.md +2 -2
- package/skills/designing-agents/pi-harness-authoring.md +26 -13
- package/skills/guided-workspace-setup/SKILL.md +131 -102
- package/skills/guided-workspace-setup/companion-manifest.json +33 -0
- package/skills/peer-coms/SKILL.md +9 -0
- package/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.pi/harnesses/damage-control/README.md +0 -65
- package/.pi/harnesses/damage-control/index.ts +0 -250
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* Damage-Control (continue) —
|
|
2
|
+
* Damage-Control (continue) — fail-closed guardrails without aborting the agent turn
|
|
3
3
|
*
|
|
4
|
-
*
|
|
5
|
-
* - The
|
|
4
|
+
* On a blocked tool call:
|
|
5
|
+
* - The result is replaced with actionable feedback that
|
|
6
6
|
* distinguishes destructive vs non-destructive intent and tells the
|
|
7
7
|
* agent how to adapt.
|
|
8
8
|
* - We do NOT call ctx.abort(), so the agent's turn continues and can
|
|
@@ -23,10 +23,9 @@
|
|
|
23
23
|
* dispatcher over its coms socket and waits for the user's decision;
|
|
24
24
|
* timeout or denial fails closed.
|
|
25
25
|
*
|
|
26
|
-
* In this repo it is the
|
|
27
|
-
*
|
|
28
|
-
*
|
|
29
|
-
* Other specialists (builder, etc.) keep the hard-stop damage-control harness.
|
|
26
|
+
* In this repo it is the only supported safety harness: the agent-hub main
|
|
27
|
+
* session and every native specialist, research helper, and nested delegate
|
|
28
|
+
* use it. Missing safety plumbing makes Agent Hub refuse child dispatch.
|
|
30
29
|
*
|
|
31
30
|
* Usage: pi -e .pi/harnesses/damage-control-continue/index.ts
|
|
32
31
|
*/
|
|
@@ -50,7 +49,9 @@ import {
|
|
|
50
49
|
type AccessRequest,
|
|
51
50
|
type Exemption,
|
|
52
51
|
type ExemptionScope,
|
|
53
|
-
|
|
52
|
+
type PathRuleCategory,
|
|
53
|
+
} from "../lib/damage-control-shared.ts";
|
|
54
|
+
import { registerVersionStatus } from "./version.ts";
|
|
54
55
|
|
|
55
56
|
interface Rule {
|
|
56
57
|
pattern: string;
|
|
@@ -264,6 +265,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
264
265
|
});
|
|
265
266
|
|
|
266
267
|
pi.on("session_start", async (_event, ctx) => {
|
|
268
|
+
registerVersionStatus(ctx);
|
|
267
269
|
const projectRulesPath = path.join(ctx.cwd, ".pi", "damage-control-rules.yaml");
|
|
268
270
|
const globalRulesPath = path.join(os.homedir(), ".pi", "damage-control-rules.yaml");
|
|
269
271
|
const rulesPath = fs.existsSync(projectRulesPath) ? projectRulesPath : fs.existsSync(globalRulesPath) ? globalRulesPath : null;
|
|
@@ -297,6 +299,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
297
299
|
// those are exemptible/escalatable. Destructive bashToolPatterns leave
|
|
298
300
|
// this null and can never be exempted.
|
|
299
301
|
let matchedPattern: string | null = null;
|
|
302
|
+
let matchedCategory: PathRuleCategory | null = null;
|
|
300
303
|
|
|
301
304
|
const checkPaths = (pathsToCheck: string[]) => {
|
|
302
305
|
for (const p of pathsToCheck) {
|
|
@@ -304,6 +307,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
304
307
|
for (const zap of rules.zeroAccessPaths) {
|
|
305
308
|
if (isPathMatch(resolved, zap, ctx.cwd)) {
|
|
306
309
|
matchedPattern = zap;
|
|
310
|
+
matchedCategory = "zero_access";
|
|
307
311
|
return `Access to zero-access path restricted: ${zap}`;
|
|
308
312
|
}
|
|
309
313
|
}
|
|
@@ -323,6 +327,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
323
327
|
if (event.input.glob.includes(zap) || isPathMatch(event.input.glob, zap, ctx.cwd)) {
|
|
324
328
|
violationReason = `Glob matches zero-access path: ${zap}`;
|
|
325
329
|
matchedPattern = zap;
|
|
330
|
+
matchedCategory = "zero_access";
|
|
326
331
|
break;
|
|
327
332
|
}
|
|
328
333
|
}
|
|
@@ -335,6 +340,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
335
340
|
if (event.input.pattern.includes(zap) || isPathMatch(event.input.pattern, zap, ctx.cwd)) {
|
|
336
341
|
violationReason = `Find pattern matches zero-access path: ${zap}`;
|
|
337
342
|
matchedPattern = zap;
|
|
343
|
+
matchedCategory = "zero_access";
|
|
338
344
|
break;
|
|
339
345
|
}
|
|
340
346
|
}
|
|
@@ -362,6 +368,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
362
368
|
if (command.includes(zap)) {
|
|
363
369
|
violationReason = `Bash command references zero-access path: ${zap}`;
|
|
364
370
|
matchedPattern = zap;
|
|
371
|
+
matchedCategory = "zero_access";
|
|
365
372
|
break;
|
|
366
373
|
}
|
|
367
374
|
}
|
|
@@ -372,6 +379,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
372
379
|
if (command.includes(rop) && (/[\s>|]/.test(command) || command.includes("rm") || command.includes("mv") || command.includes("sed"))) {
|
|
373
380
|
violationReason = `Bash command may modify read-only path: ${rop}`;
|
|
374
381
|
matchedPattern = rop;
|
|
382
|
+
matchedCategory = "read_only";
|
|
375
383
|
break;
|
|
376
384
|
}
|
|
377
385
|
}
|
|
@@ -386,6 +394,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
386
394
|
if (matched) {
|
|
387
395
|
violationReason = `Bash command attempts to delete/move protected path: ${ndp}`;
|
|
388
396
|
matchedPattern = ndp;
|
|
397
|
+
matchedCategory = "no_delete";
|
|
389
398
|
break;
|
|
390
399
|
}
|
|
391
400
|
}
|
|
@@ -398,6 +407,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
398
407
|
if (isPathMatch(resolved, rop, ctx.cwd)) {
|
|
399
408
|
violationReason = `Modification of read-only path restricted: ${rop}`;
|
|
400
409
|
matchedPattern = rop;
|
|
410
|
+
matchedCategory = "read_only";
|
|
401
411
|
break;
|
|
402
412
|
}
|
|
403
413
|
}
|
|
@@ -429,9 +439,12 @@ export default function (pi: ExtensionAPI) {
|
|
|
429
439
|
const ONCE = "Allow once";
|
|
430
440
|
const TURN = "Allow for this turn";
|
|
431
441
|
const SESSION = "Allow for this session";
|
|
442
|
+
const choices = matchedCategory === "no_delete"
|
|
443
|
+
? [KEEP, ONCE]
|
|
444
|
+
: [KEEP, ONCE, TURN, SESSION];
|
|
432
445
|
const choice = await ctx.ui.select(
|
|
433
446
|
`🛡️ Blocked: ${event.toolName} — ${violationReason}`,
|
|
434
|
-
|
|
447
|
+
choices,
|
|
435
448
|
{ timeout: PROMPT_TIMEOUT_MS },
|
|
436
449
|
);
|
|
437
450
|
if (choice === ONCE) {
|
|
@@ -468,6 +481,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
468
481
|
tool: event.toolName,
|
|
469
482
|
rule: violationReason,
|
|
470
483
|
pattern: matchedPattern,
|
|
484
|
+
category: matchedCategory!,
|
|
471
485
|
invocation: invocation.slice(0, 500),
|
|
472
486
|
};
|
|
473
487
|
const decision = await requestAccessFromHub(endpoint, req);
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
import { readFileSync } from "node:fs";
|
|
2
|
+
|
|
3
|
+
export const VERSION_STATUS_KEY = "00-agent-fleet-version";
|
|
4
|
+
|
|
5
|
+
function readAdjacentVersion(): string | null {
|
|
6
|
+
try {
|
|
7
|
+
const manifest = JSON.parse(readFileSync(new URL("./package.json", import.meta.url), "utf8"));
|
|
8
|
+
return typeof manifest.version === "string" && manifest.version.length > 0 ? manifest.version : null;
|
|
9
|
+
} catch {
|
|
10
|
+
return null;
|
|
11
|
+
}
|
|
12
|
+
}
|
|
13
|
+
|
|
14
|
+
export const HARNESS_VERSION = readAdjacentVersion();
|
|
15
|
+
|
|
16
|
+
export function registerVersionStatus(ctx: { ui?: { setStatus?: (key: string, text: string) => void } }): void {
|
|
17
|
+
if (HARNESS_VERSION) ctx.ui?.setStatus?.(VERSION_STATUS_KEY, `v${HARNESS_VERSION}`);
|
|
18
|
+
}
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* Shared exemption + escalation plumbing for
|
|
2
|
+
* Shared exemption + escalation plumbing for damage-control-continue and agent-hub.
|
|
3
3
|
*
|
|
4
4
|
* Exemptions are runtime, session-scoped allowances layered on top of
|
|
5
5
|
* `.pi/damage-control-rules.yaml` — they never edit the rules file and only
|
|
@@ -7,11 +7,8 @@
|
|
|
7
7
|
* noDeletePaths), never to the destructive bashToolPatterns.
|
|
8
8
|
*
|
|
9
9
|
* Consumers:
|
|
10
|
-
* - damage-control-continue —
|
|
11
|
-
*
|
|
12
|
-
* from headless children
|
|
13
|
-
* - damage-control (hard stop) — honors pre-granted exemptions from the
|
|
14
|
-
* shared file only; no prompting, no escalation
|
|
10
|
+
* - damage-control-continue — /allow commands, block-time prompts, and
|
|
11
|
+
* escalation to the agent-hub dispatcher from headless children
|
|
15
12
|
* - agent-hub — computes the shared file path, passes the env plumbing to
|
|
16
13
|
* spawned children, and answers access_request envelopes on its coms socket
|
|
17
14
|
*/
|
|
@@ -28,6 +25,7 @@ export const EXEMPTIONS_FILE_ENV = "AGENT_HUB_EXEMPTIONS_FILE";
|
|
|
28
25
|
export const AGENT_ID_ENV = "AGENT_HUB_AGENT_ID";
|
|
29
26
|
|
|
30
27
|
export type ExemptionScope = "turn" | "session";
|
|
28
|
+
export type PathRuleCategory = "zero_access" | "read_only" | "no_delete";
|
|
31
29
|
|
|
32
30
|
export interface Exemption {
|
|
33
31
|
/** The protected pattern being unlocked — same syntax as the rules file entries. */
|
|
@@ -106,11 +104,27 @@ export interface AccessRequest {
|
|
|
106
104
|
tool: string;
|
|
107
105
|
rule: string;
|
|
108
106
|
pattern: string;
|
|
107
|
+
category: PathRuleCategory;
|
|
109
108
|
invocation: string;
|
|
110
109
|
}
|
|
111
110
|
|
|
112
111
|
export type AccessDecisionChoice = "deny" | "allow_once" | "allow_agent" | "allow_all";
|
|
113
112
|
|
|
113
|
+
/** Protected deletions are approved per invocation; broader grants stay operator-explicit. */
|
|
114
|
+
export function accessDecisionChoices(category: PathRuleCategory): AccessDecisionChoice[] {
|
|
115
|
+
return category === "no_delete"
|
|
116
|
+
? ["deny", "allow_once"]
|
|
117
|
+
: ["deny", "allow_once", "allow_agent", "allow_all"];
|
|
118
|
+
}
|
|
119
|
+
|
|
120
|
+
/** Coalesce identical asks without letting one delete approval cover sibling paths. */
|
|
121
|
+
export function accessRequestCacheKey(
|
|
122
|
+
request: Pick<AccessRequest, "agent" | "pattern" | "category" | "invocation">,
|
|
123
|
+
): string {
|
|
124
|
+
const base = `${request.agent}::${request.pattern}`;
|
|
125
|
+
return request.category === "no_delete" ? `${base}::${request.invocation}` : base;
|
|
126
|
+
}
|
|
127
|
+
|
|
114
128
|
export interface AccessDecision {
|
|
115
129
|
type: "access_decision";
|
|
116
130
|
msg_id: string;
|
|
@@ -10,6 +10,6 @@ Also flag and offer to rewrite any remaining YAML configs (`teams.yaml`, `peers.
|
|
|
10
10
|
|
|
11
11
|
Also validate `.ai/agent-fleet-overrides.md` when it exists, against the schema in `docs/agent-fleet-setup.md`: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed `agent-hub` keys, missing `rules:` folders, and `## env` `required:` names that are neither set nor declared in the root `.env`. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
|
|
12
12
|
|
|
13
|
-
Present findings as a `# | Path | Issue | Suggested fix` table and
|
|
13
|
+
Present the findings per the skill's Step 1 interaction contract: print a short text summary (counts per kind, advisory findings as report-only text), then ask one `ask_user` multi-select — *"Which fixes should I apply now?"* — each option titled `<path> — <issue>` with the proposed fix as its description, chunked at ≤ 9 options; empty selection or cancel applies nothing. Without the widget, print a `# | Path | Issue | Suggested fix` table instead and take the picks as text.
|
|
14
14
|
|
|
15
15
|
Never overwrite a regular file — only act on symlinks whose target is missing. Report `repaired`, `deleted`, and `skipped` counts, and append a `## doctor-runs` line to `.ai/agent-fleet-setup.md` with the date, agent, phase (`standalone`), and counts.
|
|
@@ -12,16 +12,16 @@ Analyse the workspace. If prior install state is found (`.ai/agent-fleet-setup.m
|
|
|
12
12
|
|
|
13
13
|
The Skills group draws from **two roots**: fleet-native `skills/` and the vendored upstream import `vendor/agent-skills-upstream/skills/` (see `docs/UPSTREAM-SKILLS.md`). On a name collision the native copy wins — never offer the vendored duplicate as a separate row.
|
|
14
14
|
|
|
15
|
-
Then present the install menu
|
|
15
|
+
Then present the install menu per the skill's Step 1 interaction contract — drive every decision through the `ask_user` widget, never a printed table awaiting a free-text reply (the table format is reserved for the no-widget fallback when the user declined the bootstrap). Open with the **Express question** (fresh workspace: `Recommended ★` / `Everything` / `Custom — group by group` / `Nothing`; existing: `Keep as-is` / `Apply updates` / `Keep + add recommended ★` / `Custom`) — any answer but `Custom` skips all group screens. On `Custom`, run the **7 groups** (4 shared: Skills, Agent personas, Commands/prompts, References & Hooks; 3 pi-only: pi extensions & runtime skills, pi harnesses, External pi packages): each opens as a single-select quick screen (`Recommended ★ (n)` / `Everything (m)` / `Customise` / `Skip group`, or the installed-state variants with `Remove some…`), and multi-select drill-ins appear only behind `Customise`, chunked by sub-category (lifecycle phase for Skills, `rw`/`ro`/`pi-only` for personas, harness category, …) at ≤ 9 options per call, ≤ 8 `context` lines. Option titles carry `name ★ [st]` (`ok`/`upd`/`mod`/`cflt`/`gone`/`new`/`pkg`/`—`/`brk`); descriptions carry the purpose plus the state in plain words (`mod` → warn that refreshing overwrites local edits). There is **no pre-checking** (`ask_user` has no preselect) — installed state shows as counts on quick screens and words in descriptions; leaving an installed item unselected in a drill-in keeps it as-is. Freeform stays on so `all` / `recommended` (adds `★` on top — never removes) / `none` / `keep` still work; cancel = keep-as-is/skip. `cflt` rows are resolved only by printing the three-way diff and asking per row with `displayMode: "inline"` — never by Express or `Apply updates`. The External pi packages group lists `pi-ask-user` and the optional suggested `pi-codex-image-gen`. After Step 5b, `pi-ask-user` normally counts toward `Keep as-is` (`pkg`, scope `project` / `bundled by @chankov/agent-fleet` / `global` — state it in the restate line, no duplicate entries). `pi-codex-image-gen` is not bundled or bootstrapped; offer `pi install -l npm:pi-codex-image-gen` only when the user selects it. Never offer `setup`, `doctor`, or `guided-workspace-setup` — those are installer-only and live in the source agent-fleet repo.
|
|
16
16
|
|
|
17
|
-
|
|
17
|
+
Removal happens **only** on an explicit `Remove some…` multi-select (empty selection = remove nothing), and it is scoped: the screen lists only items whose name is in the agent-fleet inventory **and** that are recorded in `## install-status` (or are symlinks resolving into the source repo). User-authored skills, custom commands, third-party plugins, external pi packages not recorded by this setup, and unrelated settings/env keys are left untouched and logged as "Skipped — not owned by agent-fleet".
|
|
18
18
|
|
|
19
19
|
**No cross-tool substitution.** Each row is offered only when the source file the chosen agent needs already exists — for `pi`, that means `.pi/prompts/<name>.md`, `.pi/extensions/<name>/`, etc. Never fall back to `.claude/commands/` (or another agent's tree) to satisfy a pi prompt request; items missing their per-agent source are filtered out of the menu entirely.
|
|
20
20
|
|
|
21
21
|
**Personas are generated for non-pi targets.** The personas group lists the full availability roster from `node <source-root>/bin/cli.js transform-persona --list --agent <agent>`. For `pi` the canonical `agents/<name>.md` installs as-is (copy or symlink). For `claude-code`/`opencode` the apply step runs `transform-persona --agent <agent> --workspace <workspace> <name…>` instead — always a generated copy, even in symlink mode — and records the rows with `transformed: true`; status checks diff against the generated output, not the raw source.
|
|
22
22
|
|
|
23
|
-
**pi harness companions.** Installing, refreshing, or removing any pi harness also refreshes its companions in the same pass — the `justfile` launch recipes, `scripts/team-up.ts`, the peer/team YAML and personas, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json`. When `agent-hub` is installed or kept, keep its required launch companions together: `damage-control
|
|
23
|
+
**pi harness companions.** Installing, refreshing, or removing any pi harness also refreshes its companions in the same pass — the `justfile` launch recipes, `scripts/team-up.ts`, the peer/team YAML and personas, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json`. When `agent-hub` is installed or kept, keep its required launch companions together: `damage-control-continue` and `ask-user-remote`; the managed `just hub` / `hub-solo` recipes load both before `agent-hub`, and every native child inherits continue. Treat the retired `damage-control` hard-stop directory as `gone`: remove it only when recorded and unchanged against the recorded snapshot, or when it is a symlink into the source root (including a broken retirement link); preserve every user-modified or unowned copy. Refresh the `justfile` from the **current** source so retired-harness recipes are pruned and new ones added, rewriting only the managed region between the `agent-fleet:harnesses` sentinels so any user recipes survive.
|
|
24
24
|
|
|
25
|
-
**No mid-apply overwrite prompts.** The
|
|
25
|
+
**No mid-apply overwrite prompts.** The `mod` description already warns that refreshing overwrites local edits. The user's selection is the consent; the Step 9 confirmation is the single gate. During apply, refresh selected items unconditionally — never pause to ask "should I overwrite this file?". Genuine errors (permission denied, missing source) still stop and report.
|
|
26
26
|
|
|
27
|
-
Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis, and record what was installed in `.ai/agent-fleet-setup.md`.
|
|
27
|
+
Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis (print each draft, then `Accept` / `Edit` / `Skip` per section via `ask_user`), and record what was installed in `.ai/agent-fleet-setup.md`. Print the plan as compact action-grouped lines (Add / Refresh / Remove / Keep-count / Records / Method), then confirm with one `ask_user` single-select asked with `displayMode: "inline"` — `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel` — and write nothing until an Apply is chosen. Then perform the setup, re-scan for any new breakage, and report what changed.
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:incremental-implementation skill alongside agent-fleet:test-driven-development.
|
|
6
|
+
|
|
7
|
+
## Modes
|
|
8
|
+
|
|
9
|
+
- **`/build`** — implement the *next* pending task, then stop (careful, one slice at a time).
|
|
10
|
+
- **`/build auto`** — generate the plan if needed, get a single approval, then implement *every* task without stopping between them.
|
|
11
|
+
|
|
12
|
+
`$ARGUMENTS` selects the mode. Treat `auto` (canonical) or `all` as autonomous mode; anything else (or empty) is the default single-task mode. Note: autonomous mode is not faster *per task* — it runs the same test-driven loop — it only removes the human stepping *between* tasks.
|
|
13
|
+
|
|
14
|
+
## Default: one task
|
|
15
|
+
|
|
16
|
+
Pick the next pending task from the plan. Then:
|
|
17
|
+
|
|
18
|
+
1. Read the task's acceptance criteria
|
|
19
|
+
2. Load relevant context (existing code, patterns, types)
|
|
20
|
+
3. Write a failing test for the expected behavior (RED)
|
|
21
|
+
4. Implement the minimum code to pass the test (GREEN)
|
|
22
|
+
5. Run the full test suite to check for regressions
|
|
23
|
+
6. Run the build to verify compilation
|
|
24
|
+
7. Commit with a descriptive message
|
|
25
|
+
8. Mark the task complete and stop
|
|
26
|
+
|
|
27
|
+
## Autonomous: the whole plan (`/build auto`)
|
|
28
|
+
|
|
29
|
+
Use this once a spec exists and you want to collapse plan + build into one run. It removes the manual stepping between tasks — **not** the verification. Every task still earns a passing test and its own commit.
|
|
30
|
+
|
|
31
|
+
1. **Require a spec.** Look only for a spec at a known path: `SPEC.md` at the repo root, `docs/SPEC.md`, or a file under `spec/`. A README or arbitrary doc does **not** count. If none exists, stop and tell the user to run `/spec` first — do not invent requirements.
|
|
32
|
+
2. **Establish a clean baseline.** Run `git status --porcelain`. If there are uncommitted changes outside the expected planning artifacts (`SPEC.md`, `docs/SPEC.md`, `spec/*`, `tasks/plan.md`, `tasks/todo.md`), stop and ask the user to commit, stash, or confirm how to handle them. Autonomous per-task commits must not absorb unrelated local work, or the clean-rollback guarantee breaks.
|
|
33
|
+
3. **Plan if needed.** If there is no `tasks/plan.md`, invoke agent-fleet:planning-and-task-breakdown to generate one.
|
|
34
|
+
4. **Single checkpoint.** Present the full plan and wait for an unambiguous affirmative (e.g. "approve", "go", "yes"). Treat hedged responses ("looks reasonable", "I guess") as **not** approved. This is the only human gate — after approval, run autonomously. If you generated `tasks/plan.md`, commit it as a single preparatory commit now so it doesn't bleed into the first task's commit.
|
|
35
|
+
5. **Execute every task in dependency order.** Use each task's declared dependencies; if they aren't explicit, execute in the order the plan lists them. For each task, run the full default loop above (RED → GREEN → regression → build → commit → mark complete). Stage only the files that task touched plus its task-status update — never `git add -A` blindly — and make one commit per task so any point is a clean rollback.
|
|
36
|
+
6. **Stop and ask the user** (do not push through) when:
|
|
37
|
+
- a test can't be made to pass or the build breaks without an obvious fix → follow agent-fleet:debugging-and-error-recovery
|
|
38
|
+
- the spec is ambiguous, or a task needs a decision the spec doesn't cover
|
|
39
|
+
- a task is high-risk or irreversible — auth/permission changes, destructive data migrations, payments, deletions, deploys, anything touching secrets, **or anything you can't undo with `git revert`** → follow agent-fleet:doubt-driven-development and get explicit sign-off before continuing
|
|
40
|
+
|
|
41
|
+
After the user resolves a blocker, they re-invoke `/build auto` — it resumes from the next pending task.
|
|
42
|
+
7. **Summarize at the end:** tasks completed, tests added, commits made, and anything skipped, flagged, or left for the user.
|
|
43
|
+
|
|
44
|
+
If any step fails, follow the agent-fleet:debugging-and-error-recovery skill.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Simplify code for clarity and maintainability — reduce complexity without changing behavior
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:code-simplification skill.
|
|
6
|
+
|
|
7
|
+
Simplify recently changed code (or the specified scope) while preserving exact behavior:
|
|
8
|
+
|
|
9
|
+
1. Read CLAUDE.md and study project conventions
|
|
10
|
+
2. Identify the target code — recent changes unless a broader scope is specified
|
|
11
|
+
3. Understand the code's purpose, callers, edge cases, and test coverage before touching it
|
|
12
|
+
4. Scan for simplification opportunities:
|
|
13
|
+
- Deep nesting → guard clauses or extracted helpers
|
|
14
|
+
- Long functions → split by responsibility
|
|
15
|
+
- Nested ternaries → if/else or switch
|
|
16
|
+
- Generic names → descriptive names
|
|
17
|
+
- Duplicated logic → shared functions
|
|
18
|
+
- Dead code → remove after confirming
|
|
19
|
+
5. Apply each simplification incrementally — run tests after each change
|
|
20
|
+
6. Verify all tests pass, the build succeeds, and the diff is clean
|
|
21
|
+
|
|
22
|
+
If tests fail after a simplification, revert that change and reconsider. Use `code-review-and-quality` to review the result.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Design and write a new agent persona (agents/), workflow skill (skills/), or pi harness (.pi/harnesses/)
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:designing-agents skill.
|
|
6
|
+
|
|
7
|
+
Begin by understanding what the user wants to author:
|
|
8
|
+
1. Is this a **persona** (a role/lens the agent adopts, e.g. a reviewer or auditor), a **skill** (a repeatable workflow with gated steps and verification), or a **pi harness** (a TypeScript pi extension that reshapes the session — footer, tool-call gate, new command, or orchestrator)?
|
|
9
|
+
2. The one-sentence purpose and when it should be invoked
|
|
10
|
+
3. The framework or steps — dimensions evaluated (persona), ordered workflow (skill), or session surface and events hooked (harness)
|
|
11
|
+
4. Explicit non-goals and scope limits
|
|
12
|
+
5. Output shape — what a typical invocation should produce
|
|
13
|
+
|
|
14
|
+
Then scan the target location (`agents/`, `skills/`, or `.pi/harnesses/`) for overlap, draft the artifact using the matching template — four-block persona structure, the section order from `docs/skill-anatomy.md`, or the harness pattern in `skills/designing-agents/pi-harness-authoring.md` — verify the draft against `references/prompting-patterns.md`, and confirm with the user before writing the file(s).
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the Doctor scan from the `agent-fleet:guided-workspace-setup` skill — Step 5 (the preflight scan) — without running the rest of the install flow. Use this when the user wants the repair pass on its own; the full `/setup-agent-fleet` flow runs the same scan automatically as soon as it detects prior install state.
|
|
6
|
+
|
|
7
|
+
Walk every install-target directory the chosen coding agent uses (`agents/`, `.claude/agents/`, `.opencode/agent/` (+ legacy `.opencode/agents/`), `.pi/agents/`, `.claude/skills/`, `.opencode/skills/`, `.pi/skills/`, `.agents/skills`, `.claude/commands/`, `.opencode/commands/`, `.pi/prompts/`, `.claude/references/`, `.claude/hooks/`). For each broken symlink, resolve where it pointed, look for a canonical replacement in the source `agents/` and `skills/` trees, and offer to repair or delete (persona links under `.claude/agents/` and `.opencode/agent(s)/` are repaired by regenerating a transformed copy via `transform-persona`, not by re-symlinking the raw source). Common stale names from the pre-merge persona layout: `reviewer` → `code-reviewer`, `red-team` → `security-auditor`.
|
|
8
|
+
|
|
9
|
+
Also flag and offer to rewrite any remaining YAML configs (`teams.yaml`, `peers.yaml`, etc.) that still reference removed persona names.
|
|
10
|
+
|
|
11
|
+
Also flag malformed peer entries in `.pi/agents/peers.yaml`: field lines (`persona:`, `model:`, ...) that sit under a team heading before any `- name: ...` list item. The team-up launcher's minimal parser silently drops such lines, so the peer never spawns and nothing errors — the usual cause is a `- name:` line lost in an edit. These findings are advisory only: report them with the missing `- name: <peer>` suggestion, never rewrite the file.
|
|
12
|
+
|
|
13
|
+
Also validate `.ai/agent-fleet-overrides.md` when it exists, against the schema in `docs/agent-fleet-setup.md`: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed `agent-hub` keys, missing `rules:` folders and `docs:` entry points, and `## env` `required:` names that are neither set nor declared in the root `.env`. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
|
|
14
|
+
|
|
15
|
+
Present the findings per the skill's Step 1 interaction contract: print a short text summary (counts per kind, advisory findings as report-only text), then ask one `AskUserQuestion` multi-select — *"Which fixes should I apply now?"* — each option titled `<path> — <issue>` with the proposed fix as its description, chunked at ≤ 4 options per question; an empty selection applies nothing.
|
|
16
|
+
|
|
17
|
+
Never overwrite a regular file — only act on symlinks whose target is missing. Report `repaired`, `deleted`, and `skipped` counts, and append a `## doctor-runs` line to `.ai/agent-fleet-setup.md` with the date, agent, phase (`standalone`), and counts.
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Orchestrate a config-defined team of subagents — route planner/builder (and more) as a runtime roster, handling NEEDS_RESEARCH and PLAN_FILE handoffs
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
You are the **orchestrator**. The primary agent drives a team of installed Claude Code
|
|
6
|
+
subagents to deliver the task in `$ARGUMENTS`. Subagents cannot nest — **all dispatching is
|
|
7
|
+
yours**.
|
|
8
|
+
|
|
9
|
+
## Roles
|
|
10
|
+
|
|
11
|
+
| Role | What it does |
|
|
12
|
+
|---|---|
|
|
13
|
+
| `researcher` | Always-available read-only recon. Cites `file:line`. Never edits. |
|
|
14
|
+
| `planner` | Writes a plan doc only; ends with `PLAN_FILE: <path>` or pauses on `NEEDS_RESEARCH:`. |
|
|
15
|
+
| `builder` | Implements in small increments; may pause on `NEEDS_RESEARCH:`. |
|
|
16
|
+
| `plan-reviewer` / `code-reviewer` | Read-only; their whole result is findings (no handoff marker). |
|
|
17
|
+
|
|
18
|
+
## Step 0 — Resolve the team
|
|
19
|
+
|
|
20
|
+
1. Read `.claude/orchestrate-teams.yaml` (a map of team-name → ordered persona list).
|
|
21
|
+
2. Resolve team + task from `$ARGUMENTS`:
|
|
22
|
+
- Treat the **first token** as a team name **only** when it is a bare single word that
|
|
23
|
+
exactly matches a config key **and** is followed by the rest of the task. To force a
|
|
24
|
+
team explicitly, the user writes `/orchestrate team=<name> <task>`. Otherwise the
|
|
25
|
+
team is the first key (`default`) and all of `$ARGUMENTS` is the task.
|
|
26
|
+
- **Fallbacks:** if the config is **absent / empty / fails to parse**, fall back to the
|
|
27
|
+
built-in `planner` + `builder` default and **say which fallback fired** (don't proceed
|
|
28
|
+
silently). If a named team is requested but not found, list the available team keys and
|
|
29
|
+
ask rather than guessing.
|
|
30
|
+
3. **Validate personas:** each persona in the resolved team must exist in `.claude/agents/`.
|
|
31
|
+
Skip-with-warning any that don't. If every persona is missing, fall back to the built-in
|
|
32
|
+
default.
|
|
33
|
+
4. List the resolved team back to the user before dispatching.
|
|
34
|
+
|
|
35
|
+
`researcher` / `deep-researcher` are **always available** even when not listed in the team.
|
|
36
|
+
|
|
37
|
+
## Step 1 — The team is a roster, not a fixed pipeline
|
|
38
|
+
|
|
39
|
+
The persona list is the set of specialists you may route to; **you decide the order at
|
|
40
|
+
runtime from the task state** (the listed order is only a sensible starting default). So:
|
|
41
|
+
|
|
42
|
+
- **Skip `planner`** when a usable plan already exists (the user passed a `PLAN_FILE` or
|
|
43
|
+
pointed at one) — go straight to `builder`.
|
|
44
|
+
- **Re-dispatch `researcher` at any point** — after `planner`, mid-build — whenever a
|
|
45
|
+
specialist needs a fact checked, not only as a first step.
|
|
46
|
+
- **Loop back to `planner`** if `builder` surfaces that the plan is wrong.
|
|
47
|
+
|
|
48
|
+
Do **not** enforce a hard `researcher → planner → builder` sequence.
|
|
49
|
+
|
|
50
|
+
## The Verification Contract (applies across every step)
|
|
51
|
+
|
|
52
|
+
Read `skills/orchestration-verification/SKILL.md` before non-trivial work and hold its
|
|
53
|
+
contract for the whole run. Subagents here cannot persist a shared ledger, so **you** keep
|
|
54
|
+
the acceptance assertions in your own working notes and refuse "done" until each is proven.
|
|
55
|
+
|
|
56
|
+
- **Build the assertions first.** Before dispatching `builder` for any non-trivial task,
|
|
57
|
+
convert the request into numbered, tagged assertions (`test` | `runtime-ui` | `code-grep`
|
|
58
|
+
| `manual`, one checkable pass condition each). Pass the relevant assertions **verbatim**
|
|
59
|
+
into each dispatch and advance only on assertions that come back *proven with named
|
|
60
|
+
evidence* — propagation in prose is not verification.
|
|
61
|
+
- **Inventory parity for "behave like X" requests.** When the request is "make X behave like
|
|
62
|
+
existing Y", dispatch `researcher` / `deep-researcher` **first** to enumerate every site
|
|
63
|
+
where the exemplar is special-cased (flags, branches, display, validation, translations,
|
|
64
|
+
fixtures, tests), and turn each site into an assertion covering the *whole* set — otherwise
|
|
65
|
+
the exemplar ships and its siblings are missed.
|
|
66
|
+
- **Require runtime proof for UI assertions.** A `runtime-ui` assertion (visibility,
|
|
67
|
+
placement, "appears in the table") is closed only by an actual runtime observation via
|
|
68
|
+
`browser-testing-with-devtools`, never a static review.
|
|
69
|
+
- **Accept assertion status, not verdicts.** Treat specialist returns as `assertions_proven`
|
|
70
|
+
/ `assertions_unproven` / `assertions_failed`; demote any "approved" claim with no named
|
|
71
|
+
evidence to unproven and re-dispatch it.
|
|
72
|
+
- **Reset on "wrong again".** When the user reports a delivered requirement is wrong again,
|
|
73
|
+
treat prior summaries as suspect, rebuild the affected assertions from the **latest**
|
|
74
|
+
correction (re-running the parity inventory for "behave like" cases), then re-dispatch.
|
|
75
|
+
|
|
76
|
+
## Step 2 — Route to specialists, honouring handoff markers
|
|
77
|
+
|
|
78
|
+
State the chosen next step (and why) before each dispatch, so routing is visible.
|
|
79
|
+
|
|
80
|
+
- `planner` → read its `PLAN_FILE: <path>` and load the plan.
|
|
81
|
+
- `builder` → loop over the plan's `## Task List`, **one task per dispatch**, checking each
|
|
82
|
+
task's acceptance criteria **and the relevant acceptance assertions** before moving on.
|
|
83
|
+
- **Marker-less personas** (`plan-reviewer` / `code-reviewer`) emit no handoff marker —
|
|
84
|
+
their returned report **is** the result; "done" = the report came back, nothing to wait
|
|
85
|
+
for. Fold findings forward; if a `code-reviewer` raised must-fix issues, loop back to
|
|
86
|
+
`builder`.
|
|
87
|
+
|
|
88
|
+
## Step 3 — NEEDS_RESEARCH dispatch (core)
|
|
89
|
+
|
|
90
|
+
Whenever any persona's result contains one or more `NEEDS_RESEARCH: <question>` lines:
|
|
91
|
+
|
|
92
|
+
1. Pause that track.
|
|
93
|
+
2. Dispatch `researcher` (read-only) once per question — in parallel when independent.
|
|
94
|
+
3. Collect the findings.
|
|
95
|
+
4. Resume the paused persona by re-dispatching it with the **original task plus the
|
|
96
|
+
findings inlined**.
|
|
97
|
+
|
|
98
|
+
**Never** answer a `NEEDS_RESEARCH` by guessing.
|
|
99
|
+
|
|
100
|
+
## Step 4 — Reviewer only if present
|
|
101
|
+
|
|
102
|
+
The `default` roster has **no reviewer**. After the final builder task's acceptance criteria
|
|
103
|
+
pass, report completion and **state explicitly that review/verification was not run** and
|
|
104
|
+
which acceptance assertions therefore remain unproven (the user can pick the `full` team or
|
|
105
|
+
run `/review`). When the active team *does* include a reviewer, run it as a normal step and
|
|
106
|
+
require it to report parity across sibling cases, not just the exemplar.
|
|
107
|
+
|
|
108
|
+
## Step 5 — Report
|
|
109
|
+
|
|
110
|
+
Report crisply: **active team**, what changed, which acceptance assertions are **proven (with
|
|
111
|
+
evidence)**, which remain **unproven or failed**, and what's next. Never report "done" while a
|
|
112
|
+
relevant assertion is unproven.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Break work into small verifiable tasks with acceptance criteria and dependency ordering
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:planning-and-task-breakdown skill.
|
|
6
|
+
|
|
7
|
+
Read the existing spec (SPEC.md or equivalent) and the relevant codebase sections. Then:
|
|
8
|
+
|
|
9
|
+
1. Enter plan mode — read only, no code changes
|
|
10
|
+
2. Identify the dependency graph between components
|
|
11
|
+
3. Slice work vertically (one complete path per task, not horizontal layers)
|
|
12
|
+
4. Write tasks with acceptance criteria and verification steps
|
|
13
|
+
5. Add checkpoints between phases
|
|
14
|
+
6. Present the plan for human review
|
|
15
|
+
|
|
16
|
+
Save the plan to the location the `planning-and-task-breakdown` skill defines (default `docs/plans/{area}/PLAN-{prd-name}-{phase}.md`, with the task list embedded — no separate todo file; overridable per project via `.ai/agent-fleet-overrides.md`). Match the project's existing `docs`/`Docs` capitalization.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Load foundational context for the agent-fleet repository
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Purpose
|
|
6
|
+
|
|
7
|
+
Orient yourself in **agent-fleet** — a collection of production-grade engineering skills
|
|
8
|
+
for AI coding agents, plus pi extensions, specialist agent personas, and lifecycle
|
|
9
|
+
commands that map to the software development lifecycle.
|
|
10
|
+
|
|
11
|
+
## Workflow
|
|
12
|
+
|
|
13
|
+
1. Run `git ls-files` to see the full project file tree
|
|
14
|
+
2. Read `README.md` and `CLAUDE.md` for the project overview and conventions
|
|
15
|
+
3. Read `docs/skill-anatomy.md` to learn the required skill format
|
|
16
|
+
4. Skim `skills/*/SKILL.md` — the core skills, grouped by lifecycle phase
|
|
17
|
+
(Define → Plan → Build → Verify → Review → Ship)
|
|
18
|
+
5. Read `agents/*.md` — the specialist review personas
|
|
19
|
+
6. Read `docs/pi-extensions.md`, `.pi/extensions/*/README.md` (always-on utilities), and `.pi/harnesses/*/README.md` (selectable session harnesses)
|
|
20
|
+
7. Summarize your understanding: purpose, structure, key files, and entry points
|
|
21
|
+
|
|
22
|
+
Do this directly — read the files yourself rather than delegating to subagents.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Conduct a five-axis code review — correctness, readability, architecture, security, performance
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:code-review-and-quality skill.
|
|
6
|
+
|
|
7
|
+
Review the current changes (staged or recent commits) across all five axes:
|
|
8
|
+
|
|
9
|
+
1. **Correctness** — Does it match the spec? Edge cases handled? Tests adequate?
|
|
10
|
+
2. **Readability** — Clear names? Straightforward logic? Well-organized?
|
|
11
|
+
3. **Architecture** — Follows existing patterns? Clean boundaries? Right abstraction level?
|
|
12
|
+
4. **Security** — Input validated? Secrets safe? Auth checked? (Use security-and-hardening skill)
|
|
13
|
+
5. **Performance** — No N+1 queries? No unbounded ops? (Use performance-optimization skill)
|
|
14
|
+
|
|
15
|
+
Categorize findings as Critical, Important, or Suggestion.
|
|
16
|
+
Output a structured review with specific file:line references and fix recommendations.
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:guided-workspace-setup skill.
|
|
6
|
+
|
|
7
|
+
Run the guided install for a target workspace. If the user passed a workspace path, use it; otherwise ask for it. Detect the running coding agent and confirm it with the user.
|
|
8
|
+
|
|
9
|
+
Analyse the workspace. If prior install state is found (`.ai/agent-fleet-setup.md` or a populated agent directory), run the **Doctor preflight** first (Step 5) — scan for broken symlinks and stale persona references, present findings as a table, and apply the fixes the user picks before continuing.
|
|
10
|
+
|
|
11
|
+
The Skills group draws from **two roots**: fleet-native `skills/` and the vendored upstream import `vendor/agent-skills-upstream/skills/` (see `docs/UPSTREAM-SKILLS.md`). On a name collision the native copy wins — never offer the vendored duplicate as a separate row.
|
|
12
|
+
|
|
13
|
+
Then present the install menu per the skill's Step 1 interaction contract — drive every decision through `AskUserQuestion`, never a printed table awaiting a free-text reply. Open with the **Express question** (fresh workspace: `Recommended ★` / `Everything` / `Custom — group by group` / `Nothing`; existing: `Keep as-is` / `Apply updates` / `Keep + add recommended ★` / `Custom`) — any answer but `Custom` skips all group screens. On `Custom`, run the **7 groups** (4 shared: Skills, Agent personas, Commands/prompts, References & Hooks; 3 pi-only — a claude-code workspace sees just the 4 shared groups): each opens as a single-select quick screen (`Recommended ★ (n)` / `Everything (m)` / `Customise` / `Skip group`, or the installed-state variants with `Remove some…`), and multi-select drill-ins appear only behind `Customise`, chunked by sub-category (lifecycle phase for Skills, `rw`/`ro` for personas, …) at ≤ 4 options per question. Option titles carry `name ★ [st]` (`ok`/`upd`/`mod`/`cflt`/`gone`/`new`/`—`/`brk`); descriptions carry the purpose plus the state in plain words (`mod` → warn that refreshing overwrites local edits). There is **no pre-checking** — installed state shows as counts on quick screens and words in descriptions; leaving an installed item unselected in a drill-in keeps it as-is. `recommended` adds `★` items on top of what is installed — it never removes; cancel = keep-as-is/skip. `cflt` rows are resolved only by showing the three-way diff and asking per row — never by Express or `Apply updates`. Never offer `setup`, `doctor`, or `guided-workspace-setup` — those are installer-only and live in the source agent-fleet repo.
|
|
14
|
+
|
|
15
|
+
Removal happens **only** on an explicit `Remove some…` multi-select (empty selection = remove nothing), and it is scoped: the screen lists only items whose name is in the agent-fleet inventory **and** that are recorded in `## install-status` (or are symlinks resolving into the source repo). User-authored skills, custom commands, third-party plugins, and unrelated settings/env keys are left untouched and logged as "Skipped — not owned by agent-fleet".
|
|
16
|
+
|
|
17
|
+
**No cross-tool substitution.** Each row is offered only when the source file the chosen agent needs already exists — for `pi`, that means `.pi/prompts/<name>.md`, `.pi/extensions/<name>/`, etc. Never fall back to `.claude/commands/` (or another agent's tree) to satisfy a pi prompt request; items missing their per-agent source are filtered out of the menu entirely.
|
|
18
|
+
|
|
19
|
+
**Personas are generated for non-pi targets.** The personas group lists the full availability roster from `node <source-root>/bin/cli.js transform-persona --list --agent <agent>` (pi-only personas — `bowser`, `orchestrator` — appear only when the agent is `pi`). For `claude-code`/`opencode` the apply step installs personas via `transform-persona --agent <agent> --workspace <workspace> <name…>` — always a generated copy, even in symlink mode — and records the rows with `transformed: true`; status checks diff against the generated output, not the raw canonical source.
|
|
20
|
+
|
|
21
|
+
**pi harness companions.** When the agent is `pi`, installing/refreshing/removing any harness also refreshes its companions — the `justfile` launch recipes, the `team-up`/`coms-net` scripts, the peer/team YAML, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json`. `agent-hub` requires only `damage-control-continue` and `ask-user-remote`; auto-include both. Refresh the `justfile` from the current source (rewriting only the `agent-fleet:harnesses` managed region so user recipes survive) so retired-harness recipes are pruned and new ones added. Treat the retired `damage-control` hard-stop directory as `gone`: remove it only when recorded and unchanged against the recorded snapshot, or when it is a symlink into the source root (including a broken retirement link). Preserve every user-modified or unowned copy.
|
|
22
|
+
|
|
23
|
+
**No mid-apply overwrite prompts.** The `mod` description already warns that refreshing overwrites local edits. The user's selection is the consent; the Step 9 confirmation is the single gate. During apply, refresh selected items unconditionally — never pause to ask "should I overwrite this file?". Genuine errors (permission denied, missing source) still stop and report.
|
|
24
|
+
|
|
25
|
+
Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis (print each draft, then `Accept` / `Edit` / `Skip` per section), and record what was installed in `.ai/agent-fleet-setup.md`. Print the plan as compact action-grouped lines (Add / Refresh / Remove / Keep-count / Records / Method), then confirm with one question whose options are `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel` — write nothing until an Apply is chosen. Then perform the setup, re-scan for any new breakage, and report what changed.
|