Flutter App Workflow
Deliver a runnable, maintainable result with evidence. Preserve the user's product choices and existing conventions unless migration is explicitly requested.
Preflight
Read project preflight before planning. When the task includes a ticket, read it through the available GitHub integration or CLI, reconcile it with the current code, and state the agreed implementation scope before editing. Treat supplied project facts as preflight evidence; inspect repository constraints (SDK, platforms, packages, architecture, tests, flavors, devices) instead of re-asking. Reuse adequate existing solutions; do not add packages merely for familiarity.
Route specialists
Load only the available specialists needed for the vertical slice:
- Architecture & state:
flutter-architecture, flutter-state-management
- UI & visual:
flutter-ui-design, flutter-visual-effects, or matching UI specialist
- Data, AI & product:
flutter-networking, flutter-persistence, flutter-authentication, flutter-in-app-purchases, flutter-product-analytics, flutter-ai-integration
- Platform & ops:
flutter-package-development, flutter-notifications, flutter-background-execution, flutter-dependency-upgrades, flutter-observability, flutter-runtime-debugging
- Language & security:
dart-language, dart-concurrency, flutter-security, flutter-code-review
- Quality & delivery: testing, accessibility, performance, CI/CD, release, device specialists
If a specialist is unavailable, continue with this workflow's preflight and vertical-slice rules; do not claim it was loaded or silently install skills. Hand focused work (e.g. form validation, API cache) to dedicated specialists rather than running this workflow.
Deliver in vertical slices
- Define user-visible behavior and acceptance evidence.
- Choose the smallest architectural change fitting the existing project.
- Implement one coherent path through model, data, state, and UI.
- Add focused tests with the behavior, not after an unrelated rewrite.
- Run narrow checks after each slice and follow delivery verification, including evidence labels and scoped Git handoff.
Keep files cohesive and domain-oriented. Do not split files solely for line counts.
Stop conditions
Do not claim completion while required checks fail. If credentials, devices, or backends block verification, report what was verified and what remains blocked.
Sources
1---2name: flutter-app-workflow3description: Coordinate end-to-end delivery of a complete Flutter app or feature across UI, state, data, tests, and runtime verification. Use for broad vertical-slice ownership; not for data-only sync/cache, one screen or form, or contained work that merely touches multiple files or two domains.4---56# Flutter App Workflow78Deliver a runnable, maintainable result with evidence. Preserve the user's product choices and existing conventions unless migration is explicitly requested.910## Preflight1112Read [project preflight](references/project-preflight.md) before planning. When the task includes a ticket, read it through the available GitHub integration or CLI, reconcile it with the current code, and state the agreed implementation scope before editing. Treat supplied project facts as preflight evidence; inspect repository constraints (SDK, platforms, packages, architecture, tests, flavors, devices) instead of re-asking. Reuse adequate existing solutions; do not add packages merely for familiarity.1314## Route specialists1516Load only the available specialists needed for the vertical slice:17- Architecture & state: `flutter-architecture`, `flutter-state-management`18- UI & visual: `flutter-ui-design`, `flutter-visual-effects`, or matching UI specialist19- Data, AI & product: `flutter-networking`, `flutter-persistence`, `flutter-authentication`, `flutter-in-app-purchases`, `flutter-product-analytics`, `flutter-ai-integration`20- Platform & ops: `flutter-package-development`, `flutter-notifications`, `flutter-background-execution`, `flutter-dependency-upgrades`, `flutter-observability`, `flutter-runtime-debugging`21- Language & security: `dart-language`, `dart-concurrency`, `flutter-security`, `flutter-code-review`22- Quality & delivery: testing, accessibility, performance, CI/CD, release, device specialists2324If a specialist is unavailable, continue with this workflow's preflight and vertical-slice rules; do not claim it was loaded or silently install skills. Hand focused work (e.g. form validation, API cache) to dedicated specialists rather than running this workflow.2526## Deliver in vertical slices27281. Define user-visible behavior and acceptance evidence.292. Choose the smallest architectural change fitting the existing project.303. Implement one coherent path through model, data, state, and UI.314. Add focused tests with the behavior, not after an unrelated rewrite.325. Run narrow checks after each slice and follow [delivery verification](references/delivery-verification.md), including evidence labels and scoped Git handoff.3334Keep files cohesive and domain-oriented. Do not split files solely for line counts.3536## Stop conditions3738Do not claim completion while required checks fail. If credentials, devices, or backends block verification, report what was verified and what remains blocked.3940## Sources4142- [Flutter app architecture](https://docs.flutter.dev/app-architecture)43- [Flutter testing](https://docs.flutter.dev/testing)44- [Dart and Flutter MCP server](https://docs.flutter.dev/ai/mcp-server)45- [Supported platforms](https://docs.flutter.dev/reference/supported-platforms)
thiennc-tesoglobal