@chankov/agent-fleet 0.0.3 → 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/setup-agent-fleet.md +1 -1
- package/.opencode/commands/af-setup-agent-fleet.md +1 -1
- package/.pi/harnesses/agent-hub/README.md +199 -16
- 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 +1033 -242
- 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-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/coms/README.md +10 -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/setup-agent-fleet.md +1 -1
- 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 +3 -3
- 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/test-engineer.md +11 -4
- package/bin/lib/validate-overrides.js +19 -0
- package/bin/sync-harness-versions.js +94 -0
- package/docs/ARCHITECTURE.md +46 -1
- package/docs/agent-fleet-setup.md +10 -0
- package/docs/pi-extensions.md +49 -14
- package/docs/pi-setup.md +10 -4
- package/hermes/README.md +180 -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/justfile +6 -10
- package/package.json +9 -4
- package/scripts/lib/fake-herdr-server.ts +88 -0
- 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/skills/designing-agents/SKILL.md +2 -2
- package/skills/designing-agents/pi-harness-authoring.md +26 -13
- package/skills/guided-workspace-setup/SKILL.md +11 -8
- package/.pi/harnesses/damage-control/README.md +0 -65
- package/.pi/harnesses/damage-control/index.ts +0 -250
|
@@ -0,0 +1,288 @@
|
|
|
1
|
+
// .pi/harnesses/lib/herdr-presence.ts
|
|
2
|
+
//
|
|
3
|
+
// The herdr presence backend for the coms layer (used by both the standalone
|
|
4
|
+
// coms harness and the copy embedded in agent-hub). Two halves:
|
|
5
|
+
//
|
|
6
|
+
// - HerdrPresence — reports THIS agent's state into its pane
|
|
7
|
+
// (pane.report_agent) so the herdr sidebar shows live pi agent states.
|
|
8
|
+
// - HerdrAgentWatch — watches OTHER agents via agent.list +
|
|
9
|
+
// events.subscribe (push, no polling): global pane.created/closed/exited
|
|
10
|
+
// plus a per-pane agent_status_changed subscription for every tracked
|
|
11
|
+
// pane (herdr has no wildcard for that topic — spike finding). When the
|
|
12
|
+
// tracked pane set changes, the stream is torn down and resubscribed.
|
|
13
|
+
//
|
|
14
|
+
// Wire constraint baked in (measured live, herdr 0.7.1): `custom_status` is
|
|
15
|
+
// truncated to 32 chars by the server — no JSON fits. formatPeerStatus()
|
|
16
|
+
// therefore emits `<name> <pct>% q<depth>` with the coms peer NAME FIRST, so
|
|
17
|
+
// watchers can join a herdr pane back to the registry entry that carries the
|
|
18
|
+
// full agent card. parsePeerName() is the inverse.
|
|
19
|
+
//
|
|
20
|
+
// Pure module: no pi imports; erasable-TS; testable under node --test.
|
|
21
|
+
|
|
22
|
+
import {
|
|
23
|
+
herdr,
|
|
24
|
+
herdrAvailable,
|
|
25
|
+
subscribe,
|
|
26
|
+
type HerdrClientOptions,
|
|
27
|
+
type SubscribeHandle,
|
|
28
|
+
type Subscription,
|
|
29
|
+
} from "./herdr-client.ts";
|
|
30
|
+
|
|
31
|
+
export const CUSTOM_STATUS_MAX = 32;
|
|
32
|
+
|
|
33
|
+
// HERDR_ENV=1 + HERDR_PANE_ID mark a process running inside a herdr pane.
|
|
34
|
+
export function herdrPaneId(env: NodeJS.ProcessEnv = process.env): string | null {
|
|
35
|
+
if (env.HERDR_ENV !== "1") return null;
|
|
36
|
+
return env.HERDR_PANE_ID || null;
|
|
37
|
+
}
|
|
38
|
+
|
|
39
|
+
// True when this process should use the herdr presence backend: inside a
|
|
40
|
+
// herdr pane AND the server answers ping.
|
|
41
|
+
export async function herdrPresenceAvailable(
|
|
42
|
+
opts: HerdrClientOptions = {},
|
|
43
|
+
env: NodeJS.ProcessEnv = process.env,
|
|
44
|
+
): Promise<boolean> {
|
|
45
|
+
if (!herdrPaneId(env)) return false;
|
|
46
|
+
return (await herdrAvailable(opts)) !== null;
|
|
47
|
+
}
|
|
48
|
+
|
|
49
|
+
// `<name> <pct>% q<depth>` truncated to the 32-char server cap, name first.
|
|
50
|
+
export function formatPeerStatus(name: string, contextUsedPct: number, queueDepth: number): string {
|
|
51
|
+
const s = `${name} ${Math.round(contextUsedPct)}% q${queueDepth}`;
|
|
52
|
+
return s.length <= CUSTOM_STATUS_MAX ? s : s.slice(0, CUSTOM_STATUS_MAX);
|
|
53
|
+
}
|
|
54
|
+
|
|
55
|
+
// Inverse of formatPeerStatus: the peer name is everything before the last
|
|
56
|
+
// ` <pct>% q<n>` tail (tolerates a name that was itself truncated).
|
|
57
|
+
export function parsePeerName(customStatus: string | undefined | null): string | null {
|
|
58
|
+
if (!customStatus) return null;
|
|
59
|
+
const m = customStatus.match(/^(.*?)\s+\d+%\s+q\d*$/);
|
|
60
|
+
const name = (m ? m[1] : customStatus).trim();
|
|
61
|
+
return name || null;
|
|
62
|
+
}
|
|
63
|
+
|
|
64
|
+
export type PresenceState = "idle" | "working" | "blocked" | "unknown";
|
|
65
|
+
|
|
66
|
+
export interface HerdrPresenceOptions extends HerdrClientOptions {
|
|
67
|
+
paneId: string;
|
|
68
|
+
// Identity herdr uses to arbitrate reporting authority (required by the
|
|
69
|
+
// API). Convention: `coms:<session_id>`.
|
|
70
|
+
source: string;
|
|
71
|
+
// Detected-agent label shown in the sidebar; pi peers report "pi".
|
|
72
|
+
agentLabel?: string;
|
|
73
|
+
}
|
|
74
|
+
|
|
75
|
+
// Reports this agent's state into its herdr pane. All calls are best-effort:
|
|
76
|
+
// presence must never break the session, so errors resolve false.
|
|
77
|
+
//
|
|
78
|
+
// Two wire calls per report (both idempotent): pane.report_agent carries the
|
|
79
|
+
// state and covers panes herdr's built-in detection does NOT recognize; for
|
|
80
|
+
// recognized panes (pi has a detection manifest) that call is accepted but
|
|
81
|
+
// IGNORED — detection holds agent authority — so pane.report_metadata carries
|
|
82
|
+
// the custom_status annotation that detection cannot provide. Measured live
|
|
83
|
+
// on herdr 0.7.1; see docs/plans/herdr/spike-notes.md.
|
|
84
|
+
export class HerdrPresence {
|
|
85
|
+
private opts: HerdrPresenceOptions;
|
|
86
|
+
|
|
87
|
+
constructor(opts: HerdrPresenceOptions) {
|
|
88
|
+
this.opts = opts;
|
|
89
|
+
}
|
|
90
|
+
|
|
91
|
+
async report(state: PresenceState, customStatus: string): Promise<boolean> {
|
|
92
|
+
const status = customStatus.slice(0, CUSTOM_STATUS_MAX);
|
|
93
|
+
const agent = this.opts.agentLabel ?? "pi";
|
|
94
|
+
let ok = false;
|
|
95
|
+
try {
|
|
96
|
+
await herdr.paneReportAgent(
|
|
97
|
+
{ pane_id: this.opts.paneId, source: this.opts.source, agent, state, custom_status: status },
|
|
98
|
+
this.opts,
|
|
99
|
+
);
|
|
100
|
+
ok = true;
|
|
101
|
+
} catch {
|
|
102
|
+
// fall through — metadata may still land
|
|
103
|
+
}
|
|
104
|
+
try {
|
|
105
|
+
await herdr.paneReportMetadata(
|
|
106
|
+
{
|
|
107
|
+
pane_id: this.opts.paneId,
|
|
108
|
+
source: this.opts.source,
|
|
109
|
+
agent,
|
|
110
|
+
custom_status: status,
|
|
111
|
+
// Expire if this reporter dies without releasing: a bit over
|
|
112
|
+
// two keepalive cycles keeps the annotation fresh-or-gone.
|
|
113
|
+
ttl_ms: 90_000,
|
|
114
|
+
},
|
|
115
|
+
this.opts,
|
|
116
|
+
);
|
|
117
|
+
ok = true;
|
|
118
|
+
} catch {
|
|
119
|
+
// best-effort
|
|
120
|
+
}
|
|
121
|
+
return ok;
|
|
122
|
+
}
|
|
123
|
+
|
|
124
|
+
async release(): Promise<void> {
|
|
125
|
+
try {
|
|
126
|
+
await herdr.paneReleaseAgent(
|
|
127
|
+
{ pane_id: this.opts.paneId, source: this.opts.source, agent: this.opts.agentLabel ?? "pi" },
|
|
128
|
+
this.opts,
|
|
129
|
+
);
|
|
130
|
+
} catch {
|
|
131
|
+
// best-effort
|
|
132
|
+
}
|
|
133
|
+
}
|
|
134
|
+
}
|
|
135
|
+
|
|
136
|
+
export interface HerdrAgentInfo {
|
|
137
|
+
pane_id: string;
|
|
138
|
+
agent?: string;
|
|
139
|
+
agent_status?: string;
|
|
140
|
+
custom_status?: string;
|
|
141
|
+
workspace_id?: string;
|
|
142
|
+
[key: string]: unknown;
|
|
143
|
+
}
|
|
144
|
+
|
|
145
|
+
export interface AgentWatchOptions extends HerdrClientOptions {
|
|
146
|
+
// Called with the full current agent set after every change (initial
|
|
147
|
+
// snapshot included). Consumers diff/join against their own state.
|
|
148
|
+
onChange: (agents: HerdrAgentInfo[]) => void;
|
|
149
|
+
// This process's own pane — excluded from the tracked set.
|
|
150
|
+
ownPaneId?: string | null;
|
|
151
|
+
onError?: (err: Error) => void;
|
|
152
|
+
reconnectDelayMs?: number;
|
|
153
|
+
}
|
|
154
|
+
|
|
155
|
+
// Push-driven view of the herdr agent population. start() takes an
|
|
156
|
+
// agent.list snapshot and opens the event stream; pane lifecycle events
|
|
157
|
+
// refresh the snapshot (and the per-pane subscription set).
|
|
158
|
+
export class HerdrAgentWatch {
|
|
159
|
+
private opts: AgentWatchOptions;
|
|
160
|
+
private agents = new Map<string, HerdrAgentInfo>();
|
|
161
|
+
private stream: SubscribeHandle | null = null;
|
|
162
|
+
private stopped = false;
|
|
163
|
+
private resyncTimer: ReturnType<typeof setTimeout> | null = null;
|
|
164
|
+
// Pane-id set the live stream was opened with. resync() only tears the
|
|
165
|
+
// stream down when the set actually changed — an unconditional resubscribe
|
|
166
|
+
// would loop forever through onConnect → resync → resubscribe → onConnect,
|
|
167
|
+
// hammering the server with stream churn (seen live: herdr pegged a core).
|
|
168
|
+
private subscribedKey: string | null = null;
|
|
169
|
+
|
|
170
|
+
constructor(opts: AgentWatchOptions) {
|
|
171
|
+
this.opts = opts;
|
|
172
|
+
}
|
|
173
|
+
|
|
174
|
+
current(): HerdrAgentInfo[] {
|
|
175
|
+
return [...this.agents.values()];
|
|
176
|
+
}
|
|
177
|
+
|
|
178
|
+
async start(): Promise<void> {
|
|
179
|
+
await this.resync();
|
|
180
|
+
}
|
|
181
|
+
|
|
182
|
+
stop(): void {
|
|
183
|
+
this.stopped = true;
|
|
184
|
+
this.stream?.close();
|
|
185
|
+
this.stream = null;
|
|
186
|
+
this.subscribedKey = null;
|
|
187
|
+
if (this.resyncTimer) clearTimeout(this.resyncTimer);
|
|
188
|
+
this.resyncTimer = null;
|
|
189
|
+
}
|
|
190
|
+
|
|
191
|
+
// Re-list agents, rebuild the subscription set if it changed, notify.
|
|
192
|
+
private async resync(): Promise<void> {
|
|
193
|
+
if (this.stopped) return;
|
|
194
|
+
try {
|
|
195
|
+
const { agents } = await herdr.agentList(this.opts);
|
|
196
|
+
this.agents.clear();
|
|
197
|
+
for (const a of agents as HerdrAgentInfo[]) {
|
|
198
|
+
const paneId = a.pane_id as string | undefined;
|
|
199
|
+
if (!paneId || paneId === this.opts.ownPaneId) continue;
|
|
200
|
+
this.agents.set(paneId, a);
|
|
201
|
+
}
|
|
202
|
+
} catch (err) {
|
|
203
|
+
this.opts.onError?.(err as Error);
|
|
204
|
+
}
|
|
205
|
+
const key = [...this.agents.keys()].sort().join("\n");
|
|
206
|
+
if (this.stream === null || key !== this.subscribedKey) this.resubscribe(key);
|
|
207
|
+
this.opts.onChange(this.current());
|
|
208
|
+
}
|
|
209
|
+
|
|
210
|
+
// Debounced resync: lifecycle events often arrive in bursts (layout.apply
|
|
211
|
+
// creates N panes); one refresh after the burst is enough.
|
|
212
|
+
private scheduleResync(): void {
|
|
213
|
+
if (this.stopped || this.resyncTimer) return;
|
|
214
|
+
this.resyncTimer = setTimeout(() => {
|
|
215
|
+
this.resyncTimer = null;
|
|
216
|
+
void this.resync();
|
|
217
|
+
}, 250);
|
|
218
|
+
}
|
|
219
|
+
|
|
220
|
+
private resubscribe(key: string): void {
|
|
221
|
+
this.stream?.close();
|
|
222
|
+
this.subscribedKey = null;
|
|
223
|
+
if (this.stopped) return;
|
|
224
|
+
const subs: Subscription[] = [
|
|
225
|
+
{ type: "pane.created" },
|
|
226
|
+
{ type: "pane.closed" },
|
|
227
|
+
{ type: "pane.exited" },
|
|
228
|
+
{ type: "workspace.closed" },
|
|
229
|
+
];
|
|
230
|
+
for (const paneId of this.agents.keys()) {
|
|
231
|
+
subs.push({ type: "pane.agent_status_changed", pane_id: paneId });
|
|
232
|
+
}
|
|
233
|
+
// The ack of THIS deliberately opened stream must not resync: the
|
|
234
|
+
// snapshot is milliseconds old, and resyncing here restarts the
|
|
235
|
+
// subscribe/close loop. Only a genuine drop + reconnect (events
|
|
236
|
+
// possibly missed while disconnected) warrants a fresh snapshot.
|
|
237
|
+
let initialAck = true;
|
|
238
|
+
this.stream = subscribe(subs, (ev) => this.handleEvent(ev.event, ev.data), {
|
|
239
|
+
socketPath: this.opts.socketPath,
|
|
240
|
+
reconnectDelayMs: this.opts.reconnectDelayMs,
|
|
241
|
+
onError: this.opts.onError,
|
|
242
|
+
onConnect: () => {
|
|
243
|
+
if (initialAck) {
|
|
244
|
+
initialAck = false;
|
|
245
|
+
return;
|
|
246
|
+
}
|
|
247
|
+
this.scheduleResync();
|
|
248
|
+
},
|
|
249
|
+
});
|
|
250
|
+
this.subscribedKey = key;
|
|
251
|
+
}
|
|
252
|
+
|
|
253
|
+
private handleEvent(event: string, data: Record<string, unknown>): void {
|
|
254
|
+
const paneId = data.pane_id as string | undefined;
|
|
255
|
+
switch (event) {
|
|
256
|
+
case "pane.agent_status_changed": {
|
|
257
|
+
if (!paneId) return;
|
|
258
|
+
const existing = this.agents.get(paneId);
|
|
259
|
+
if (existing) {
|
|
260
|
+
existing.agent_status = data.agent_status as string;
|
|
261
|
+
if (typeof data.agent === "string") existing.agent = data.agent;
|
|
262
|
+
if (typeof data.custom_status === "string") existing.custom_status = data.custom_status;
|
|
263
|
+
this.opts.onChange(this.current());
|
|
264
|
+
} else {
|
|
265
|
+
// Status for a pane we don't track yet (e.g. agent detected
|
|
266
|
+
// after creation) — refresh the snapshot.
|
|
267
|
+
this.scheduleResync();
|
|
268
|
+
}
|
|
269
|
+
return;
|
|
270
|
+
}
|
|
271
|
+
case "pane.closed":
|
|
272
|
+
case "pane.exited": {
|
|
273
|
+
if (paneId && this.agents.delete(paneId)) {
|
|
274
|
+
this.opts.onChange(this.current());
|
|
275
|
+
}
|
|
276
|
+
// The pane set changed either way — resubscribe without the
|
|
277
|
+
// dead pane (and catch anything created meanwhile).
|
|
278
|
+
this.scheduleResync();
|
|
279
|
+
return;
|
|
280
|
+
}
|
|
281
|
+
case "pane.created":
|
|
282
|
+
case "workspace.closed": {
|
|
283
|
+
this.scheduleResync();
|
|
284
|
+
return;
|
|
285
|
+
}
|
|
286
|
+
}
|
|
287
|
+
}
|
|
288
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "agent-fleet-pi-harnesses-runtime-deps",
|
|
3
|
+
"lockfileVersion": 3,
|
|
4
|
+
"requires": true,
|
|
5
|
+
"packages": {
|
|
6
|
+
"": {
|
|
7
|
+
"name": "agent-fleet-pi-harnesses-runtime-deps",
|
|
8
|
+
"dependencies": {
|
|
9
|
+
"@sinclair/typebox": "^0.34.0",
|
|
10
|
+
"yaml": "^2.8.0"
|
|
11
|
+
}
|
|
12
|
+
},
|
|
13
|
+
"node_modules/@sinclair/typebox": {
|
|
14
|
+
"version": "0.34.49",
|
|
15
|
+
"resolved": "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.34.49.tgz",
|
|
16
|
+
"integrity": "sha512-brySQQs7Jtn0joV8Xh9ZV/hZb9Ozb0pmazDIASBkYKCjXrXU3mpcFahmK/z4YDhGkQvP9mWJbVyahdtU5wQA+A==",
|
|
17
|
+
"license": "MIT"
|
|
18
|
+
},
|
|
19
|
+
"node_modules/yaml": {
|
|
20
|
+
"version": "2.9.0",
|
|
21
|
+
"resolved": "https://registry.npmjs.org/yaml/-/yaml-2.9.0.tgz",
|
|
22
|
+
"integrity": "sha512-2AvhNX3mb8zd6Zy7INTtSpl1F15HW6Wnqj0srWlkKLcpYl/gMIMJiyuGq2KeI2YFxUPjdlB+3Lc10seMLtL4cA==",
|
|
23
|
+
"license": "ISC",
|
|
24
|
+
"bin": {
|
|
25
|
+
"yaml": "bin.mjs"
|
|
26
|
+
},
|
|
27
|
+
"engines": {
|
|
28
|
+
"node": ">= 14.6"
|
|
29
|
+
},
|
|
30
|
+
"funding": {
|
|
31
|
+
"url": "https://github.com/sponsors/eemeli"
|
|
32
|
+
}
|
|
33
|
+
}
|
|
34
|
+
}
|
|
35
|
+
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Implement the next task incrementally — build, test, verify, request review
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `incremental-implementation` and `test-driven-development` skills before proceeding.
|
|
6
|
+
|
|
7
|
+
Pick the next pending task from the plan. For each task:
|
|
8
|
+
|
|
9
|
+
1. Read the task's acceptance criteria
|
|
10
|
+
2. Load relevant context (existing code, patterns, types)
|
|
11
|
+
3. Write a failing test for the expected behavior (RED)
|
|
12
|
+
4. Implement the minimum code to pass the test (GREEN)
|
|
13
|
+
5. Run the full test suite to check for regressions
|
|
14
|
+
6. Run the build to verify compilation
|
|
15
|
+
7. Present the Standard Slice Summary and ask the user to choose between:
|
|
16
|
+
- **Approve & continue** — proceed to the next slice
|
|
17
|
+
- **Request changes** — revise within the same slice, then re-summarize and re-ask
|
|
18
|
+
- **Compact & continue** — call `request_compaction` (from the `compact-and-continue` extension) with a self-contained `continuationPrompt` describing the remaining slices and the next concrete action, then end the turn so compaction runs; pi will auto-resume from the continuation prompt
|
|
19
|
+
- **Stop here** — leave changes unstaged and end the session
|
|
20
|
+
Use the `ask_user` tool (from `pi-ask-user`) when available; otherwise ask in chat. Wait for an explicit choice — do not proceed on silence. If the `request_compaction` tool is not registered (extension not installed), omit the "Compact & continue" option.
|
|
21
|
+
8. Leave changes unstaged; the user handles staging and commits manually
|
|
22
|
+
9. Mark the task complete and move to the next one only after approval
|
|
23
|
+
|
|
24
|
+
If any step fails, load and follow the `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
|
+
Load and follow the `code-simplification` skill before proceeding.
|
|
6
|
+
|
|
7
|
+
Simplify recently changed code (or the specified scope) while preserving exact behavior:
|
|
8
|
+
|
|
9
|
+
1. Read the repository agent guide 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. Load and follow `code-review-and-quality` to review the result.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Scan agent-fleet install targets for broken symlinks, stale persona references, and overrides-file problems, then offer repairs
|
|
3
|
+
---
|
|
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.
|
|
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 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
|
+
|
|
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
|
+
|
|
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.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Break work into small verifiable tasks with acceptance criteria and dependency ordering
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `planning-and-task-breakdown` skill before proceeding.
|
|
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,16 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Conduct a five-axis code review — correctness, readability, architecture, security, performance
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `code-review-and-quality` skill before proceeding.
|
|
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? Load and follow the `security-and-hardening` skill where relevant.
|
|
13
|
+
5. **Performance** — No N+1 queries? No unbounded ops? Load and follow the `performance-optimization` skill where relevant.
|
|
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,27 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Guided setup — install agent-fleet artifacts into a workspace for a chosen coding agent
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `guided-workspace-setup` skill before proceeding.
|
|
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
|
+
**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.
|
|
12
|
+
|
|
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
|
+
|
|
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
|
+
|
|
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
|
+
|
|
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
|
+
|
|
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
|
+
|
|
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
|
+
|
|
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
|
+
|
|
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,17 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Run the pre-launch checklist and prepare for production deployment
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `shipping-and-launch` skill before proceeding.
|
|
6
|
+
|
|
7
|
+
Run through the complete pre-launch checklist:
|
|
8
|
+
|
|
9
|
+
1. **Code Quality** — Tests pass, build clean, lint clean, no TODOs, no console.logs
|
|
10
|
+
2. **Security** — npm audit clean, no secrets in code, auth in place, headers configured
|
|
11
|
+
3. **Performance** — Core Web Vitals good, no N+1 queries, images optimized, bundle sized
|
|
12
|
+
4. **Accessibility** — Keyboard nav works, screen reader compatible, contrast adequate
|
|
13
|
+
5. **Infrastructure** — Env vars set, migrations ready, monitoring configured
|
|
14
|
+
6. **Documentation** — README current, ADRs written, changelog updated
|
|
15
|
+
|
|
16
|
+
Report any failing checks and help resolve them before deployment.
|
|
17
|
+
Define the rollback plan before proceeding.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Start spec-driven development — write a structured specification before writing code
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `spec-driven-development` skill before proceeding.
|
|
6
|
+
|
|
7
|
+
Begin by understanding what the user wants to build. Ask clarifying questions about:
|
|
8
|
+
1. The objective and target users
|
|
9
|
+
2. Core features and acceptance criteria
|
|
10
|
+
3. Tech stack preferences and constraints
|
|
11
|
+
4. Known boundaries (what to always do, ask first about, and never do)
|
|
12
|
+
|
|
13
|
+
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
|
|
14
|
+
|
|
15
|
+
Save the spec to the location the `spec-driven-development` skill defines (default `docs/prds/{area}/PRD{n}-{topic}.md`; overridable per project via `.ai/agent-fleet-overrides.md`). Confirm with the user before proceeding.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Load and follow the `test-driven-development` skill before proceeding.
|
|
6
|
+
|
|
7
|
+
For new features:
|
|
8
|
+
1. Write tests that describe the expected behavior (they should FAIL)
|
|
9
|
+
2. Implement the code to make them pass
|
|
10
|
+
3. Refactor while keeping tests green
|
|
11
|
+
|
|
12
|
+
For bug fixes (Prove-It pattern):
|
|
13
|
+
1. Write a test that reproduces the bug (must FAIL)
|
|
14
|
+
2. Confirm the test fails
|
|
15
|
+
3. Implement the fix
|
|
16
|
+
4. Confirm the test passes
|
|
17
|
+
5. Run the full test suite for regressions
|
|
18
|
+
|
|
19
|
+
For browser-related issues, also load and follow the `browser-testing-with-devtools` skill and verify with Chrome DevTools MCP.
|