skills.rest
gonz0w
gonz0wCOMMUNITY
Explore all skills by this author →
Website𝕏@gonz0wGitHub

planner-scope-estimation

Calculate per-task context estimates and enforce budget rules for planner plans.

1|Updated Feb 22, 2026
Search Tags:#planning#parallelization#scope#planner#task-splitting#context-budget#depth-calibration
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill planner-scope-estimation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planner-scope-estimation
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/planner-scope-estimation
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill planner-scope-estimation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning workloads can exhaust context windows; this skill defines quantitative rules to size plans and manage context budgets.

Core Features & Use Cases

  • Context budgeting rules for planners (50% target, 2-3 tasks per plan)
  • Split signals and depth calibration to guide task breakdown and parallelization
  • Per-task context impact estimates by file count and complexity to optimize plan scope
  • Use case: apply to a new feature to estimate scope and decide wave structure

Quick Start

Initiate a plan by applying the planner-scope-estimation rules to determine a 2-3 task scope within a ~50% context budget.

Frequently Asked Questions about planner-scope-estimation

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

FAQPage Schema
How do I prevent context window exhaustion during complex planning phases?▼

Context window exhaustion during planning is prevented by calculating and enforcing context budget rules, maintaining a 50% target limit, and restricting scope to 2-3 tasks per plan.

What is the best way to estimate context budget for a new feature plan?▼

The best way to estimate context budget for a new feature plan is to calculate per-task context impact using file count and complexity metrics to determine the overall scope and wave structure.

How do I use split signals to guide task breakdown and parallelization?▼

Split signals guide task breakdown and parallelization by providing depth calibration across simple to complex plans, triggering task-splitting when context estimates exceed the defined budget threshold.

Can I apply depth calibration to simple plans without over-splitting tasks?▼

Yes, you can apply depth calibration to simple plans because the rules scale across simple to complex scopes, providing structured guidelines that prevent over-splitting while maintaining a 2-3 task scope.

Why does my planner exceed the context limit when processing large task breakdowns?▼

Your planner exceeds the context limit because it lacks quantitative context budget rules; applying scope estimation constraints limits plans to 2-3 tasks within a 50% context budget to prevent exhaustion.

Related Skills

Explore More Product & Management Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
shakestzdshakestzd
3

htmlgraph:execute

Execute parallelized development plans with Git worktrees and quality gates.

Community
Advanced
PorkbuttsPorkbutts
1

task-decomposition

Generate epics, user stories, and atomic tasks from PRD and architecture documents.

Community
Intermediate
abhishekdutta18abhishekdutta18

token-budget-advisor

Estimate response token counts and suggest depth levels for AI conversations.

Community
Intermediate