← ClaudeAtlas

estimatelisted

Derive user stories and a day-based, uncertainty-aware effort estimate from a Requivo session's model, in this Claude session, and save both as tracked artifacts against one revision. Use when the user wants an effort estimate for the current scope.
jbkkz/requivo · ★ 3 · AI & Automation · score 72
Install: claude install-skill jbkkz/requivo
# /requivo:estimate Produce a **day-based effort estimate**, one entry per user story — stories first, because the estimate is reasoned against them, and #519 (`decision: the-estimate-graduates`) saves both together against one revision: the estimate's provenance is incomplete without the stories it rests on. **You** do the estimation; Requivo tracks both documents. This mirrors `src/requivo/assets/prompts/stories.md` + the `Stories` contract, and `assets/prompts/estimate.md` + `EstimateDraft`, at commit `969cfd9` — the same two calls `requivo estimate` makes, restated here because the plugin cannot import those files at runtime (`decision: plugin-skills-mirror-a-pinned-cli-commit`). Read `${CLAUDE_PLUGIN_ROOT}/REASONING.md` unless you already hold it from an earlier `/requivo:*` in this conversation — and read it again whenever you are unsure you still do. ## 0. Preflight Run the shared **preflight** from REASONING.md before anything else: `requivo doctor --json`, checking whether the command ran *at all* rather than what it reported. If it could not run, the `requivo` CLI is not installed — follow REASONING.md's missing-CLI flow. Nothing has been saved at this point, so there is no half-written estimate to find. ## 1. Load the model ``` requivo model show <slug> requivo status <slug> --json ``` Note the `revision` — call it `N`. Both documents you write below are tied to this one revision, per invariant 12: one snapshot, two files. ## 2. Reason → stories, then the estim