gemini-cli-conductor

To automate feature development with the Gemini CLI, this Skill runs a single interactive subprocess, pipes your task objectives and context into stdin, and bridges JSON events to dynamically synthesize LLM responses.

The interactive subprocess handles LLM responses by parsing JSON objects emitted from the stream and synthesizing dynamic responses to unblock the Gemini CLI during ask_user tool calls.

Yes, you can bridge user intentions to the Gemini CLI by piping task objectives and context upfront into stdin, which executes one continuous process for the entire feature development lifecycle.

The best way to manage context for Gemini CLI tasks is to pipe task objectives directly into the subprocess upfront, ensuring the single-spawn interactive stream maintains continuous lifecycle context.

The Gemini CLI requires an environment that supports spawning an interactive subprocess to execute the single-spawn stream, allowing it to parse JSON events and synthesize dynamic responses for unblocking.

The Gemini CLI needs synthesized responses during ask_user tool calls to dynamically unblock the automation process, allowing the interactive subprocess to continue executing the feature development workflow without manual input.