Evolution & Improvement

Scope

Prepare a prioritized improvement path for the requested project or area. Separate demonstrated defects from proposed new capabilities and uncertain opportunities.

Procedure

1. Inspect the relevant product/runtime paths, defining rules, existing validation and constraints. Use supplied goals as authority for new behavior.
2. Identify concrete correctness, usability, data, delivery or performance outcomes. State assumptions where traffic, business priority or capacity is unmeasured.
3. Compare impact, risk, effort and dependencies at the level the evidence supports. Do not invent numerical estimates or fill arbitrary phases.
4. Group compatible changes into independently useful stages; preserve migrations and rollout order where contracts overlap.
5. Recommend a direction for each actionable item. Explain alternatives when an unresolved decision genuinely needs a comparison.

Result

Use the requested format and planning horizon. Include the baseline/constraints, desired outcomes, ordered work, acceptance and verification, dependencies and material decisions. Save a plan file only when requested or when updating an existing plan. No separate audit, task creation or background run is mandatory.

Separate committed next work from optional opportunities. When an item is selected for execution, pass its chosen outcome, constraints and dependency evidence to Task Shaping and Validation & Clarification. Do not let an unmeasured benefit or a roadmap priority substitute for a product requirement or an acceptance criterion.