steward-watch

Automates steward watch-respond-rewatch lifecycle by monitoring inbound channels and triaging messages per SOP.

3|1|Updated Jan 8, 2026

Search Tags:#automation #workflow #orchestrator #sop #watch #steward

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill steward-watch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: steward-watch
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/steward-watch
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill steward-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs the steward watch-respond-rewatch lifecycle by continuously monitoring an inbound channel, triaging messages according to the SOP, executing required actions, and posting outcomes for audit and rewatching.

Core Features & Use Cases

Continuous inbound message monitoring and triage according to the SOP for autonomous, queued, or custom modes.
Lifecycle management: create, monitor, and inject chunks, coordinate with orchestrator, and publish changelog updates.
Safe, deterministic processing: explicit stop, ack, and safety guidance to avoid duplicate processing and orphan tasks.
Rewatch and recovery: reliably re-engage monitoring after actions to maintain state consistency.

Quick Start

Run the steward-watch loop to begin monitoring the designated inbound channel and triaging messages.

Frequently Asked Questions about steward-watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate continuous inbound message triage for operational workflows?▼

You can automate continuous message triage by running the steward-watch loop to monitor an inbound channel, apply deterministic SOP-based handling, execute actions, and post outcomes for audit. It manages the entire watch-respond-rewatch lifecycle autonomously.

What is the watch-respond-rewatch cycle for workflow orchestration?▼

The watch-respond-rewatch cycle is an automated message triage process that continuously monitors inbound channels, executes SOP-based actions, and reliably re-engages monitoring after actions to maintain state consistency and prevent orphan tasks.

How do I configure an automated SOP orchestrator for message monitoring?▼

Configure the SOP orchestrator via documented frontmatter specifying swarm, channel, changelog_channel, behavior.mode, and behavior.custom_instructions. These parameters control triage behavior, chunk creation, and orchestrator coordination for the monitoring loop.

Can I run autonomous message triage without creating duplicate tasks?▼

Yes, autonomous message triage enforces safe deterministic processing with explicit stop, ack, and safety guidance to avoid duplicate processing and orphan tasks while coordinating chunk creation with the orchestrator.

How do I recover monitoring state after executing triage actions?▼

Recover monitoring state through the rewatch mechanism, which reliably re-engages monitoring after actions execute. This maintains state consistency across the watch-respond-rewatch lifecycle and coordinates with orchestrator-monitor for chunk management.

Does the steward-watch orchestrator support queued or custom triage modes?▼

Yes, the orchestrator supports autonomous, queued, and custom behavior modes for inbound message triage. Custom modes allow tailored SOP-based handling while maintaining the same deterministic processing and rewatch recovery lifecycle.