scope

Audit git diff changes against the active project plan.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LayerDynamics/Lore --skill scope-layerdynamics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/scope
Command: npx skills add https://github.com/LayerDynamics/Lore --skill scope-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code changes align with the project's active plan, preventing scope creep and maintaining development focus.

Core Features & Use Cases

  • Scope Verification: Compares current git changes against a defined project plan.
  • Drift Detection: Identifies out-of-scope modifications and tracks task completion.
  • Use Case: After implementing a feature, use this Skill to confirm that only the planned files were modified and that all planned tasks have corresponding commits.

Quick Start

Run a scope audit comparing the current git diff against the active plan.

Frequently Asked Questions about scope

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

FAQPage Schema
How do I check my git diff against a project plan for scope creep?

To check git diff for scope creep, audit the current changes against the active project plan. This process compares git diff output with file paths in the plan document to identify in-scope and out-of-scope modifications, preventing unplanned drift.

What is code drift detection in a git workflow?

Code drift detection in a git workflow identifies out-of-scope modifications by comparing git diff output against the active project plan. It categorizes modified, created, and deleted files to assess task progress and report unplanned changes.

How do I verify task completion status using git diff?

Verify task completion status by auditing the git diff against the most recent project plan. The audit assesses task progress by matching modified, created, and deleted files with the planned file paths to confirm all tasks have corresponding commits.

Can I audit modified and deleted files against a plan document?

Yes, you can audit modified and deleted files against a plan document. The audit compares the git diff output with file paths listed in the most recent plan to categorize changes and report in-scope versus out-of-scope modifications.

What is the best way to prevent scope creep during code review?

The best way to prevent scope creep during code review is to audit the git diff against the active project plan. This verifies that only planned files were modified and tracks task completion to maintain development focus.