governance-enrich-ticket

To update existing markdown work items, parse frontmatter and merge section-aware content to add shipped behavior, decisions, and artifact links while preserving existing history. This prevents project documentation from becoming stale after changes are completed.

Linking ADRs and design artifacts to completed work items involves adding related items and documentation links with clear reasons for connections during governance enrichment. This ensures decisions and designs stay connected to shipped reality.

Yes, you can enrich discovery documents and spike stories without overwriting existing content by using section-aware content merging and a confirmation-based workflow. This preserves existing work item history while applying precise updates.

Keeping project governance documentation aligned requires updating existing work item records with completed scope, implementation details, and decisions after changes ship. This ensures discovery documents, stories, and ADRs match current reality.

Yes, this work item enrichment approach requires manual confirmation before writing updates. It reviews current work item content first, then applies precise changes through a controlled workflow to prevent accidental overwrites of existing records.

Updating work items with shipped decisions and artifacts requires markdown files with frontmatter parsing support. The process handles discovery documents, stories, spikes, ADRs, and designs by merging content into existing sections without losing history.