flutter-estimate
/flutter-estimate
Produces an honest, AI-assisted effort and complexity assessment for a Flutter feature or project, including approach class, custom work after the package, backend dependency, native work, platform differences and risks, as ranges with stated assumptions. Use when asked to estimate, scope, assess feasibility or compare options before building.
- Author
- imdanishk ↗
- Repository
- flutter-ai-kit ↗
- Licence
- Apache-2.0
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Produces an honest, AI-assisted effort and complexity assessment for a Flutter feature or project, including approach class, custom work after the package, backend dependency, native work, platform differences and risks, as ranges with stated assumptions. Use when asked to estimate, scope, assess feasibility or compare options before building.
Original author description
Produces an honest, AI-assisted effort and complexity assessment for a Flutter feature or project, including approach class, custom work after the package, backend dependency, native work, platform differences and risks, as ranges with stated assumptions. Use when asked to estimate, scope, assess feasibility or compare options before building.
How it works
- Steps
- Rules
SKILL.md preview
--- name: flutter-estimate description: Produces an honest, AI-assisted effort and complexity assessment for a Flutter feature or project, including approach class, custom work after the package, backend dependency, native work, platform differences and risks, as ranges with stated assumptions. Use when asked to estimate, scope, assess feasibility or compare options before building. license: Apache-2.0 --- # Flutter estimate An estimate for AI-assisted work measures the developer's attention time, not the time the agent spends typing. Give ranges, state assumptions, and never invent precision. ## Steps 1. **Restate the request** in one or two lines, and name anything undefined that changes the size (platforms, offline support, roles, scale, existing backend, design ready or not). Ask the requester up to five questions only when an answer would change the estimate by more than a day. 2. **Classify each part of the request** with one approach class: - Package only - Package plus custom work (say what the custom work is) - Backend-dependent (say which endpoints, data and jobs the backend must provide) - Third-party SDK or vendor (say the vendor, cost model and approval steps) - Native code required (say Android, iOS or both) - Limited or not realistic on Flutter (say what can be achieved instead) 3. **Check the facts that decide it.** Before recommending a package, check its current version, maintenance, platform support and licence on pub.dev, and look for a newer or better-maintained alternative; do not rely on memory. If you cannot check, label the claim unverified. Use the `flutter-feature-notes` skill for the feature, and report the verified date of the entry you used. 4. **Name waits that are not coding time.** If the feature needs store, Firebase or Cloud setup (agreements, billing, identity verification, a closed test, App Review), list each as an elapsed-time blocker, separate from the attention-time range; see `flutter-service-setup` and `flutter-release`. 5. **Name the Android and iOS differences** that change the work (permissions, background limits, store review, entitlements, extensions) as none, minor or significant. 6. **Estimate with the drivers in `references/estimation.md`.** Give a low to high range of attention time per part and in total. Show the assumptions that would move the range. 7. **Report** in this shape (a request for flows or an ordered build plan is `flutter-plan`'s job; when `flutter-plan` calls this skill, return only the ranges per slice): summary line; table (part, approach class, custom work after the package, backend dependency, Android/iOS difference, range); assumptions; risks and unknowns; questions still open; what you would build first to cut the biggest uncertainty. ## Rules - A range with its assumptions is the deliverable. A single number is not. - Say plainly when something is not realistic or depends on a platform owner's approval. - If the team keeps actual times, tell the requester to compare them with this estimate (see `references/estimation.md`) so the ranges improve.
Files in this package (2)
- SKILL.md 3 KB
- references/estimation.md 2 KB
Versions
The database has no other skills named flutter-estimate.
Database snapshot: 13.11.2026 · package version 012b222ee0f3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90estimate
Analyzes a task or GitHub issue and provides effort estimation broken into subtasks with T-shirt sizing, risk assessment, and dependency mapping. Use for sprint planning or before committing to deadlines. - 100effort-assessment
Estimates what an AI opportunity will really take - build effort by pattern, the scarce skills and owners it needs, its dependencies on knowledge, data, platforms and reviewers, and the ongoing run cost after release - as ranges with stated confidence. Use when an opportunity… - 90feature-estimate
Scope and estimate a feature. Two procedures — "init" builds an architecture map of the team's repos through guided questions; "estimate" returns an impact map, risk flags, open questions and a tiered size for a feature given as text, a .md file or a ticket link. Use when asked… - 100effort-estimate-banding
Estimate research effort in coarse calibrated bands instead of false-precision hours, so queue arithmetic stays honest about how wrong the numbers are allowed to be. Use when you rank work by expected value per hour but your hour estimates are guesses you never check - 90scope
Estimate and propose client work from a repo or a brief: deliverables, ranges, assumptions, risks, rate-card price, timeline, a client-ready proposal and an internal estimate. Use when asked to quote, estimate, size a job, write a proposal or SOW, or say how long or how much.… - 100flutter-feature-notes
Looks up how a mobile app feature is built in Flutter (recommended package, what the backend must provide, native Android/iOS setup, custom work after the package, store-review risks, effort range and a verified or unverified status). Use when asked whether a mobile feature is…