Scope Check

Scope Check

Compares original planned scope against current state to detect, quantify, and triage

Category: content-creation Source: Donchitos/Claude-Code-Game-Studios

Scope Check: Detecting and Quantifying Scope Creep in Content Creation Projects

Scope management is a critical aspect of any software or content development process. The "Scope Check" skill for the Happycapy Skills platform is designed to help teams stay on track by systematically comparing the original planned scope of a feature, sprint, or milestone against its current state. This article provides a technical overview of the Scope Check skill, explaining its purpose, rationale, usage, optimal application times, and important implementation notes.

What Is Scope Check?

Scope Check is a read-only, analytical skill that identifies, quantifies, and triages scope creep within a project. Given a feature name, sprint number, or milestone, it locates the original scope definition, assesses the current implementation or progress, and flags any additions or deviations. It also quantifies the extent of scope bloat and suggests possible cuts to bring the project back in line with initial goals. Scope Check operates without modifying any files, ensuring that its analysis is non-intrusive and purely diagnostic.

The skill is invoked with a single argument, such as a feature identifier or sprint name. Based on this input, it methodically compares the baseline scope document with the live state of the codebase and related project artifacts.

Why Use Scope Check?

Scope creep is a common risk factor in content creation and software development. It occurs when new requirements, features, or tasks are added after the initial planning phase, often without proper evaluation or resource allocation. Unchecked scope creep leads to missed deadlines, budget overruns, and diluted project focus. Traditional manual reviews are time-consuming and prone to oversight.

By automating the comparison between planned and current scope, Scope Check provides several benefits:

  • Early Detection: Instantly highlights new or unplanned additions that may not have been formally approved.
  • Quantification: Measures the degree of deviation, helping teams prioritize corrective action.
  • Audit Trail: Provides objective evidence of where and how scope has changed, useful for retrospectives and process improvement.
  • Actionable Insights: Recommends specific items to cut or defer, enabling faster decision-making.

Scope Check is particularly valuable in agile environments where rapid iteration can lead to unintentional expansion of work items.

How to Use Scope Check

To use Scope Check on the Happycapy Skills platform, invoke the skill with the relevant argument representing the scope you wish to analyze. The argument can be a feature name, sprint number, or milestone name.

Example Usage:

scope-check "inventory-system"
scope-check "sprint-04"
scope-check "Alpha-Release"

Step-by-Step Process

  1. Locate the Baseline Scope Document

    • For a feature: Looks for design/gdd/[feature].md or similar files in the design/ directory.
    • For a sprint: Searches for production/sprints/sprint-XX.md or equivalent in the production/sprints/ directory.
    • For a milestone: Checks production/milestones/[milestone].md.
    • If the baseline document is missing, Scope Check reports the missing file and stops, as there is nothing to compare against.

  2. Read the Current State

    • Scans the codebase for files related to the target feature, sprint, or milestone.
    • Reads the git log for relevant commits, typically filtering by date or related keywords.
    • Searches for TODO or FIXME comments that may indicate ongoing or unplanned work.
    • Reviews the active sprint plan if the feature is currently in development.

Sample Command to Review Commits:

git log --oneline --since="2024-05-01" --grep="inventory"
  1. Compare and Analyze
    • Identifies discrepancies between the baseline and current state.
    • Flags any additions or changes that are not part of the original plan.
    • Quantifies the scope increase, such as percentage bloat or number of extra features.
    • Recommends specific items for removal or deferment to restore focus.

When to Use Scope Check

Scope Check should be used at the following points in the development lifecycle:

  • During Sprint Reviews: To verify that the team is delivering only what was agreed upon at sprint planning.
  • Before Major Releases: To ensure that feature creep has not jeopardized release readiness.
  • After Significant Feature Work: To catch incremental scope changes that may have occurred during development.
  • Whenever Concerns Arise: If team members raise questions such as "Are we staying in scope?" or "Has there been any scope creep?"

Regular use of Scope Check ensures that scope drift is caught early and managed proactively.

Important Notes

  • Read-Only Operation: Scope Check does not modify any files or project data. Its function is strictly analytical.
  • Dependency on Baseline Documents: Without a baseline document, the skill cannot perform a comparison and will terminate with a missing file report.
  • Flexible Argument Handling: The skill intelligently locates the relevant baseline document based on the argument provided, but directory conventions should be followed for reliable results.
  • Complementary to Human Review: While automated, the results should be interpreted by project leads or scrum masters, especially when making decisions about cuts or deferrals.

Scope Check is a powerful addition to any content-creation workflow, equipping teams with automated scope analysis to maintain project discipline and deliverables. By integrating this tool into regular project reviews, teams can enhance transparency, accountability, and delivery performance.