document-release

Post-ship documentation synchronization is the process of updating README, ARCHITECTURE, and CLAUDE.md files to match shipped changes. This workflow automates that process using Bash to orchestrate updates across your project's core documentation.

The best way to update CLAUDE.md and README files after shipping is to run a post-ship docs workflow. It automatically aligns your documentation with shipped changes and can optionally prompt for Linear integration to align governance with docs.

Yes, you can use post-ship docs sync with Linear integration. The workflow can prompt for optional Linear integration to align governance with documentation updates, keeping your project tracking and docs consistent across teams.

The files updated during a post-ship documentation workflow include README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md. The workflow loads the Markdown body as operational instructions to orchestrate these updates accurately.

Yes, you need YAML frontmatter for post-ship documentation updates. The workflow enforces a YAML frontmatter with a name and description at the root level to properly load the Markdown body as operational instructions for Bash orchestration.