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.
• Do not edit behavior whose requirement or ownership remains materially ambiguous.
• 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.
• After exhausting available evidence, give a compact understanding checkpoint covering:
  • current and intended behavior, evidence versus hypotheses
  • in-scope work and affected shared consumers
  • data contracts, time, or localization semantics
  • tests and platforms outside scope
  • inspection that can continue