planlisted

Use the current user request as this skill's input. In Claude Code invoke it as `/ufil:plan`; in Codex invoke it as `$ufil:plan`. Resolve `UFIL_ROOT` to the plugin root containing this skill; Claude Code may provide `CLAUDE_PLUGIN_ROOT`, while Codex can resolve it from the installed skill path. Use the client's native subagent capability; do not hardcode one client's tool call schema. Analyze a GitHub issue/ticket and create a detailed Flutter implementation plan BEFORE coding. Arguments: <requested arguments> (GitHub issue ID, e.g., `123` or `issues/123`) ## Step 0: Initialize Serena + Read docs (MANDATORY) ### 0a. Initialize Serena (auto-onboard if needed) Run in order: 1. Call `mcp__serena__initial_instructions` — load Serena's instructions manual. 2. Call `mcp__serena__check_onboarding_performed` — check whether this project has been onboarded. 3. **If not onboarded:** - Probe for analyzable code: `find . -maxdepth 3 -type f -name '*.dart' -not -path '*/.*' | head -1` - If a Dart file is found → call `mcp__serena__onboarding` to build the symbol index and project memories (one-time cost per project). - If empty → SKIP onboarding, fall back to built-in search and read tools. Inform the user: "Serena onboarding skipped — no Dart code detected. Will auto-run the next time the plan or implement workflow is invoked after code exists." 4. **If already onboarded:** proceed. Use Serena tools throughout planning for code exploration and symbol lookup. To force re-o