skills.rest
vh2224
vh2224COMMUNITY
Explore all skills by this author →
GitHub

forge-scope-clarity

Extract commitments and classify milestone items into IN, OUT, DEFERRED, or UNCLEAR.

3|Updated Apr 8, 2026
Search Tags:#production#verification#milestones#scope#criteria#observable
One-click install
npx skills add https://github.com/vh2224/forge-agent --skill forge-scope-clarity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-scope-clarity
Source: https://github.com/vh2224/forge-agent/tree/main/skills/forge-scope-clarity
Command: npx skills add https://github.com/vh2224/forge-agent --skill forge-scope-clarity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in milestone scope often leads to scope creep, misaligned expectations, and rework. This skill helps teams define a clear, observable contract for what is IN, OUT, and DEFERRED, with built-in verification.

Core Features & Use Cases

  • Extract explicit commitments, implied commitments, and anti-requirements from milestone descriptions.
  • Classify items into IN, OUT, DEFERRED, or UNCLEAR using the scope razor method, with rationale.
  • Produce observable success criteria that are verifiable by automation or tests, and provide a ready-to-share scope document.

Quick Start

Create a scope contract for your milestone by extracting commitments from the milestone description, applying the scope razor, and writing verifiable IN/OUT/DEFERRED items to M###-SCOPE.md.

Frequently Asked Questions about forge-scope-clarity

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

FAQPage Schema
How do I turn vague milestone descriptions into testable scope?▼

You can prevent milestone scope creep by classifying commitments into IN, OUT, DEFERRED, and UNCLEAR categories, providing clear rationale for each item to align team expectations and reduce rework.

How do I write observable success criteria for project milestones?▼

Observable success criteria are written by extracting anti-requirements and implied commitments from milestone context, then specifying conditions for each IN item that can be verified by automation or tests.

How do I generate a markdown scope contract for milestone verification?▼

Generate a markdown scope contract by applying the scope razor to milestone commitments and writing verifiable IN, OUT, and DEFERRED items with open questions into a structured scope document.

Can I use scope classification to prevent scope creep in product management?▼

Yes, scope classification prevents scope creep by applying a scope razor to explicitly mark items as OUT or DEFERRED, establishing a clear boundary against anti-requirements and unrequested features.

What is the scope razor method for milestone planning?▼

The scope razor method for milestone planning is a classification technique that evaluates extracted commitments and anti-requirements, sorting them into IN, OUT, DEFERRED, or UNCLEAR categories with documented rationale.

Related Skills

Explore More Product & Management Skills→
NlightNFotisNlightNFotis
2

communication-pragmatics

Analyze engineering text for pragmatic meaning and implied commitments.

Community
Advanced
songyinggohsongyinggoh

phase-verify

Analyze PLAN.md criteria and run automated codebase checks to generate verification reports.

Community
Advanced
musher-devmusher-dev

shaping-writing-milestones

Generate milestone map documents defining project phases with exit criteria and sequencing.

Official
Intermediate
Nhqvu2005Nhqvu2005
54

project-management-assistant

Analyze feature scope against timelines and generate phased milestone plans.

Community
Intermediate