@chankov/agent-fleet 0.0.5 → 0.0.6
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/.pi/extensions/agent-fleet-update-check/README.md +4 -4
- package/.pi/extensions/btw/README.md +10 -10
- package/.pi/extensions/btw/index.ts +11 -11
- package/.pi/extensions/chrome-devtools-mcp/README.md +2 -2
- package/.pi/extensions/chrome-devtools-mcp/index.ts +1 -0
- package/.pi/extensions/compact-and-continue/README.md +2 -2
- package/.pi/extensions/pi-voice-stt/README.md +7 -7
- package/.pi/extensions/pi-voice-stt/index.ts +4 -4
- package/.pi/harnesses/agent-hub/README.md +58 -58
- package/.pi/harnesses/agent-hub/backend-policy.js +1 -1
- package/.pi/harnesses/agent-hub/delegate.ts +3 -3
- package/.pi/harnesses/agent-hub/drift-watchdog.js +1 -1
- package/.pi/harnesses/agent-hub/index.ts +248 -248
- package/.pi/harnesses/agent-hub/package.json +1 -1
- package/.pi/harnesses/agent-hub/run-budget.js +1 -1
- package/.pi/harnesses/coms/README.md +2 -2
- package/.pi/harnesses/coms/index.ts +13 -13
- package/.pi/harnesses/coms/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/README.md +9 -9
- package/.pi/harnesses/damage-control-continue/index.ts +11 -11
- package/.pi/harnesses/damage-control-continue/package.json +1 -1
- package/.pi/prompts/{doctor-agent-fleet.md → af-doctor-agent-fleet.md} +1 -1
- package/.pi/prompts/{setup-agent-fleet.md → af-setup-agent-fleet.md} +1 -1
- package/.versions/0.0.6/.claude/commands/build.md +44 -0
- package/.versions/0.0.6/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.6/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.6/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.6/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.6/.claude/commands/plan.md +16 -0
- package/.versions/0.0.6/.claude/commands/prime.md +22 -0
- package/.versions/0.0.6/.claude/commands/review.md +16 -0
- package/.versions/0.0.6/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.6/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.6/.claude/commands/ship.md +72 -0
- package/.versions/0.0.6/.claude/commands/spec.md +15 -0
- package/.versions/0.0.6/.claude/commands/test.md +19 -0
- package/.versions/0.0.6/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.6/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.6/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.6/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.6/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.6/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.6/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.6/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.6/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.6/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.6/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.6/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.6/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.6/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.6/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.6/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.6/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.6/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.6/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.6/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.6/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.6/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.6/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/0.0.6/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.6/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.6/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.6/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.6/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.6/.pi/extensions/package.json +9 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.6/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.6/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.6/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.6/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.6/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.6/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.6/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.6/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.6/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.6/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.6/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.6/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.6/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.6/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.6/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.6/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.6/.pi/prompts/af-build.md +24 -0
- package/.versions/0.0.6/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/0.0.6/.pi/prompts/af-doctor-agent-fleet.md +15 -0
- package/.versions/0.0.6/.pi/prompts/af-plan.md +16 -0
- package/.versions/0.0.6/.pi/prompts/af-review.md +16 -0
- package/.versions/0.0.6/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.6/.pi/prompts/af-setup-agent-fleet.md +27 -0
- package/.versions/0.0.6/.pi/prompts/af-ship.md +17 -0
- package/.versions/0.0.6/.pi/prompts/af-spec.md +15 -0
- package/.versions/0.0.6/.pi/prompts/af-test.md +19 -0
- package/.versions/0.0.6/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.6/.version +1 -0
- package/.versions/0.0.6/agents/architect.md +23 -0
- package/.versions/0.0.6/agents/bowser.md +26 -0
- package/.versions/0.0.6/agents/builder.md +53 -0
- package/.versions/0.0.6/agents/code-reviewer.md +205 -0
- package/.versions/0.0.6/agents/deep-researcher.md +31 -0
- package/.versions/0.0.6/agents/documenter.md +18 -0
- package/.versions/0.0.6/agents/orchestrator.md +54 -0
- package/.versions/0.0.6/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.6/agents/planner.md +69 -0
- package/.versions/0.0.6/agents/releaser.md +24 -0
- package/.versions/0.0.6/agents/researcher.md +28 -0
- package/.versions/0.0.6/agents/security-auditor.md +166 -0
- package/.versions/0.0.6/agents/test-engineer.md +151 -0
- package/.versions/0.0.6/agents/web-debugger.md +42 -0
- package/.versions/0.0.6/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.6/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.6/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.6/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.6/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.6/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.6/docs/coms-hermes-bridge.md +179 -0
- package/.versions/0.0.6/docs/getting-started.md +183 -0
- package/.versions/0.0.6/docs/npm-install.md +337 -0
- package/.versions/0.0.6/docs/opencode-setup.md +249 -0
- package/.versions/0.0.6/docs/pi-extensions.md +293 -0
- package/.versions/0.0.6/docs/pi-setup.md +476 -0
- package/.versions/0.0.6/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.6/hermes/README.md +231 -0
- package/.versions/0.0.6/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.6/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.6/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/.versions/0.0.6/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.6/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.6/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.6/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.6/hooks/hooks.json +14 -0
- package/.versions/0.0.6/hooks/session-start.sh +74 -0
- package/.versions/0.0.6/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.6/justfile +245 -0
- package/.versions/0.0.6/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.6/references/definition-of-done.md +67 -0
- package/.versions/0.0.6/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.6/references/observability-checklist.md +91 -0
- package/.versions/0.0.6/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.6/references/performance-checklist.md +153 -0
- package/.versions/0.0.6/references/prompting-patterns.md +380 -0
- package/.versions/0.0.6/references/security-checklist.md +179 -0
- package/.versions/0.0.6/references/testing-patterns.md +236 -0
- package/.versions/0.0.6/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.6/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.6/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.6/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.6/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.6/scripts/fleet.ts +141 -0
- package/.versions/0.0.6/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.6/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.6/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.6/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.6/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.6/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.6/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.6/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.6/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.6/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.6/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.6/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.6/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.6/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.6/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.6/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.6/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.6/scripts/team-up.ts +351 -0
- package/.versions/0.0.6/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.6/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.6/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.6/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.6/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.6/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.6/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.6/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.6/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.6/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.6/skills/guided-workspace-setup/SKILL.md +544 -0
- package/.versions/0.0.6/skills/guided-workspace-setup/companion-manifest.json +35 -0
- package/.versions/0.0.6/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.6/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.6/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.6/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.6/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.6/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.6/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.6/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.6/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.6/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.6/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.6/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.6/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.6/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.6/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.6/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +6 -0
- package/README.md +24 -23
- package/agents/documenter.md +1 -1
- package/agents/releaser.md +1 -1
- package/bin/cli.js +20 -20
- package/bin/lib/bootstrap.js +16 -16
- package/bin/lib/doctor.js +1 -1
- package/docs/ARCHITECTURE.md +4 -4
- package/docs/agent-fleet-setup.md +11 -11
- package/docs/coms-hermes-bridge.md +8 -8
- package/docs/npm-install.md +21 -21
- package/docs/pi-extensions.md +7 -7
- package/docs/pi-setup.md +51 -47
- package/hermes/README.md +1 -1
- package/package.json +1 -1
- package/references/fleet-coordination-patterns.md +2 -2
- package/skills/browser-testing-with-devtools/SKILL.md +1 -1
- package/skills/compound-learning/SKILL.md +3 -3
- package/skills/guided-workspace-setup/SKILL.md +16 -14
- /package/.pi/prompts/{build.md → af-build.md} +0 -0
- /package/.pi/prompts/{code-simplify.md → af-code-simplify.md} +0 -0
- /package/.pi/prompts/{plan.md → af-plan.md} +0 -0
- /package/.pi/prompts/{review.md → af-review.md} +0 -0
- /package/.pi/prompts/{set-hermes-telegram.md → af-set-hermes-telegram.md} +0 -0
- /package/.pi/prompts/{ship.md → af-ship.md} +0 -0
- /package/.pi/prompts/{spec.md → af-spec.md} +0 -0
- /package/.pi/prompts/{test.md → af-test.md} +0 -0
|
@@ -100,7 +100,7 @@ function refusalTail(mode) {
|
|
|
100
100
|
return "Do NOT retry this call in this turn. Summarize progress so far (including " +
|
|
101
101
|
"unproven assertions and artifact paths), then ask the user whether to continue — " +
|
|
102
102
|
"the next user message starts a fresh budget window. The user can widen budgets " +
|
|
103
|
-
`with /hub-mode (current: ${mode}) or the max-*-per-turn / turn-wall-time-s keys ` +
|
|
103
|
+
`with /af-hub-mode (current: ${mode}) or the max-*-per-turn / turn-wall-time-s keys ` +
|
|
104
104
|
"in .ai/agent-fleet-overrides.md.";
|
|
105
105
|
}
|
|
106
106
|
|
|
@@ -46,7 +46,7 @@ when you are on the herdr backend.
|
|
|
46
46
|
|
|
47
47
|
## Commands & tools
|
|
48
48
|
|
|
49
|
-
- `/coms` — open the coms control surface; `--project <name>` retargets the pool (use `*` for
|
|
49
|
+
- `/af-coms` — open the coms control surface; `--project <name>` retargets the pool (use `*` for
|
|
50
50
|
every project) and `--all` toggles private (`--explicit`) peers into view
|
|
51
51
|
- `coms_list` / `coms_send` / `coms_get` / `coms_await` tools — discover peers and
|
|
52
52
|
exchange messages
|
|
@@ -67,7 +67,7 @@ Standalone `coms-cli` queues are project-scoped under `~/.pi/coms/cli/projects/<
|
|
|
67
67
|
The pool widget defines who you can reach: `coms_list` and `coms_send` resolve targets through one
|
|
68
68
|
`peersInScope()` helper, so a peer is reachable only if it is in the pool. By default the
|
|
69
69
|
pool is your own project and excludes `--explicit` peers. **Widening is a human-only action** — the
|
|
70
|
-
`coms_list` tool cannot widen scope; only `/coms --project` / `/coms --all` can. This prevents an
|
|
70
|
+
`coms_list` tool cannot widen scope; only `/af-coms --project` / `/af-coms --all` can. This prevents an
|
|
71
71
|
agent from messaging a cross-project peer that the widget never showed.
|
|
72
72
|
|
|
73
73
|
## Requires
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
*
|
|
8
8
|
* Phase A (foundation): identity resolution, registry I/O, transport bind/send,
|
|
9
9
|
* connection handlers. Phase B: tools (coms_list/send/get/await), agent_end
|
|
10
|
-
* response capture. Phase C: live pool widget, ping + keepalive cycles, /coms
|
|
10
|
+
* response capture. Phase C: live pool widget, ping + keepalive cycles, /af-coms
|
|
11
11
|
* slash command, clean shutdown lifecycle.
|
|
12
12
|
*
|
|
13
13
|
* Usage: pi -e extensions/coms.ts
|
|
@@ -1279,7 +1279,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
1279
1279
|
// Scoped to the connected pool only (peersInScope): you can reach exactly the
|
|
1280
1280
|
// peers the widget shows. Match by name first (preferred, human-facing), then by
|
|
1281
1281
|
// session_id. A peer outside the current scope is intentionally NOT resolved — the
|
|
1282
|
-
// human must widen scope via /coms --project / --all first. This closes the old
|
|
1282
|
+
// human must widen scope via /af-coms --project / --all first. This closes the old
|
|
1283
1283
|
// cross-project leak where a name match fell through to scanning every project.
|
|
1284
1284
|
const scope = peersInScope();
|
|
1285
1285
|
const byName = scope.find((e) => e.name === target);
|
|
@@ -1295,10 +1295,10 @@ export default function (pi: ExtensionAPI) {
|
|
|
1295
1295
|
description:
|
|
1296
1296
|
"List the peer agents in your current coms pool — the ones shown in the pool widget. Returns " +
|
|
1297
1297
|
"names, models, and live context-window usage. Discovery is scoped to what the human displays " +
|
|
1298
|
-
"via /coms; you CANNOT widen it to other projects or reveal --explicit peers yourself.",
|
|
1298
|
+
"via /af-coms; you CANNOT widen it to other projects or reveal --explicit peers yourself.",
|
|
1299
1299
|
parameters: Type.Object({
|
|
1300
|
-
project: Type.Optional(Type.String({ description: "Narrow to a project WITHIN the current pool scope. Cannot widen beyond what /coms displays — a widening request is ignored." })),
|
|
1301
|
-
include_explicit: Type.Optional(Type.Boolean({ description: "Only narrows: pass false to hide explicit peers. Cannot reveal them unless the human ran /coms --all." })),
|
|
1300
|
+
project: Type.Optional(Type.String({ description: "Narrow to a project WITHIN the current pool scope. Cannot widen beyond what /af-coms displays — a widening request is ignored." })),
|
|
1301
|
+
include_explicit: Type.Optional(Type.Boolean({ description: "Only narrows: pass false to hide explicit peers. Cannot reveal them unless the human ran /af-coms --all." })),
|
|
1302
1302
|
}),
|
|
1303
1303
|
async execute(_callId, params) {
|
|
1304
1304
|
if (!identity) {
|
|
@@ -1308,9 +1308,9 @@ export default function (pi: ExtensionAPI) {
|
|
|
1308
1308
|
};
|
|
1309
1309
|
}
|
|
1310
1310
|
// Clamp discovery to the human-set pool scope (displayProject + includeExplicit,
|
|
1311
|
-
// driven by /coms). The LLM's project/include_explicit may NARROW within that
|
|
1311
|
+
// driven by /af-coms). The LLM's project/include_explicit may NARROW within that
|
|
1312
1312
|
// scope but can never widen it — cross-project or explicit discovery requires a
|
|
1313
|
-
// deliberate /coms --project / --all from the human. So coms_list returns exactly
|
|
1313
|
+
// deliberate /af-coms --project / --all from the human. So coms_list returns exactly
|
|
1314
1314
|
// the pool, the same boundary coms_send enforces.
|
|
1315
1315
|
const scopeProject = displayProject ?? identity.project;
|
|
1316
1316
|
let projects: string[];
|
|
@@ -1322,7 +1322,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
1322
1322
|
if (params.project && params.project !== scopeProject) widened = true;
|
|
1323
1323
|
}
|
|
1324
1324
|
// include_explicit may only narrow (turn OFF); it cannot reveal explicit peers
|
|
1325
|
-
// unless the human already did via /coms --all.
|
|
1325
|
+
// unless the human already did via /af-coms --all.
|
|
1326
1326
|
const includeExp = includeExplicit && params.include_explicit !== false;
|
|
1327
1327
|
if (params.include_explicit === true && !includeExplicit) widened = true;
|
|
1328
1328
|
|
|
@@ -1357,7 +1357,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
1357
1357
|
const notice = widened
|
|
1358
1358
|
? `\n\n(Discovery is scoped to "${scopeProject}"${includeExplicit ? "" : ", explicit peers hidden"}. ` +
|
|
1359
1359
|
`Widening to other projects or revealing --explicit peers is a human action via ` +
|
|
1360
|
-
`/coms --project <name> or /coms --all.)`
|
|
1360
|
+
`/af-coms --project <name> or /af-coms --all.)`
|
|
1361
1361
|
: "";
|
|
1362
1362
|
|
|
1363
1363
|
const lines = agents.length === 0
|
|
@@ -1405,7 +1405,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
1405
1405
|
"Use coms_get (non-blocking) or coms_await (blocking) with the msg_id to retrieve the response. " +
|
|
1406
1406
|
"Throws if the receiver is unreachable or rejects the envelope.",
|
|
1407
1407
|
parameters: Type.Object({
|
|
1408
|
-
target: Type.String({ description: "Peer name (preferred) or session_id — must be a peer currently in your coms pool (shown in the widget). Out-of-pool targets are refused; ask the human to widen scope with /coms --project or /coms --all." }),
|
|
1408
|
+
target: Type.String({ description: "Peer name (preferred) or session_id — must be a peer currently in your coms pool (shown in the widget). Out-of-pool targets are refused; ask the human to widen scope with /af-coms --project or /af-coms --all." }),
|
|
1409
1409
|
prompt: Type.String({ description: "The prompt to send." }),
|
|
1410
1410
|
conversation_id: Type.Optional(Type.String()),
|
|
1411
1411
|
response_schema: Type.Optional(Type.Any({ description: "Optional JSON Schema describing the expected response shape." })),
|
|
@@ -1423,7 +1423,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
1423
1423
|
throw new Error(
|
|
1424
1424
|
`coms: no connected peer "${params.target}" in your pool (project ${scope}). ` +
|
|
1425
1425
|
`Only peers shown in the coms pool are reachable. If you expected this peer, ask the ` +
|
|
1426
|
-
`human to widen scope with /coms --project <name> or /coms --all, then retry.`,
|
|
1426
|
+
`human to widen scope with /af-coms --project <name> or /af-coms --all, then retry.`,
|
|
1427
1427
|
);
|
|
1428
1428
|
}
|
|
1429
1429
|
const hops = currentInbound ? currentInbound.hops + 1 : 0;
|
|
@@ -1690,8 +1690,8 @@ export default function (pi: ExtensionAPI) {
|
|
|
1690
1690
|
}
|
|
1691
1691
|
});
|
|
1692
1692
|
|
|
1693
|
-
// ━━ /coms slash command ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
1694
|
-
pi.registerCommand("coms", {
|
|
1693
|
+
// ━━ /af-coms slash command ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
1694
|
+
pi.registerCommand("af-coms", {
|
|
1695
1695
|
description: "Force-refresh the coms pool widget (or filter with --all / --project <name>)",
|
|
1696
1696
|
handler: async (args, ctx) => {
|
|
1697
1697
|
const trimmed = (args ?? "").trim();
|
|
@@ -37,10 +37,10 @@ They apply to the **path categories only** — `zeroAccessPaths`, `readOnlyPaths
|
|
|
37
37
|
**Pre-authorize** (when you know the agent will need it):
|
|
38
38
|
|
|
39
39
|
```
|
|
40
|
-
/allow .env # exempt for the rest of the session (default)
|
|
41
|
-
/allow .env turn # exempt until the end of the current/next turn
|
|
42
|
-
/allowed # list active exemptions
|
|
43
|
-
/revoke .env # remove an exemption
|
|
40
|
+
/af-allow .env # exempt for the rest of the session (default)
|
|
41
|
+
/af-allow .env turn # exempt until the end of the current/next turn
|
|
42
|
+
/af-allowed # list active exemptions
|
|
43
|
+
/af-revoke .env # remove an exemption
|
|
44
44
|
```
|
|
45
45
|
|
|
46
46
|
**Block-time dialog** (when you forgot): in an interactive session a path block
|
|
@@ -60,7 +60,7 @@ timeout. At most 3 escalations per child run; denials are cached.
|
|
|
60
60
|
|
|
61
61
|
**Shared exemptions file**: agent-hub keeps one session-scoped file
|
|
62
62
|
(`~/.pi/coms/exemptions/<session>.json`, deleted on shutdown) and passes it to
|
|
63
|
-
every spawned child via `AGENT_HUB_EXEMPTIONS_FILE`. `/allow <pattern> session`
|
|
63
|
+
every spawned child via `AGENT_HUB_EXEMPTIONS_FILE`. `/af-allow <pattern> session`
|
|
64
64
|
in the hub lands there, so it covers the whole team. Every native specialist,
|
|
65
65
|
research helper, and nested delegate uses this harness and re-reads the file on
|
|
66
66
|
every block, so mid-session grants reach already-running children. Everything
|
|
@@ -76,9 +76,9 @@ refuses guarded child dispatch rather than launching an unprotected process.
|
|
|
76
76
|
|
|
77
77
|
## Commands & tools
|
|
78
78
|
|
|
79
|
-
- `/allow <pattern> [turn|session]` — exempt a protected path pattern
|
|
80
|
-
- `/allowed` — list active exemptions
|
|
81
|
-
- `/revoke <pattern>` — remove an exemption
|
|
79
|
+
- `/af-allow <pattern> [turn|session]` — exempt a protected path pattern
|
|
80
|
+
- `/af-allowed` — list active exemptions
|
|
81
|
+
- `/af-revoke <pattern>` — remove an exemption
|
|
82
82
|
|
|
83
83
|
Blocking itself runs passively on the `tool_call` event.
|
|
84
84
|
|
|
@@ -111,7 +111,7 @@ pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/agent-hub/
|
|
|
111
111
|
call were stripped (this repo does not ship pi themes).
|
|
112
112
|
- The `find` tool's `pattern` is matched against `zeroAccessPaths`, closing a gap
|
|
113
113
|
where `find` could still locate secret files.
|
|
114
|
-
- Exemption layer added (not in upstream): `/allow`/`/allowed`/`/revoke`,
|
|
114
|
+
- Exemption layer added (not in upstream): `/af-allow`/`/af-allowed`/`/af-revoke`,
|
|
115
115
|
block-time approval dialog, and escalation from headless agent-hub children to
|
|
116
116
|
the dispatcher — see the Exemptions section above. Shared plumbing lives in
|
|
117
117
|
[`../lib/damage-control-shared.ts`](../lib/damage-control-shared.ts).
|
|
@@ -12,8 +12,8 @@
|
|
|
12
12
|
* On top of the rule engine this variant supports runtime EXEMPTIONS for the
|
|
13
13
|
* path categories (zeroAccessPaths / readOnlyPaths / noDeletePaths) — never
|
|
14
14
|
* for the destructive bashToolPatterns:
|
|
15
|
-
* - /allow <pattern> [turn|session] pre-authorizes a protected pattern
|
|
16
|
-
* (/allowed lists, /revoke removes). Session grants are mirrored into the
|
|
15
|
+
* - /af-allow <pattern> [turn|session] pre-authorizes a protected pattern
|
|
16
|
+
* (/af-allowed lists, /af-revoke removes). Session grants are mirrored into the
|
|
17
17
|
* shared exemptions file when agent-hub provides one, so spawned children
|
|
18
18
|
* inherit them.
|
|
19
19
|
* - In interactive sessions a path block opens a dialog (keep blocked /
|
|
@@ -191,8 +191,8 @@ export default function (pi: ExtensionAPI) {
|
|
|
191
191
|
: `🛡️ Damage-Control (continue): ${total} Rules`;
|
|
192
192
|
}
|
|
193
193
|
|
|
194
|
-
pi.registerCommand("allow", {
|
|
195
|
-
description: "Damage-control: exempt a protected path pattern — /allow <pattern> [turn|session]",
|
|
194
|
+
pi.registerCommand("af-allow", {
|
|
195
|
+
description: "Damage-control: exempt a protected path pattern — /af-allow <pattern> [turn|session]",
|
|
196
196
|
handler: async (args, ctx) => {
|
|
197
197
|
const parts = args.trim().split(/\s+/).filter(Boolean);
|
|
198
198
|
let scope: ExemptionScope = "session";
|
|
@@ -203,7 +203,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
203
203
|
}
|
|
204
204
|
const pattern = parts.join(" ");
|
|
205
205
|
if (!pattern) {
|
|
206
|
-
ctx.ui.notify("Usage: /allow <pattern> [turn|session] — e.g. /allow .env turn", "warning");
|
|
206
|
+
ctx.ui.notify("Usage: /af-allow <pattern> [turn|session] — e.g. /af-allow .env turn", "warning");
|
|
207
207
|
return;
|
|
208
208
|
}
|
|
209
209
|
const already = activeExemptions().some((e) => e.pattern === pattern && (e.scope === scope || e.scope === "session"));
|
|
@@ -217,7 +217,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
217
217
|
},
|
|
218
218
|
});
|
|
219
219
|
|
|
220
|
-
pi.registerCommand("allowed", {
|
|
220
|
+
pi.registerCommand("af-allowed", {
|
|
221
221
|
description: "Damage-control: list active exemptions",
|
|
222
222
|
handler: async (_args, ctx) => {
|
|
223
223
|
const lines: string[] = [];
|
|
@@ -230,12 +230,12 @@ export default function (pi: ExtensionAPI) {
|
|
|
230
230
|
},
|
|
231
231
|
});
|
|
232
232
|
|
|
233
|
-
pi.registerCommand("revoke", {
|
|
234
|
-
description: "Damage-control: revoke an exemption — /revoke <pattern>",
|
|
233
|
+
pi.registerCommand("af-revoke", {
|
|
234
|
+
description: "Damage-control: revoke an exemption — /af-revoke <pattern>",
|
|
235
235
|
handler: async (args, ctx) => {
|
|
236
236
|
const pattern = args.trim();
|
|
237
237
|
if (!pattern) {
|
|
238
|
-
ctx.ui.notify("Usage: /revoke <pattern>", "warning");
|
|
238
|
+
ctx.ui.notify("Usage: /af-revoke <pattern>", "warning");
|
|
239
239
|
return;
|
|
240
240
|
}
|
|
241
241
|
let removed = false;
|
|
@@ -458,7 +458,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
458
458
|
}
|
|
459
459
|
const note = choice === KEEP
|
|
460
460
|
? `The user reviewed this call and kept the block in place.`
|
|
461
|
-
: `The user did not answer the approval dialog in time (auto-kept blocked). They can pre-authorize with /allow ${matchedPattern} [turn|session].`;
|
|
461
|
+
: `The user did not answer the approval dialog in time (auto-kept blocked). They can pre-authorize with /af-allow ${matchedPattern} [turn|session].`;
|
|
462
462
|
if (choice === KEEP) deniedThisTurn.add(matchedPattern);
|
|
463
463
|
ctx.ui.setStatus("damage-control", `⚠️ Last Violation: ${violationReason.slice(0, 30)}...`);
|
|
464
464
|
pi.appendEntry("damage-control-log", { tool: event.toolName, input: event.input, rule: violationReason, action: choice === KEEP ? "blocked_by_user" : "blocked_prompt_timeout" });
|
|
@@ -525,7 +525,7 @@ export default function (pi: ExtensionAPI) {
|
|
|
525
525
|
}
|
|
526
526
|
} else {
|
|
527
527
|
const note = matchedPattern
|
|
528
|
-
? `The user can pre-authorize this path with /allow ${matchedPattern} [turn|session] in a damage-control-continue session.`
|
|
528
|
+
? `The user can pre-authorize this path with /af-allow ${matchedPattern} [turn|session] in a damage-control-continue session.`
|
|
529
529
|
: undefined;
|
|
530
530
|
ctx.ui.notify(`🛑 Damage-Control: Blocked ${event.toolName} (${violationReason}) — agent will adapt and continue.`);
|
|
531
531
|
ctx.ui.setStatus("damage-control", `⚠️ Last Violation: ${violationReason.slice(0, 30)}...`);
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
|
|
3
3
|
---
|
|
4
4
|
|
|
5
|
-
Load and follow Step 5 (Doctor preflight) of the `guided-workspace-setup` skill — 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.
|
|
5
|
+
Load and follow Step 5 (Doctor preflight) of the `guided-workspace-setup` skill — without running the rest of the install flow. Use this when the user wants the repair pass on its own; the full `/af-setup-agent-fleet` flow runs the same scan automatically as soon as it detects prior install state.
|
|
6
6
|
|
|
7
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
8
|
|
|
@@ -8,7 +8,7 @@ Run the guided install for a target workspace. If the user passed a workspace pa
|
|
|
8
8
|
|
|
9
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
10
|
|
|
11
|
-
**Bootstrap `pi-ask-user` first (Step 5b).** Before the install menu, check whether the `pi-ask-user` interaction package is available (bundled by `@chankov/agent-fleet`, recorded as a project package, or global). If it is missing, offer to install it project-scoped (`pi install -l npm:pi-ask-user`), record it as an external/project pi package, then **stop the pass** and ask the user to reload pi and re-run `/setup-agent-fleet`. The tool only becomes callable after reload, and on the re-run the menu uses its native multi-select widget. Only fall back to a text menu in this pass if the user *declines* the bootstrap.
|
|
11
|
+
**Bootstrap `pi-ask-user` first (Step 5b).** Before the install menu, check whether the `pi-ask-user` interaction package is available (bundled by `@chankov/agent-fleet`, recorded as a project package, or global). If it is missing, offer to install it project-scoped (`pi install -l npm:pi-ask-user`), record it as an external/project pi package, then **stop the pass** and ask the user to reload pi and re-run `/af-setup-agent-fleet`. The tool only becomes callable after reload, and on the re-run the menu uses its native multi-select widget. Only fall back to a text menu in this pass if the user *declines* the bootstrap.
|
|
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
|
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:incremental-implementation skill alongside agent-fleet:test-driven-development.
|
|
6
|
+
|
|
7
|
+
## Modes
|
|
8
|
+
|
|
9
|
+
- **`/build`** — implement the *next* pending task, then stop (careful, one slice at a time).
|
|
10
|
+
- **`/build auto`** — generate the plan if needed, get a single approval, then implement *every* task without stopping between them.
|
|
11
|
+
|
|
12
|
+
`$ARGUMENTS` selects the mode. Treat `auto` (canonical) or `all` as autonomous mode; anything else (or empty) is the default single-task mode. Note: autonomous mode is not faster *per task* — it runs the same test-driven loop — it only removes the human stepping *between* tasks.
|
|
13
|
+
|
|
14
|
+
## Default: one task
|
|
15
|
+
|
|
16
|
+
Pick the next pending task from the plan. Then:
|
|
17
|
+
|
|
18
|
+
1. Read the task's acceptance criteria
|
|
19
|
+
2. Load relevant context (existing code, patterns, types)
|
|
20
|
+
3. Write a failing test for the expected behavior (RED)
|
|
21
|
+
4. Implement the minimum code to pass the test (GREEN)
|
|
22
|
+
5. Run the full test suite to check for regressions
|
|
23
|
+
6. Run the build to verify compilation
|
|
24
|
+
7. Commit with a descriptive message
|
|
25
|
+
8. Mark the task complete and stop
|
|
26
|
+
|
|
27
|
+
## Autonomous: the whole plan (`/build auto`)
|
|
28
|
+
|
|
29
|
+
Use this once a spec exists and you want to collapse plan + build into one run. It removes the manual stepping between tasks — **not** the verification. Every task still earns a passing test and its own commit.
|
|
30
|
+
|
|
31
|
+
1. **Require a spec.** Look only for a spec at a known path: `SPEC.md` at the repo root, `docs/SPEC.md`, or a file under `spec/`. A README or arbitrary doc does **not** count. If none exists, stop and tell the user to run `/spec` first — do not invent requirements.
|
|
32
|
+
2. **Establish a clean baseline.** Run `git status --porcelain`. If there are uncommitted changes outside the expected planning artifacts (`SPEC.md`, `docs/SPEC.md`, `spec/*`, `tasks/plan.md`, `tasks/todo.md`), stop and ask the user to commit, stash, or confirm how to handle them. Autonomous per-task commits must not absorb unrelated local work, or the clean-rollback guarantee breaks.
|
|
33
|
+
3. **Plan if needed.** If there is no `tasks/plan.md`, invoke agent-fleet:planning-and-task-breakdown to generate one.
|
|
34
|
+
4. **Single checkpoint.** Present the full plan and wait for an unambiguous affirmative (e.g. "approve", "go", "yes"). Treat hedged responses ("looks reasonable", "I guess") as **not** approved. This is the only human gate — after approval, run autonomously. If you generated `tasks/plan.md`, commit it as a single preparatory commit now so it doesn't bleed into the first task's commit.
|
|
35
|
+
5. **Execute every task in dependency order.** Use each task's declared dependencies; if they aren't explicit, execute in the order the plan lists them. For each task, run the full default loop above (RED → GREEN → regression → build → commit → mark complete). Stage only the files that task touched plus its task-status update — never `git add -A` blindly — and make one commit per task so any point is a clean rollback.
|
|
36
|
+
6. **Stop and ask the user** (do not push through) when:
|
|
37
|
+
- a test can't be made to pass or the build breaks without an obvious fix → follow agent-fleet:debugging-and-error-recovery
|
|
38
|
+
- the spec is ambiguous, or a task needs a decision the spec doesn't cover
|
|
39
|
+
- a task is high-risk or irreversible — auth/permission changes, destructive data migrations, payments, deletions, deploys, anything touching secrets, **or anything you can't undo with `git revert`** → follow agent-fleet:doubt-driven-development and get explicit sign-off before continuing
|
|
40
|
+
|
|
41
|
+
After the user resolves a blocker, they re-invoke `/build auto` — it resumes from the next pending task.
|
|
42
|
+
7. **Summarize at the end:** tasks completed, tests added, commits made, and anything skipped, flagged, or left for the user.
|
|
43
|
+
|
|
44
|
+
If any step fails, follow the agent-fleet:debugging-and-error-recovery skill.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Simplify code for clarity and maintainability — reduce complexity without changing behavior
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:code-simplification skill.
|
|
6
|
+
|
|
7
|
+
Simplify recently changed code (or the specified scope) while preserving exact behavior:
|
|
8
|
+
|
|
9
|
+
1. Read CLAUDE.md and study project conventions
|
|
10
|
+
2. Identify the target code — recent changes unless a broader scope is specified
|
|
11
|
+
3. Understand the code's purpose, callers, edge cases, and test coverage before touching it
|
|
12
|
+
4. Scan for simplification opportunities:
|
|
13
|
+
- Deep nesting → guard clauses or extracted helpers
|
|
14
|
+
- Long functions → split by responsibility
|
|
15
|
+
- Nested ternaries → if/else or switch
|
|
16
|
+
- Generic names → descriptive names
|
|
17
|
+
- Duplicated logic → shared functions
|
|
18
|
+
- Dead code → remove after confirming
|
|
19
|
+
5. Apply each simplification incrementally — run tests after each change
|
|
20
|
+
6. Verify all tests pass, the build succeeds, and the diff is clean
|
|
21
|
+
|
|
22
|
+
If tests fail after a simplification, revert that change and reconsider. Use `code-review-and-quality` to review the result.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Design and write a new agent persona (agents/), workflow skill (skills/), or pi harness (.pi/harnesses/)
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:designing-agents skill.
|
|
6
|
+
|
|
7
|
+
Begin by understanding what the user wants to author:
|
|
8
|
+
1. Is this a **persona** (a role/lens the agent adopts, e.g. a reviewer or auditor), a **skill** (a repeatable workflow with gated steps and verification), or a **pi harness** (a TypeScript pi extension that reshapes the session — footer, tool-call gate, new command, or orchestrator)?
|
|
9
|
+
2. The one-sentence purpose and when it should be invoked
|
|
10
|
+
3. The framework or steps — dimensions evaluated (persona), ordered workflow (skill), or session surface and events hooked (harness)
|
|
11
|
+
4. Explicit non-goals and scope limits
|
|
12
|
+
5. Output shape — what a typical invocation should produce
|
|
13
|
+
|
|
14
|
+
Then scan the target location (`agents/`, `skills/`, or `.pi/harnesses/`) for overlap, draft the artifact using the matching template — four-block persona structure, the section order from `docs/skill-anatomy.md`, or the harness pattern in `skills/designing-agents/pi-harness-authoring.md` — verify the draft against `references/prompting-patterns.md`, and confirm with the user before writing the file(s).
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the Doctor scan from the `agent-fleet:guided-workspace-setup` skill — Step 5 (the preflight scan) — without running the rest of the install flow. Use this when the user wants the repair pass on its own; the full `/setup-agent-fleet` flow runs the same scan automatically as soon as it detects prior install state.
|
|
6
|
+
|
|
7
|
+
Walk every install-target directory the chosen coding agent uses (`agents/`, `.claude/agents/`, `.opencode/agent/` (+ legacy `.opencode/agents/`), `.pi/agents/`, `.claude/skills/`, `.opencode/skills/`, `.pi/skills/`, `.agents/skills`, `.claude/commands/`, `.opencode/commands/`, `.pi/prompts/`, `.claude/references/`, `.claude/hooks/`). For each broken symlink, resolve where it pointed, look for a canonical replacement in the source `agents/` and `skills/` trees, and offer to repair or delete (persona links under `.claude/agents/` and `.opencode/agent(s)/` are repaired by regenerating a transformed copy via `transform-persona`, not by re-symlinking the raw source). Common stale names from the pre-merge persona layout: `reviewer` → `code-reviewer`, `red-team` → `security-auditor`.
|
|
8
|
+
|
|
9
|
+
Also flag and offer to rewrite any remaining YAML configs (`teams.yaml`, `peers.yaml`, etc.) that still reference removed persona names.
|
|
10
|
+
|
|
11
|
+
Also flag malformed peer entries in `.pi/agents/peers.yaml`: field lines (`persona:`, `model:`, ...) that sit under a team heading before any `- name: ...` list item. The team-up launcher's minimal parser silently drops such lines, so the peer never spawns and nothing errors — the usual cause is a `- name:` line lost in an edit. These findings are advisory only: report them with the missing `- name: <peer>` suggestion, never rewrite the file.
|
|
12
|
+
|
|
13
|
+
Also validate `.ai/agent-fleet-overrides.md` when it exists, against the schema in `docs/agent-fleet-setup.md`: unknown sections, unknown keys in known sections, invalid values for the mechanically parsed `agent-hub` keys, missing `rules:` folders and `docs:` entry points, and `## env` `required:` names that are neither set nor declared in the root `.env`. These findings are advisory only — report them with fix "edit by hand", never edit the overrides file.
|
|
14
|
+
|
|
15
|
+
Present the findings per the skill's Step 1 interaction contract: print a short text summary (counts per kind, advisory findings as report-only text), then ask one `AskUserQuestion` multi-select — *"Which fixes should I apply now?"* — each option titled `<path> — <issue>` with the proposed fix as its description, chunked at ≤ 4 options per question; an empty selection applies nothing.
|
|
16
|
+
|
|
17
|
+
Never overwrite a regular file — only act on symlinks whose target is missing. Report `repaired`, `deleted`, and `skipped` counts, and append a `## doctor-runs` line to `.ai/agent-fleet-setup.md` with the date, agent, phase (`standalone`), and counts.
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Orchestrate a config-defined team of subagents — route planner/builder (and more) as a runtime roster, handling NEEDS_RESEARCH and PLAN_FILE handoffs
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
You are the **orchestrator**. The primary agent drives a team of installed Claude Code
|
|
6
|
+
subagents to deliver the task in `$ARGUMENTS`. Subagents cannot nest — **all dispatching is
|
|
7
|
+
yours**.
|
|
8
|
+
|
|
9
|
+
## Roles
|
|
10
|
+
|
|
11
|
+
| Role | What it does |
|
|
12
|
+
|---|---|
|
|
13
|
+
| `researcher` | Always-available read-only recon. Cites `file:line`. Never edits. |
|
|
14
|
+
| `planner` | Writes a plan doc only; ends with `PLAN_FILE: <path>` or pauses on `NEEDS_RESEARCH:`. |
|
|
15
|
+
| `builder` | Implements in small increments; may pause on `NEEDS_RESEARCH:`. |
|
|
16
|
+
| `plan-reviewer` / `code-reviewer` | Read-only; their whole result is findings (no handoff marker). |
|
|
17
|
+
|
|
18
|
+
## Step 0 — Resolve the team
|
|
19
|
+
|
|
20
|
+
1. Read `.claude/orchestrate-teams.yaml` (a map of team-name → ordered persona list).
|
|
21
|
+
2. Resolve team + task from `$ARGUMENTS`:
|
|
22
|
+
- Treat the **first token** as a team name **only** when it is a bare single word that
|
|
23
|
+
exactly matches a config key **and** is followed by the rest of the task. To force a
|
|
24
|
+
team explicitly, the user writes `/orchestrate team=<name> <task>`. Otherwise the
|
|
25
|
+
team is the first key (`default`) and all of `$ARGUMENTS` is the task.
|
|
26
|
+
- **Fallbacks:** if the config is **absent / empty / fails to parse**, fall back to the
|
|
27
|
+
built-in `planner` + `builder` default and **say which fallback fired** (don't proceed
|
|
28
|
+
silently). If a named team is requested but not found, list the available team keys and
|
|
29
|
+
ask rather than guessing.
|
|
30
|
+
3. **Validate personas:** each persona in the resolved team must exist in `.claude/agents/`.
|
|
31
|
+
Skip-with-warning any that don't. If every persona is missing, fall back to the built-in
|
|
32
|
+
default.
|
|
33
|
+
4. List the resolved team back to the user before dispatching.
|
|
34
|
+
|
|
35
|
+
`researcher` / `deep-researcher` are **always available** even when not listed in the team.
|
|
36
|
+
|
|
37
|
+
## Step 1 — The team is a roster, not a fixed pipeline
|
|
38
|
+
|
|
39
|
+
The persona list is the set of specialists you may route to; **you decide the order at
|
|
40
|
+
runtime from the task state** (the listed order is only a sensible starting default). So:
|
|
41
|
+
|
|
42
|
+
- **Skip `planner`** when a usable plan already exists (the user passed a `PLAN_FILE` or
|
|
43
|
+
pointed at one) — go straight to `builder`.
|
|
44
|
+
- **Re-dispatch `researcher` at any point** — after `planner`, mid-build — whenever a
|
|
45
|
+
specialist needs a fact checked, not only as a first step.
|
|
46
|
+
- **Loop back to `planner`** if `builder` surfaces that the plan is wrong.
|
|
47
|
+
|
|
48
|
+
Do **not** enforce a hard `researcher → planner → builder` sequence.
|
|
49
|
+
|
|
50
|
+
## The Verification Contract (applies across every step)
|
|
51
|
+
|
|
52
|
+
Read `skills/orchestration-verification/SKILL.md` before non-trivial work and hold its
|
|
53
|
+
contract for the whole run. Subagents here cannot persist a shared ledger, so **you** keep
|
|
54
|
+
the acceptance assertions in your own working notes and refuse "done" until each is proven.
|
|
55
|
+
|
|
56
|
+
- **Build the assertions first.** Before dispatching `builder` for any non-trivial task,
|
|
57
|
+
convert the request into numbered, tagged assertions (`test` | `runtime-ui` | `code-grep`
|
|
58
|
+
| `manual`, one checkable pass condition each). Pass the relevant assertions **verbatim**
|
|
59
|
+
into each dispatch and advance only on assertions that come back *proven with named
|
|
60
|
+
evidence* — propagation in prose is not verification.
|
|
61
|
+
- **Inventory parity for "behave like X" requests.** When the request is "make X behave like
|
|
62
|
+
existing Y", dispatch `researcher` / `deep-researcher` **first** to enumerate every site
|
|
63
|
+
where the exemplar is special-cased (flags, branches, display, validation, translations,
|
|
64
|
+
fixtures, tests), and turn each site into an assertion covering the *whole* set — otherwise
|
|
65
|
+
the exemplar ships and its siblings are missed.
|
|
66
|
+
- **Require runtime proof for UI assertions.** A `runtime-ui` assertion (visibility,
|
|
67
|
+
placement, "appears in the table") is closed only by an actual runtime observation via
|
|
68
|
+
`browser-testing-with-devtools`, never a static review.
|
|
69
|
+
- **Accept assertion status, not verdicts.** Treat specialist returns as `assertions_proven`
|
|
70
|
+
/ `assertions_unproven` / `assertions_failed`; demote any "approved" claim with no named
|
|
71
|
+
evidence to unproven and re-dispatch it.
|
|
72
|
+
- **Reset on "wrong again".** When the user reports a delivered requirement is wrong again,
|
|
73
|
+
treat prior summaries as suspect, rebuild the affected assertions from the **latest**
|
|
74
|
+
correction (re-running the parity inventory for "behave like" cases), then re-dispatch.
|
|
75
|
+
|
|
76
|
+
## Step 2 — Route to specialists, honouring handoff markers
|
|
77
|
+
|
|
78
|
+
State the chosen next step (and why) before each dispatch, so routing is visible.
|
|
79
|
+
|
|
80
|
+
- `planner` → read its `PLAN_FILE: <path>` and load the plan.
|
|
81
|
+
- `builder` → loop over the plan's `## Task List`, **one task per dispatch**, checking each
|
|
82
|
+
task's acceptance criteria **and the relevant acceptance assertions** before moving on.
|
|
83
|
+
- **Marker-less personas** (`plan-reviewer` / `code-reviewer`) emit no handoff marker —
|
|
84
|
+
their returned report **is** the result; "done" = the report came back, nothing to wait
|
|
85
|
+
for. Fold findings forward; if a `code-reviewer` raised must-fix issues, loop back to
|
|
86
|
+
`builder`.
|
|
87
|
+
|
|
88
|
+
## Step 3 — NEEDS_RESEARCH dispatch (core)
|
|
89
|
+
|
|
90
|
+
Whenever any persona's result contains one or more `NEEDS_RESEARCH: <question>` lines:
|
|
91
|
+
|
|
92
|
+
1. Pause that track.
|
|
93
|
+
2. Dispatch `researcher` (read-only) once per question — in parallel when independent.
|
|
94
|
+
3. Collect the findings.
|
|
95
|
+
4. Resume the paused persona by re-dispatching it with the **original task plus the
|
|
96
|
+
findings inlined**.
|
|
97
|
+
|
|
98
|
+
**Never** answer a `NEEDS_RESEARCH` by guessing.
|
|
99
|
+
|
|
100
|
+
## Step 4 — Reviewer only if present
|
|
101
|
+
|
|
102
|
+
The `default` roster has **no reviewer**. After the final builder task's acceptance criteria
|
|
103
|
+
pass, report completion and **state explicitly that review/verification was not run** and
|
|
104
|
+
which acceptance assertions therefore remain unproven (the user can pick the `full` team or
|
|
105
|
+
run `/review`). When the active team *does* include a reviewer, run it as a normal step and
|
|
106
|
+
require it to report parity across sibling cases, not just the exemplar.
|
|
107
|
+
|
|
108
|
+
## Step 5 — Report
|
|
109
|
+
|
|
110
|
+
Report crisply: **active team**, what changed, which acceptance assertions are **proven (with
|
|
111
|
+
evidence)**, which remain **unproven or failed**, and what's next. Never report "done" while a
|
|
112
|
+
relevant assertion is unproven.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Break work into small verifiable tasks with acceptance criteria and dependency ordering
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:planning-and-task-breakdown skill.
|
|
6
|
+
|
|
7
|
+
Read the existing spec (SPEC.md or equivalent) and the relevant codebase sections. Then:
|
|
8
|
+
|
|
9
|
+
1. Enter plan mode — read only, no code changes
|
|
10
|
+
2. Identify the dependency graph between components
|
|
11
|
+
3. Slice work vertically (one complete path per task, not horizontal layers)
|
|
12
|
+
4. Write tasks with acceptance criteria and verification steps
|
|
13
|
+
5. Add checkpoints between phases
|
|
14
|
+
6. Present the plan for human review
|
|
15
|
+
|
|
16
|
+
Save the plan to the location the `planning-and-task-breakdown` skill defines (default `docs/plans/{area}/PLAN-{prd-name}-{phase}.md`, with the task list embedded — no separate todo file; overridable per project via `.ai/agent-fleet-overrides.md`). Match the project's existing `docs`/`Docs` capitalization.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Load foundational context for the agent-fleet repository
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Purpose
|
|
6
|
+
|
|
7
|
+
Orient yourself in **agent-fleet** — a collection of production-grade engineering skills
|
|
8
|
+
for AI coding agents, plus pi extensions, specialist agent personas, and lifecycle
|
|
9
|
+
commands that map to the software development lifecycle.
|
|
10
|
+
|
|
11
|
+
## Workflow
|
|
12
|
+
|
|
13
|
+
1. Run `git ls-files` to see the full project file tree
|
|
14
|
+
2. Read `README.md` and `CLAUDE.md` for the project overview and conventions
|
|
15
|
+
3. Read `docs/skill-anatomy.md` to learn the required skill format
|
|
16
|
+
4. Skim `skills/*/SKILL.md` — the core skills, grouped by lifecycle phase
|
|
17
|
+
(Define → Plan → Build → Verify → Review → Ship)
|
|
18
|
+
5. Read `agents/*.md` — the specialist review personas
|
|
19
|
+
6. Read `docs/pi-extensions.md`, `.pi/extensions/*/README.md` (always-on utilities), and `.pi/harnesses/*/README.md` (selectable session harnesses)
|
|
20
|
+
7. Summarize your understanding: purpose, structure, key files, and entry points
|
|
21
|
+
|
|
22
|
+
Do this directly — read the files yourself rather than delegating to subagents.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Conduct a five-axis code review — correctness, readability, architecture, security, performance
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Invoke the agent-fleet:code-review-and-quality skill.
|
|
6
|
+
|
|
7
|
+
Review the current changes (staged or recent commits) across all five axes:
|
|
8
|
+
|
|
9
|
+
1. **Correctness** — Does it match the spec? Edge cases handled? Tests adequate?
|
|
10
|
+
2. **Readability** — Clear names? Straightforward logic? Well-organized?
|
|
11
|
+
3. **Architecture** — Follows existing patterns? Clean boundaries? Right abstraction level?
|
|
12
|
+
4. **Security** — Input validated? Secrets safe? Auth checked? (Use security-and-hardening skill)
|
|
13
|
+
5. **Performance** — No N+1 queries? No unbounded ops? (Use performance-optimization skill)
|
|
14
|
+
|
|
15
|
+
Categorize findings as Critical, Important, or Suggestion.
|
|
16
|
+
Output a structured review with specific file:line references and fix recommendations.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Install/status the Hermes liaison or turn its Telegram ask_user bridge on/off
|
|
3
|
+
argument-hint: "<install|status|on|off> [telegram-id] [--profile NAME] [--force] [--restart]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Run the deterministic Agent Fleet controller with the arguments from `$ARGUMENTS`. Supported forms are:
|
|
7
|
+
|
|
8
|
+
```text
|
|
9
|
+
set-hermes-telegram install [--profile NAME] [--force] [--restart]
|
|
10
|
+
set-hermes-telegram status [--profile NAME]
|
|
11
|
+
set-hermes-telegram on <telegram-id[:topic-id]> [--profile NAME]
|
|
12
|
+
set-hermes-telegram off <telegram-id[:topic-id]> [--profile NAME]
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
Use `node bin/cli.js set-hermes-telegram ...` when the checkout-local CLI exists; otherwise use `npx --no-install agent-fleet set-hermes-telegram ...`. Pass parsed values as separately quoted shell arguments. If neither CLI exists, report that Agent Fleet must be installed or updated. Do not reproduce installation or Herdr lifecycle with ad-hoc commands, do not bypass a `--force` refusal, and do not send a test Telegram message. Return the controller output verbatim.
|
|
@@ -0,0 +1,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.
|