os-evolution-planner

Automating plugin evolution planning requires a target and an evolution goal to generate a structured task plan and a Copilot CLI delegation prompt. The workflow brainstorms 2-3 approach options using a cheap model, presents them for selection, and then writes the delegation instructions for the chosen path.

Generating a Copilot CLI delegation prompt is best handled by providing the target plugin name and the evolution goal. The system brainstorms multiple cheap-model approaches, lets you select the optimal one, and outputs a structured task plan paired with the ready-to-run CLI prompt.

Brainstorming cheap-model approaches for skill updates requires defining the target skill and the desired evolution goal. The system automatically generates 2-3 distinct approach options using the cheapest available model and presents them for your selection before drafting the final plan.

Plugin evolution planning can be invoked standalone by providing a target and an evolution goal to produce task plan outputs directly. It is also called by os-architect for Path B update executions or Path C create executions to handle the delegation workflow.

Creating a structured task plan for agent evolution requires you to provide the target agent name and a clear evolution goal. Using these inputs, the system brainstorms 2-3 approaches, prompts you to select one, and outputs the finalized plan with a Copilot CLI delegation prompt.