scaffold-update-checklist

Mirrored files between the cookiecutter template and project docs drift when structural or plugin changes occur. Synchronization prevents this drift by keeping cross-references, counts, and version numbers aligned between the cookiecutter source and the project root.

The best way to apply structural updates to a scaffold template is to follow a repeatable checklist workflow, ensuring you update both the cookiecutter copy and the project docs, then run the migration to apply changes and validate consistency.

You validate cross-link consistency after a scaffold migration by adhering to the update workflow, which requires validating mirrored file sets to ensure migration guides and references stay current between the cookiecutter source and project root.

Yes, you can use a repeatable checklist to guide migrations for plugin components, safely applying changes across plugin skills, commands, and agents while ensuring mirrored copies and cross-references remain aligned.

You need to synchronize scaffold templates and mirrored documentation when making structural or plugin changes, ensuring that mirrored copies, cross-references, counts, and version numbers stay aligned between the cookiecutter source and the project root.