uninterrupted-execution-planner

To create a task agreement, this skill normalizes your specifications into a persistent `.agent/tasks/TASK.md` file, defining acceptance criteria, milestones, and error escalation policies before implementation begins.

Formalizing acceptance criteria and milestones prevents scope creep and misunderstandings by establishing a clear, agreed-upon contract with verification steps and error escalation policies before any implementation starts.

The best way to document task verification and error policies is generating a standardized `TASK.md` agreement that maps evidence to milestones and defines closure checks for long-running work.

Yes, this skill performs input normalization to integrate your existing tickets, specifications, or notes directly into the standardized `.agent/tasks/TASK.md` task agreement structure.

You need a formal task agreement when starting major feature development to ensure alignment between stakeholders and the development agent, enforcing sections like Objective, Verification, and Evidence Mapping.

A normalized task agreement requires Objective, Acceptance Criteria, Milestones, Verification, Error Policy, and Evidence Mapping sections, ensuring all required components are present before implementation handoff.