guardian
Guardian — Agent Team Progress Monitor
The Guardian is a persistent, lightweight teammate that monitors an agent team via tmux and intervenes only when the Lead gets stuck or goes idle. It runs on a recurring cron loop for the entire duration of the work session.
Guardian Role Summary
| Attribute | Value |
|---|---|
| Model | haiku (cheapest; monitoring is procedural) |
| Type | general-purpose subagent |
| Team membership | Required — spawned via Agent(team_name=..., name="guardian", ...) |
| Lifetime | Entire work session — spawned after TeamCreate, cancelled as the LAST action |
| Cron interval | 5 minutes (*/5 * * * *) |
| Cron durability | false (session-only; dies with Lead) |
How the Lead Spawns the Guardian
More from satone7/skills
writing-plans-plus
Enhanced planning with structured, machine-readable task format based on writing-plans. Use this skill whenever you need to create implementation plans with explicit completion tracking, cross-validation issue tracking, or machine-readable JSON output. Always use this when planning software development tasks, especially when tasks need to be executed by other agents or reviewed later.
10find-next-task
Find the next executable task from writing-plans-plus JSON plan files. Use this skill whenever you need to locate the next task to work on, check task status, or understand what to do next in a project with structured plans. Always use this when the user asks "what's next", "find the next task", "show pending tasks", or wants to continue working on a plan.
5aitc-workflow
>
5find-task-skills
>
4executing-single-task
执行 writing-plans-plus 计划中的“恰好一个任务”：输入为 find-next-task 的完整输出 JSON。严格按四阶段流程（实现→规范审查→质量审查→最终验证），基于证据更新 plan JSON 的 passes（成功时删除 issue 字段；失败时写入/更新非空 issue[]），并创建且仅创建一个 git commit。凡用户要求“执行下一个任务/只跑一个任务/把 passes 写回/自动执行单任务”都应优先使用本技能。
4github-pr-fixer
>
3