dan:unify

To generate a summary of completed plan execution, you can run a workflow that reads your PLAN.md and task commits to assemble a comprehensive SUMMARY.md, while simultaneously updating STATE.md and ROADMAP.md to reflect progress and decisions.

Closing execution loops in markdown involves capturing deviations and consolidating execution evidence by generating a SUMMARY.md that satisfies frontmatter metadata requirements and transitions the plan status in your project files.

To update a roadmap file after a plan phase is completed, the workflow reads executed plans and task commits to advance the project state, writing metrics and decisions into ROADMAP.md without spawning additional agents.

No dependencies are required for this plan management workflow to consolidate git commits; it executes in-session to read task commits and write summary records directly into your markdown project files.

This execution tracking process is applicable only to phases where plans have already been executed, deviations identified, and a consolidated record is required to close the loop on the completed work.

Your plan management workflow needs frontmatter metadata in the summary file to satisfy standard accounting requirements, ensuring task and file tracking data are systematically captured during the plan status transition.