session-end

To keep documentation and task tracking in sync, you need to update feature README status tables, refresh workplans, and record development notes before committing changes. This prevents out-of-sync documentation and ensures a clean handoff for the next work cycle.

Automating documentation updates involves applying a workflow to your feature development worktree that updates the README.md status table, refreshes workplan.md with completed acceptance criteria, and commits these changes to the feature branch using standard Git operations.

The best way to create an audit trail is to generate a DEVELOPMENT-NOTES.md entry using a standardized template capturing date, feature slug, worktree, goals, accomplishments, and lessons learned. This records session outcomes and decisions for future reference.

Yes, session finalization requires a conventional repository layout containing feature README.md, workplan.md, and DEVELOPMENT-NOTES.md files. It also requires standard Git operations to commit and push the updated documentation changes to the feature branch.

Yes, you can update and close GitHub issues that progressed during the session as part of workflow hygiene. It commits all documentation changes on the feature branch while finalizing session outputs and synchronizing project management tracking.

You should not use an automated session-end workflow if your repository lacks the required conventional layout of feature README.md, workplan.md, and DEVELOPMENT-NOTES.md files, or if you cannot perform standard Git operations to commit and push changes.