executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Explorer les Skills
Productivité · SKILL.md
patrol-monitoring
patrol-monitoringContinuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.
Independent GitHub snapshot · Automated classification · Original documentation governs
Documentation de la Skill
GitHubname: patrol-monitoring description: Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery. allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion graph: domains: [domain:software-engineering] skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop] workflows: [workflow:feature-development] topics: [topic:developer-experience] roles: [role:tech-lead, role:backend-engineer]
- When agents may become stuck or unresponsive
- For long-running multi-agent workflows
- When automated recovery is desired
Process
- Health check all active agents and convoys
- Detect stuck or unresponsive agents via heartbeats
- Recover - restart, reassign, or escalate as needed
- Report patrol findings with trend analysis
Monitoring Roles
- Deacon: Daemon supervisor, monitors overall health
- Witness: Per-rig lifecycle manager for workers
- Boot (Dog): Watches the Deacon every 5 minutes
Recovery Modes
- restart: Restart the stuck agent session
- reassign: Move beads to a different agent
- escalate: Alert human for manual intervention
Tool Use
Invoke via babysitter process: methodologies/gastown/gastown-patrol