Estimates implementation time for web development tasks (frontend and/or backend) by analyzing the existing codebase and calibrating for an AI coding agent as executor — not a human developer. Use when the user asks about effort, sizing, or feasibility: 'how long', 'how much work', 'estimate this', 'what is the effort', 'breakdown this task', 'can we do this in X days', 'is this a big task', 'how complex is', 'what's involved in', 'fits in the sprint', 'rough sizing', 't-shirt size', 'story points'. Also use when the user describes a feature and implicitly wants to know scope — e.g. 'we need to add X to the app', 'thinking about building Y', 'is this feasible by Friday'. Supports batch estimation from any structured source (BMAD output, spec folders, PRDs, backlogs, task lists) — use when the user mentions 'estimate the stories', 'estimate the epic', 'scan the backlog', 'estimate all tasks', 'estimate the specs', or points to a folder of task/story/spec files.
95
94%
Does it follow best practices?
Impact
98%
1.40xAverage score across 5 eval scenarios
Passed
No known issues
A client is evaluating whether to build a real-time notification system for their web application. They want push notifications in the browser, an in-app notification bell with a dropdown showing recent notifications, read/unread status tracking, and the ability to configure notification preferences per user.
The client has not shared access to their codebase. They mentioned it's "a standard web app" but haven't specified the framework, language, or database. They want a rough idea of effort before deciding whether to move forward.
No project files, repository access, or technical details are available beyond what's described above.
Produce an estimation document and save it to estimate.md. Since no codebase is available to review, be explicit about the limitations of the estimate and how much the actual effort might differ once the codebase is analyzed. The estimate should be calibrated for an AI coding agent.
_refs
bin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5