post-work-update

To automatically update project documentation after completing a code change, you can run a skill that synchronizes AGENTS.md, SKILL.md, and spec status boards. It ensures knowledge bases stay current by revising navigation indexes and logging gotchas whenever files are added or removed.

Keeping spec status boards and knowledge bases current in an agile workflow requires automatically marking completed specs and adding rows to epic boards. This prevents outdated information from accumulating by applying defined triggers after any feature addition or specification completion.

Yes, you can sync AGENTS.md and navigation indexes when repository files are renamed or removed. The documentation sync process automatically updates related tables and keeps the master spec index accurate by adding, removing, or updating entries according to defined triggers.

To capture gotchas and reusable patterns after implementing a new feature, you can log friction and newly discovered patterns during a post-work update. This learning capture records reusable solutions and integrates them into the project knowledge base for future reference.

Yes, post-work documentation update works without any external dependencies. The skill operates independently to refresh all documentation, update the spec status board, and record newly discovered gotchas directly within your repository environment.

You need to run a documentation sync for your repository after any development or documentation activity, such as a code change, feature addition, or specification completion. This ensures AGENTS.md, SKILL.md, and navigation indexes are revised before outdated information accumulates.