devenv-plan-update

To update an implementation plan markdown file surgically, you can mark tasks as complete, append notes, or add single tasks. This enforces a strict three-change limit per invocation to preserve sequential task numbering and maintain revision history.

Yes, you can track GitHub issue task completion by updating the GitHub issue artifact or the linked implementation plan markdown file. The process supports appending completion notes and logging mandatory revision history for project tracking transparency.

The maximum changes allowed for an implementation plan update is three per invocation. This strict limit ensures surgical, safe edits, preserves sequential task numbering, and mandates revision history logging for all modifications made.

Updating implementation plan markdown files requires validation of input scope and strictly preserves sequential task numbering. Any modifications, such as marking tasks complete or adding new ones, enforce this sequential integrity alongside mandatory revision tracking.

Use a surgical implementation plan update when you need to make small, precise changes like marking a task done or answering an open question. It removes the friction of a full planning session while automatically maintaining revision history for accountability.