update-docs

You can keep project documentation in sync after coding by running a documentation update workflow that journals recent changes, syncs state and module files, and fixes stale README.md and CLAUDE.md content automatically.

Automating README and CLAUDE.md updates is best handled by a post-implementation documentation skill that detects stale content and refreshes it to match the current project structure alongside generating a journal entry.

Journaling for project state management works by recording what changed and why in a journal directory, then updating index, state, and module documentation files to reflect the latest code modifications.

You do not need any specific dependencies to update project docs automatically, as the skill operates without external packages but requires access to your journal directory and key documentation files like README.md and CLAUDE.md.

Yes, you can use a documentation sync workflow for fixing stale content in markdown files, as it specifically targets and updates outdated sections in README.md and CLAUDE.md to align with recent code changes.

You should run a documentation update workflow immediately after implementing new features or making significant code changes, ensuring your journal entries, state files, and project documentation accurately reflect the latest updates.