scope-guard

Compares git diff against a plan and reports drift percentage by tiered status.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill scope-guard-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-guard
Source: https://github.com/linenoize/topia/tree/main/skills/scope-guard
Command: npx skills add https://github.com/linenoize/topia --skill scope-guard-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents scope creep by comparing current changes against the original plan and surfacing unexpected files before they spread into larger work.

Core Features & Use Cases

  • Plan-aware review: Loads the active task plan from todo state or .topia/progress.md and extracts intended files, tasks, and exclusions.
  • Git change inspection: Reviews staged and unstaged diffs to identify what actually changed in the repository.
  • Drift classification: Labels changes as in-scope or out-of-scope, then computes drift percentage and assigns a tiered status for escalation.
  • Use case: A coding agent adds an unplanned feature while implementing a fix; this skill flags the extra files, quantifies the drift, and recommends whether to continue, pause, or re-scope.

Quick Start

Use the scope-guard skill to compare the current git diff against the active plan and report any out-of-scope files with drift percentage.

Frequently Asked Questions about scope-guard

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

FAQPage Schema
How do I detect scope creep in my git diff before merging changes?

Detect scope creep by comparing changed files in your git diff against the original plan, classifying in-scope and out-of-scope changes, and calculating drift percentage for tiered status reporting.

What is plan validation for coding workflows and how does it prevent drift?

Plan validation prevents drift by loading the active task plan, extracting intended files and exclusions, then inspecting git changes to ensure task execution stays within agreed scope boundaries.

How do I calculate drift percentage for out-of-scope file changes?

Calculate drift percentage by labeling changed files as in-scope or out-of-scope relative to the original plan, then compute the ratio of out-of-scope changes to assign a tiered escalation status.

Can I use workflow guardrails to flag unplanned features added during a bug fix?

Workflow guardrails can flag unplanned features by comparing the current git diff against the active plan, quantifying the drift percentage, and recommending whether to continue, pause, or re-scope.

Does scope creep detection work without a pre-existing task plan?

Scope creep detection requires a pre-existing plan loaded from todo state or progress files to extract intended files and exclusions, without which there is no baseline to classify drift against.

What are the limitations of using git diff inspection for scope drift detection?

Git diff inspection limitations include reliance on an accurate active plan for baseline comparison, meaning untracked files or unstructured work without explicit task plans cannot be effectively classified for drift.