hourly-supervisor-review

Validate Awaiting Test queue submissions against Notion logs and repository state.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/michaelkd01/dic-skills --skill hourly-supervisor-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hourly-supervisor-review
Source: https://github.com/michaelkd01/dic-skills/tree/main/hourly-supervisor-review
Command: npx skills add https://github.com/michaelkd01/dic-skills --skill hourly-supervisor-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill protects product quality by autonomously vetting Awaiting Test tasks so humans do not miss regressions or undocumented state before deployment.

Core Features & Use Cases

  • Scheduled Review: Triggers hourly via Claude, enumerates Awaiting Test items, and logs the review start, counters, and outcomes.
  • Evidence-Based Validation: Gathers Notion execution logs, repository history, branch strategy, tests, lints, and architectural guidance to evaluate each acceptance criterion.
  • Conservative Decisioning: Auto-passes only when every criterion is PASS and no drift is detected, otherwise flags tasks, comments in Notion, updates logs, and alerts via Slack.

Quick Start

Ask hourly-supervisor-review to run now and report which Awaiting Test tasks passed or need human attention.

Frequently Asked Questions about hourly-supervisor-review

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

FAQPage Schema
How do I automate Notion QA queue reviews for awaiting test tasks?

Automated Notion QA queue reviews validate Awaiting Test tasks by checking Notion execution logs, repository state, and acceptance criteria hourly. It logs outcomes and auto-passes tasks only when every criterion passes without drift.

How do I validate git branch state before merging scheduled feature branches?

Validating git branch state before merging scheduled feature branches involves checking repository history and branch strategy against acceptance criteria. This conservative approach flags tasks and alerts via Slack when drift is detected.

Does hourly supervisor review work with Slack notifications and Notion databases?

Hourly supervisor review requires integration with Notion databases, git repositories, osascript commands, and Slack DM notifications to enforce conservative verdicts, log results, and alert humans when tasks need attention.

What happens when an awaiting test task fails acceptance criteria validation?

When an Awaiting Test task fails acceptance criteria validation, the supervisor workflow flags the task, comments in Notion, updates execution logs, and alerts the team via Slack DM notifications requiring human attention.

Why does conservative QA automation auto-pass only when no repository drift is detected?

Conservative QA automation auto-passes only when no repository drift is detected to prevent missed regressions or undocumented state before deployment, ensuring product quality by autonomously vetting tasks instead of blindly merging.

Do I need osascript and git integration to run scheduled QA automation?

You need git repositories and osascript commands alongside Notion databases and Slack DM notifications to run scheduled QA automation, enabling the hourly supervisor workflow to enumerate Awaiting Test items and log outcomes.