What problem does it solve? Estimating how long a feature will take is error-prone when done from memory or a quick skim of the spec. This Skill applies Codeleap's official "Process: How to Estimate" workflow end to end: it reads the full Notion Feature Spec, checks technical specs and real code in the repository, maps the flow, surfaces hidden coupling and edge cases, and produces a justified line-item estimate in dev days (1 dev day = 8 hours). ## Core Features & Use Cases - Spec-driven estimation: Reads a Notion Feature Spec (or pasted text), classifies ambiguities as blocking questions or additive line items, and asks all blocking questions in a single round before finalizing numbers. - Codebase-grounded analysis: Explores the actual repositories per area (Mobile/Web/Backend) to confirm reuse, hidden coupling, and risks, citing real evidence instead of guessing. - Structured output across 5 areas: Always breaks work into Mobile, Web, Backend, QA, and Design line items with per-item justification, additive items, and risk buffers shown separately from the base total. - Use Case: Paste a Notion Feature Spec URL and ask "how many dev days will this take" — the Skill reads the spec, explores the code, asks clarifying questions, and returns a per-area estimate table in the chat, optionally filling the spec's Calculator database only if explicitly requested. ## Quick Start Estimate how many dev days this Notion Feature Spec will take, checking the codebase for reuse before giving me the numbers.
