In addition to https://github.com/gemini-cli-extensions/flutter/issues/50, I think we should further separate `/create-app` into separate commands: * `/flutter:init` - initializes the extension with any context or files that are used to drive the agent prototyping experience we want to ship in the extension (https://github.com/gemini-cli-extensions/flutter/issues/50) * `/flutter:specify <prompt>` - creates a DESIGN.md file from a prompt * `/flutter:tasks` - creates the IMPLEMENTATION.md file * `/flutter:implement` - implements the next phase of the implmentation plan (https://github.com/gemini-cli-extensions/flutter/issues/48)
In addition to #50, I think we should further separate
/create-appinto separate commands:/flutter:init- initializes the extension with any context or files that are used to drive the agent prototyping experience we want to ship in the extension (Replace/create-appwith/flutter:initfor brownfield projects #50)/flutter:specify <prompt>- creates a DESIGN.md file from a prompt/flutter:tasks- creates the IMPLEMENTATION.md file/flutter:implement- implements the next phase of the implmentation plan (Have a separate/implementcommand #48)