feat(plan): budget tasks by tool-call estimate, not row count#174
Merged
Conversation
Add Step 2d budget heuristic to /plan: classifies each task by cost class (trivial/bounded/judgmental/exploratory), estimates tool-call ops, force-splits or DP-flags tasks exceeding 50 ops, and emits a Budget Table in the plan artifact's Wave Structure section. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
13 tasks
…plit-row example - SKILL.md: remove 'Implementation helper' line (LLM cannot execute TS at runtime) - budget.ts: delete unused OpsRange interface and OPS_RANGE export (dead public API) - plan-template.mdx: add placeholder row showing YES split case Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/plan: each task is classified by cost class (trivial/bounded/judgmental/exploratory) and an ops estimate is computed from items × class mid-pointestimated_total_ops > 50are force-split or presented as DP(A) before the plan is finalizedFiles changed
plugins/dev-core/skills/plan/SKILL.md— Step 2d budget heuristic, class table, force-split rule, artifact formatplugins/dev-core/skills/plan/references/plan-template.mdx— Budget Table section added to Wave Structureplugins/dev-core/skills/plan/lib/budget.ts— classifier helper (classifyTask,computeBudget,renderBudgetTable,SPLIT_THRESHOLD)plugins/dev-core/skills/plan/__tests__/budget.test.ts— 16 vitest tests covering all exportsAcceptance checklist
/planStep 2d emits per-task ops estimatedev-process.mdxnot present in this repo — no edit neededCoupling note
Issue #169 (
/framepremise-validity gate) is in parallel. This PR does not touch frame skill files or~/.claude/shared/*. Ifglobal-patterns.md§6 needs an update to reference the 50-op budget threshold, flag as follow-up.Closes #168