scope-creep-flagger

Detect and flag out-of-scope requests from Slack and Gmail against a signed SOW.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/venturecrane/ss-console --skill scope-creep-flagger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-creep-flagger
Source: https://github.com/venturecrane/ss-console/tree/main/operator/skills/scope-creep-flagger
Command: npx skills add https://github.com/venturecrane/ss-console --skill scope-creep-flagger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires hermes, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies requests outside the scope of a service agreement (SOW), preventing scope creep and ensuring that the agency's resources are used efficiently.

Core Features & Use Cases

  • Detects Out-of-Scope Requests: Monitors Slack channels and email inboxes for requests that exceed the agreed-upon SOW.
  • Surfaces to Agency Owner: Immediately alerts the agency owner with a one-paragraph proposed disposition.
  • Use Case: When a client requests additional work that is not covered by the SOW, the Skill flags it to the owner, who can then decide the best course of action.

Quick Start

Use the scope-creep-flagger skill to flag a message from a Slack channel that is out of scope.

Frequently Asked Questions about scope-creep-flagger

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

FAQPage Schema
How do I detect out-of-scope requests in Slack and email to prevent scope creep?

Scope creep detection in Slack and email works by monitoring communication channels against a signed SOW, flagging out-of-scope requests to the agency owner with a proposed disposition.

What is SOW compliance monitoring for agency project management?

SOW compliance monitoring evaluates incoming client requests against the signed service agreement, automatically identifying work that exceeds the agreed scope and alerting the agency owner to protect profits.

Do I need Hermes to run automated scope creep flagging for incoming client messages?

Yes, you need Hermes for execution. The Skill requires the Hermes environment to process Slack and Gmail communications and assess whether requests fall inside or outside the signed SOW.

Can I use this to flag out-of-SOW requests across both Gmail and Slack channels?

Yes, the Skill monitors both Slack channels and Gmail inboxes to detect client requests that exceed the agreed-upon SOW, immediately surfacing them to the agency owner for review.

What's the best way to alert agency owners about scope creep without manual monitoring?

Automated request flagging assesses messages against the signed SOW and alerts the agency owner with a one-paragraph proposed disposition, eliminating the need for manual communication channel monitoring.

When should I not rely on automated SOW compliance flagging for project management?

Automated SOW compliance flagging should not replace human judgment when a client request is ambiguous, as the Skill assesses scope boundaries but the agency owner must make the final disposition decision.