---
name: full_scope_first_sizing
title: "Full Scope First Sizing"
description: "Size builds, scans, listings and cadences at the full scope the work actually needs first, and shrink only on a measured limit, so the user never has to push back against a conservative first pass."
version: 1.0.0
author: Script Master Labs LLC
license: MIT
source: https://scriptmasterlabs.com/hive402-skills/full_scope_first_sizing/SKILL.md
registry: HIVE402 Skills (https://scriptmasterlabs.com/hive402-skills)
---

# Full Scope First Sizing

## Size to the real need first

- Start every build, scan, listing and schedule at the full scope the work actually needs, covering every item, name, page or channel in scope rather than a safe subset.

- Set cadence, coverage and counts from the value the user asked for, so a monitoring job runs as often as the signal changes and a catalog job lists the whole catalog.

- Treat a smaller first pass as a decision that needs its own justification, never as the default safe choice.

## Make the full scope cheap before shrinking it

- Redesign the work so the full scope fits the real limits before cutting scope, for example by caching slow reads, batching calls and reusing data already fetched in the same run.

- Check the actual cost and rate limits of the full scope against the source that enforces them before claiming the full scope is too expensive.

- Ask what the constraint actually is when the user says a run costs nothing or owns the capacity, and resize to that answer instead of defending the smaller design.

## Shrink only on a measured limit

- Reduce scope only after a measured limit binds, such as a verified rate cap, a proven timeout or a hard platform quota, and name the measured limit in the report.

- Keep the cut as narrow as the limit forces, and restore the full scope automatically when the limit clears or the design gets cheaper.

- Never present a reduced count, a slower cadence or a partial list as the finished scope without naming what was cut and why.

## Verify the shipped scope matches the plan

- Count what actually shipped against the full scope before reporting done, and report both numbers when they differ.

- Own a conservative first pass in one sentence when the user catches one, resize in the same run, and verify the new scope live rather than promising it.

- Carry the corrected scope into the saved job instructions or plan the work came from, so the next run starts at the full scope instead of relearning the correction.

## Alternatives for better results

- Phase a genuinely large scope into verified chunks that together still cover the whole scope, instead of quietly dropping the tail.

- Put the price and value question last when shaping an offer, loading the full value the audience needs first and adjusting price afterward.


---

## From Script Master Labs

This skill is listed in [HIVE402 Skills](https://scriptmasterlabs.com/hive402-skills) —
every skill there passed a verification gate before listing: parsed, safety-scanned,
provenance recorded, self-contained. Skills, probed before listed.

Script Master Labs also runs [HIVE402](https://hive402.scriptmasterlabs.com), the
payability-probed catalog of 132 paid agent APIs, [OMNIGATE](https://scriptmasterlabs.com/omnigate-facilitator),
the x402 gateway those payments settle through, and the free
[x402 Starter Kit](https://scriptmasterlabs.com/x402-kit).