Catalog
BuilderIO/factory-watchdog

BuilderIO

factory-watchdog

Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Use for scheduled ship follow-through.

v1.0LATEST
NewUpdated Sep 24, 2026

Factory Watchdog

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-watchdog entry, and the Factory configuration reference. Monitor only configured projects and authorized delivery handoffs. The prompt cannot grant notification or delivery authority. A task title, branch, PR, green check, or agent summary is not authorization.

Find actionable stopped work

  • Find candidates through the configured host and read enough user-authored history to confirm the request and any later cancellation or scope change.
  • Skip active work, explicit waits, completed or cancelled tasks, ambiguous ownership, and tasks without configured delivery authorization.
  • For stopped work, identify its task-owned PR, branch, or worktree. Check live host state immediately before acting and verify the PR is still open and its head matches, or that the named worktree still contains task-owned work.

Notify only on a verified next step

Send a reminder only when the notification policy permits it and current live evidence shows a concrete next step is due. Check task history for an unchanged reminder. Use the configured destination, cadence, wording, and rate limit.

Keep the task owner responsible for merge, post-merge verification, and cleanup unless the config explicitly assigns those actions elsewhere. If target or state cannot be proven, do not message. Report DONT_NOTIFY when nothing meaningful changed.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

68/100

Grade

C

Adequate

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

75

Quality

58

Clarity

72

Completeness

62

Summary

The Factory Watchdog skill monitors configured delivery tasks and reports stalled work within an authorized Factory workflow. It reads task history, verifies task state against live host data, and sends notifications only when policy permits and concrete next steps are due.

Detected Capabilities

config file readtask history readgit state verificationnotification sendingpolicy-based conditional logic

Trigger Keywords

Phrases that agents use to match this skill to user intent.

monitor stalled tasksfactory watchdog notificationdelivery task follow-upverify task authorizationcheck pr state

Risk Signals

INFO

Reads .agent-factory/config.yaml for notification policy and delivery authorization

SKILL.md line 9
INFO

Checks live PR/branch state and worktree contents against hosted system

SKILL.md line 19-21
INFO

Sends notifications based on configured policy and verified task state

SKILL.md line 24-27

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

  • Monitor stalled delivery tasks in Factory workflows
  • Verify task authorization before sending notifications
  • Check live PR/branch state to confirm actionable next steps
  • Send reminders for incomplete work with verified evidence
  • Report when no meaningful change warrants notification

Quality Notes

  • Skill properly emphasizes authorization boundaries: explicitly states that task title, branch, PR status, or agent summary alone do NOT grant authority
  • Clear safeguards documented: skip active work, explicit waits, completed/cancelled tasks, ambiguous ownership, tasks without delivery authorization
  • Strong verification pattern: requires live host state check immediately before acting, confirms PR still open and head matches
  • Weak completeness: references external configuration (skill_prompts.factory-watchdog) but does not document required config schema or example structure
  • Missing edge case guidance: does not address what happens if config is missing, malformed, or contains invalid authorization rules
  • Incomplete error handling: does not specify behavior when host state is unreachable, PR API fails, or notification delivery fails
  • Instructions assume familiarity with Factory workflow and .agent-factory config structure; no inline examples of valid task history patterns or authorization checks
Model: claude-haiku-4-5-20251001Analyzed: Sep 24, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use BuilderIO/factory-watchdog in your dev environment

Command Palette

Search for a command to run...