task-plan-normalizer

To normalize raw task input, the skill analyzes issue context, PR details, and repo profiles to extract requirements and generate a structured JSON execution plan. This process ensures deterministic, safe task execution before initiating any automated code changes.

Task planning prevents errors in unattended operations by evaluating task feasibility, scope, and potential risks before execution. It transforms ambiguous requests into clear execution plans, preventing accidental data loss or incorrect modifications during headless automated workflows.

Yes, you can use this skill to assess feasibility and scope before running automated code changes. It evaluates the request to determine if the task should proceed, needs human clarification, or is blocked, ensuring a safe and defined execution path.

The best way to handle ambiguous tasks in automated workflows is converting them into structured JSON plans. This skill normalizes underspecified input by detailing the decision, plan, assumptions, and stop conditions for predictable outcomes.

When a task is blocked or needs human clarification during execution plan generation, the skill explicitly refuses to proceed. It outputs a structured JSON decision detailing whether the task should proceed, needs human intervention, or is blocked.

You should not use automated task normalization when a task lacks sufficient issue context, PR context, or repo profile data. The skill requires these inputs to extract requirements, assess feasibility, and generate a safe, deterministic execution plan.