scope-guardian-reviewer

Analyze consulting proposals and statements of work for scope creep risks.

29|12|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/matteotitta/genesys-skills --skill scope-guardian-reviewer-matteotitta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-guardian-reviewer
Source: https://github.com/matteotitta/genesys-skills/tree/main/skills/meta/catalog/scope-guardian-reviewer
Command: npx skills add https://github.com/matteotitta/genesys-skills --skill scope-guardian-reviewer-matteotitta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unbillable rework by identifying vague deliverables, unbounded revisions, and missing acceptance criteria in client-facing proposals and statements of work.

Core Features & Use Cases

  • Risk Assessment: Evaluates documents against five critical dimensions including mission drift and client-input dependencies.
  • Actionable Rewrites: Provides specific, bounded language replacements to tighten scope and protect project margins.
  • Use Case: Before sending a complex consulting proposal, run this review to ensure all deliverables are clearly defined and protected against open-ended requests.

Quick Start

Invoke the scope guardian reviewer on your draft proposal to identify and fix potential scope creep risks.

Frequently Asked Questions about scope-guardian-reviewer

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

FAQPage Schema
How do I prevent scope creep in B2B SaaS consulting proposals?

To prevent scope creep in B2B SaaS consulting proposals, you analyze client documents for vague deliverables and missing acceptance criteria. This process identifies unbounded revisions, ensuring all commitments are clearly defined to protect project margins against unbillable rework.

How do I identify unrealistic delivery commitments in a statement of work?

You identify unrealistic delivery commitments in a statement of work by validating project documentation against a five-dimensional risk framework. This evaluates mission drift and client-input dependencies to highlight unbounded requests that threaten delivery timelines and project margins.

What is the best way to tighten vague deliverables in a SaaS proposal?

The best way to tighten vague deliverables in a SaaS proposal is by generating actionable rewrites with bounded language. This provides specific replacements to clearly define deliverables and establish strict revision limits for professional consulting documents.

Can I review a draft consulting proposal for mission drift before sending it?

Yes, you can review a draft consulting proposal for mission drift before sending it by running a scope guardian analysis. This detects unbillable rework risks and ensures all deliverables are protected against open-ended client requests.

Does this scope review work for complex SaaS project documentation?

Yes, this scope review works for complex SaaS project documentation by evaluating professional consulting documents against a five-dimensional risk framework. It operates on statements of work to produce tighter-scope rewrites tailored for complex B2B SaaS environments.