Use when archiving an already-maintained engineering project into a governed Obsidian vault, especially when the project has active code, docs, ADRs, roadmaps, repo metadata, or working notes that should become structured vault knowledge instead of a raw code dump.
Use this skill when an existing software or engineering project should enter the vault as structured knowledge. The vault should preserve project understanding, not become a second source repository.
topic_id$vault-canonical-promotion instead of self-promotingRead references/project-archiving-pattern.md before archiving.