What problem does it solve? Restructuring a documentation repository into bilingual language pairs (docs/en/ and docs/zh/) without losing Git history, breaking links, or drifting between translations is error-prone. This Skill provides a phase-gated migration workflow with a machine-readable manifest, canonical state machine, blob integrity tracking, and validation gates so authority switches atomically and verifiably. ## Core Features & Use Cases - Phase-gated migration workflow: P0 infrastructure through P6 cleanup, one independent commit per phase, covering entry points, history docs, ADRs, evidence, and normative documents (SRS/HLD/traceability). - Manifest and blob integrity model: a documentation-manifest.json records document roles, authority paths, migration phases, and Git blob OIDs so canonical state is never inferred from directory location alone. - Translation and review rules: fenced-block classification, identifier preservation (REQ-, DES-, ADR-* IDs, code, commands), delegated parallel translation, and bilingual reviewer gates before cutover. - Use Case: A team needs to make their Chinese-first docs bilingual with English as canonical. The Skill guides creating the manifest and validator, translating with preserved tuples, running a human review gate, then atomically cutting over with git mv and pointer stubs. ## Quick Start Ask the agent to migrate the repository's documentation into English and Chinese language pairs following the canonical-English convention with per-phase commits.
