ase-task-estimate

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

$ARGUMENTS

@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md

Procedure

Derive the scores of the plan (the body only, never the frontmatter or backmatter), skipping every bullet-point in the inert checkbox states [-] and [>] entirely, while all other checkbox states (including [x], as the effort covers the entire lifecycle of the task) count alike. A bullet-point without a type (like in a legacy plan) counts with the types following from its section: DOM or IFC for a context or specification section (but nothing for a pure rationale like a why), ARC or IMP for a changes or design section, and REG or CON for a verification section. Do not output anything.

1. Attention score: set to the sum of the weights of all counted bullet-points, with the weights DOM 5.0, IFC 4.0, ARC 3.0, IMP 1.0, REG 0.5, and CON 1.0, each multiplied by the item count of the bullet-point: the number of distinct requirements, behaviors, or changes it states (at least 1), like one per independent statement or per enumerated element, so a dense bullet-point stating ten key bindings counts ten times, while a bullet-point stating a single fact counts once. Set to times .

2. Volume score: predict the code impact of the counted ARC and IMP bullet-points strictly read-only from the plan and the code base (never change, stage, or commit anything), disregarding any already existing change set of the task (its uncommitted changes, its branch, or its change set attachment): never measure the volume from such a change set, so estimations before and after the implementation stay comparable. Set to the number of files they touch (or create) -- the files named by the bullet-points plus the files following from them, like call sites, documentation, manual pages, and generated catalogs -- and to the estimated number of changed lines, sizing new files after comparable existing ones and changes after the code they touch, and to the part of in newly created files. Set to times plus plus twice times , so a newly written line weighs three times a changed one. As a plan describes the straightforward path only, while the edge cases, the error handling, and the polishing of the realization regularly multiply its size, already covers this growth, hence do not inflate the predicted lines themselves.

3. Base size: set to plus , and set to the smallest size of XS, S, M, and L whose upper band bound in is greater than or equal to , or to XL if exceeds all bounds.

1. Determine Operation:

   1. Set to the whitespace-separated tokens of , each with a trailing : removed. Inherit the always existing , , , and from the current context. Do not output anything.

   2. Validate the arguments and options:

      • If a token of does not match the regexp ^[a-zA-Z0-9#][a-zA-Z0-9#_-]*$, only output the following and then immediately STOP processing the entire current skill: