/scope

Compare feature lists against the brief and generate a scope health report.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/fnkydcks-lab/dt-foundry --skill scope-fnkydcks-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /scope
Source: https://github.com/fnkydcks-lab/dt-foundry/tree/main/scope
Command: npx skills add https://github.com/fnkydcks-lab/dt-foundry --skill scope-fnkydcks-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Holds the line on project scope by auditing features against the brief and halting drift when the build diverges from agreed goals.

Core Features & Use Cases

  • Compare current feature list to the brief and flag drift.
  • Propose decisions to keep work within scope, including what to defer or cut.
  • Generate a scope health report to dt-foundry/scope.md with a timestamp.

Quick Start

Run the scope review to compare the current feature list with the brief and generate a scope health report.

Frequently Asked Questions about /scope

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

FAQPage Schema
How do I prevent scope creep during a development sprint?

Prevent scope creep by validating the current feature list against the original brief. The scope review applies deterministic checks via scripted comparisons to flag drift and document decisions on what to defer or cut.

What is a scope health report and how does it track project drift?

A scope health report tracks project drift by documenting the divergence between implemented features and agreed goals. It records proposed decisions to keep work within scope and writes the results to a timestamped file.

How do I compare my feature list to the project brief automatically?

Compare your feature list to the project brief automatically by running scripted comparisons. The review process audits current features against the brief, flags any misalignment, and proposes decisions to keep the build aligned.

Can I use scope validation for feature evolutions or only new builds?

Scope validation applies to both new development sprints and feature evolutions. Any time project drift must be flagged, documented, and decisions recorded, the validation process holds the line on agreed goals.

Where does the scope review output its drift analysis report?

The scope review outputs its drift analysis report to dt-foundry/scope.md. The generated file includes a timestamp and documents the scope health status along with proposed decisions for the build.

What is the best way to document decisions when deferring features?

The best way to document decisions when deferring features is to generate a scope health report. It records the choices made to keep work within the original brief and writes them to a timestamped file for future reference.