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 team is planning the next sprint for a TypeScript/Next.js SaaS application. We need estimates for 5 features so we can decide what fits in a 2-week sprint. The application uses Next.js 14 with App Router, Prisma ORM with PostgreSQL, NextAuth for authentication, and Tailwind CSS with shadcn/ui components.
Please estimate all 5 features together and produce a consolidated view that helps us prioritize and sequence the work.
Produce a single consolidated estimation document and save it to estimate.md. The document should contain a summary table comparing all tasks, individual estimates, and guidance on sequencing. All estimates should be calibrated for an AI coding agent.
The following files describe the current project and the 5 features to estimate. Extract them before beginning.
=============== FILE: inputs/package.json =============== { "name": "projecthub", "version": "3.2.0", "dependencies": { "next": "14.2.8", "react": "18.3.1", "@prisma/client": "^5.17.0", "next-auth": "^4.24.0", "tailwindcss": "^3.4.0", "zod": "^3.23.0", "@tanstack/react-query": "^5.51.0", "date-fns": "^3.6.0", "resend": "^3.4.0" }, "devDependencies": { "typescript": "^5.5.0", "prisma": "^5.17.0", "vitest": "^2.0.0" } }
=============== FILE: inputs/file-tree.txt =============== src/ ├── app/ │ ├── layout.tsx │ ├── (auth)/login/page.tsx │ ├── dashboard/ │ │ ├── page.tsx │ │ └── projects/[id]/page.tsx │ └── api/ │ ├── auth/[...nextauth]/route.ts │ ├── projects/route.ts │ └── users/route.ts ├── components/ │ ├── ui/ (shadcn) │ ├── ProjectCard.tsx │ └── UserAvatar.tsx ├── lib/ │ ├── prisma.ts │ ├── auth.ts │ └── email.ts prisma/ └── schema.prisma tests/ └── api/projects.test.ts
=============== FILE: inputs/feature-1.md ===============
Allow project owners to invite team members by email. The invited user receives an email with a link to join. If they don't have an account, the link takes them to signup first, then auto-joins the project. Show pending invitations on the project settings page.
=============== FILE: inputs/feature-2.md ===============
Add an activity feed to each project page showing recent actions: task created, task completed, member joined, comment added. Show the actor, action, and timestamp. Paginate with infinite scroll. Store events in a dedicated table.
=============== FILE: inputs/feature-3.md ===============
Add a dark mode toggle to the settings page. Persist the preference per user. The app already uses Tailwind and shadcn/ui.
=============== FILE: inputs/feature-4.md ===============
Add a button on the project page to export all tasks as CSV. Include task name, status, assignee, created date, and due date. The export should respect the current filters applied on the page.
=============== FILE: inputs/feature-5.md ===============
Currently all project members have the same access. Add three roles: Owner, Editor, Viewer. Owners can manage members and settings. Editors can create and edit tasks. Viewers can only read. Enforce permissions on both frontend (hide UI) and backend (API validation).
_refs
bin
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5