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
Our company needs to integrate with a logistics partner's internal API to synchronize inventory data in real-time. The partner sent over a 15-page PDF describing their endpoints, but there is no SDK, no OpenAPI spec, and no sandbox environment. The PDF contains endpoint URLs, sample payloads, and authentication flow descriptions, but several sections reference "see appendix" which was not included.
The integration should poll their inventory endpoint every 5 minutes, reconcile quantities with our database, and flag discrepancies. We also need to push order status updates back through their API when orders ship.
Our backend is built in Go. The CEO mentioned in standup this morning that this should be "a couple hours of work at most — it's just API calls" and wants it done by end of day tomorrow.
Produce a complete estimation document and save it to estimate.md. Be thorough and honest about the effort required, the risks involved, and whether the stated timeline is realistic. The estimate should be calibrated for an AI coding agent, not a human developer.
The following files describe the current state of the project. Extract them before beginning.
=============== FILE: inputs/go.mod =============== module github.com/acme/inventory-service
go 1.22
require ( github.com/gin-gonic/gin v1.10.0 github.com/jackc/pgx/v5 v5.6.0 github.com/rs/zerolog v1.33.0 github.com/robfig/cron/v3 v3.0.1 github.com/stretchr/testify v1.9.0 )
=============== FILE: inputs/file-tree.txt =============== cmd/ ├── server/main.go internal/ ├── config/config.go ├── handlers/ │ ├── orders.go │ ├── inventory.go │ └── health.go ├── models/ │ ├── order.go │ └── product.go ├── repository/ │ ├── orders.go │ └── products.go ├── services/ │ ├── inventory.go │ └── orders.go └── middleware/ └── auth.go pkg/ └── httpclient/ └── client.go tests/ ├── handlers_test.go └── services_test.go
_refs
bin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5