plan-sync

You can automatically update a plan document by analyzing conversation context and codebase changes like git diffs. This Skill marks tasks complete, adds new ones, and removes obsolete items in your markdown plan files.

Synchronizing project plans with implementation works by reading conversation history and analyzing code changes via git, grep, and glob tools. It then rewrites markdown plan files to accurately match actual development progress.

Yes, you can use this to track user stories in markdown after a coding session. It applies to software development workflows for maintaining accurate task tracking by updating existing plan documents with evidence-based changes.

You need tools for reading conversation history and analyzing code, which includes git, grep, and glob. These dependencies are required to gather the evidence needed for updating your plan documents accurately.

The best way to keep task tracking accurate is to use evidence-based synchronization. This Skill backs all plan updates with evidence from conversation logs and code changes, ensuring your plans reflect actual progress without manual effort.

Obsolete tasks may remain if the Skill cannot gather sufficient evidence from conversation logs or codebase changes. It relies on analyzing conversation context and code via git, grep, and glob to identify and remove outdated tasks.