flutter-senior-orchestration

Flutter Senior Orchestration

Overview

The Flutter Senior Orchestration skill governs end-to-end delivery of Flutter and Dart applications across a 6-state Graph Engineering DAG: silent Cross-AI LLM Wiki memory restoration (context/memory/MEMORY.md), target-project AGENTS.md (<= 90 lines) integration, 3-Tier Dynamic Routing, Capability & Risk-Gated Dispatch in PLAN.md (<= 50 lines per feature), parallel TDD implementation, tiered review (Adversarial Review Committee), Fail-Honest E2E transparency, and milestone memory persistence across Claude Code and Google Antigravity.

When to Use

• Trigger Scenarios:
  • Orchestrating Flutter features, multi-screen flows, widget refactors, state management migrations, 60/120fps jank fixes, or multi-platform store releases.
  • Coordinating capability-gated discovery (ui-ux-designer, flutter-architect), isolated parallel flutter-implementer tracks, and tiered verification (flutter-reviewer, flutter-release-engineer, qa-tester).
• When NOT to Use:
  • Pure backend tasks (python-expert, database-migration-expert) or single-turn Q&A without code edits.

Core Invariants & Artifact Line Budgets

1. Zero Direct Dart Implementation: The orchestrator NEVER edits .dart files (lib/, test/). Direct writes are restricted to PLAN.md, root AGENTS.md, root DESIGN.md, doc/adr/*.md, docs/ (docs/<feature-name>/), .agents/, and context/memory/.
2. Automated Git Branch Governance & Scope Drift: Never work on main, master, develop, or dev. At State 0, inspect git symbolic-ref --short HEAD and auto-branch (git checkout -b feat/<descriptive-slug> or fix/<slug>). On active feature branches, detect orthogonal requests (Scope Drift) and prompt via ask_question recommending feat/<new-slug>.
3. Target-Project AGENTS.md + DESIGN.md + MEMORY.md Integration: In State 0 / State 5, verify root AGENTS.md; if missing or if stack/commands/conventions changed, generate/update a concise root AGENTS.md (<= 90 lines) linking executable commands (flutter analyze, flutter test), root DESIGN.md, and context/memory/MEMORY.md.
4. Strict Conciseness Line Caps:
   • PLAN.md feature block <= 50 lines | Root AGENTS.md <= 90 lines | Root DESIGN.md <= 110 lines
   • Single discovery file docs/<feature-name>/spec.md: ## Product <= 50 (product-analyst) | ## Design <= 30 (ui-ux-designer, screen delta only) | ## Architecture <= 50 (flutter-architect)
   • adr-NNN-*.md <= 55 lines (only for a structural decision) | docs/<feature-name>/test-matrix.md <= 80 lines | docs/<feature-name>/evidence/*.png
   • No review report files: flutter-reviewer, critic, challenger, e2e-blackbox-tester return their verdict in the final message (<= 50 lines: verdict, findings with file:line, required fixes).
   • Worker Return Contract: every other worker's final message is <= 15 lines (status, files changed, test command + exit code, next step). Never ask workers for long narratives.
5. Fail-Honest E2E Transparency: If e2e-blackbox-tester returns BLOCKED or SKIPPED (e.g., mobile-only target without web, server couldn't start, Chromium unavailable), explicitly tell the user in the final summary: "Browser E2E was NOT executed (BLOCKED/SKIPPED): " — NEVER mask it as passed.