mvt-update-plan

You can update task status in a yaml development plan by applying deterministic script-based mutations that change states like done or blocked, then recompute current_tasks while ensuring schema-safe writes to preserve overall workflow state.

Automatic next-step progression works by recomputing current_tasks and plan completion state through a provided update script, immediately surfacing the next executable task and recommended follow-up skill without requiring manual reasoning or file edits.

Yes, you can attach implementation notes and produced artifact files directly to a task update. The Skill records these details on the task entry within the active plan.yaml to ensure full development traceability.

When a change plan finishes inside a larger epic, the Skill supports epic-aware advancement by safely advancing the child change or deferring progression, keeping the broader project state consistent without manual intervention.

Yes, validated session context is required. The Skill relies on active change plan resolution and controlled session state updates to securely manage task transitions, blocker tracking, and epic-linked progression inside the shared workspace.

Automated plan management prevents the risk of breaking workflow state by eliminating manual plan file edits and manual task progression calculations, reliably marking work as done, blocked, or skipped while keeping project flow consistent.