opi

Update opi documentation so it stays truthful to the shipped code and the English/Chinese mirrors stay in sync. Use this skill whenever the user mentions "update the docs/README", "refresh the README", "sync EN/ZH", "translate the README", "fix doc drift", "文档更新", "文档同步", "更新 README", "翻译 README", or asks to bring docs in line after a change. Also use at Phase 6 of the opi workflow (after implementation/remediation, before release), and whenever a version bump needs the doc version-strings resynced.

Use when executing opi-spec.md tasks or reviewed supplemental opi phase tasks, checking implementation status, reinitializing the task ledger, resuming interrupted implementation, clearing task blockers, or auto-selecting the next unblocked task. Triggers on implement, resume, verify, or progress requests for spec tasks; not on merely reading or discussing specs.

Orchestrates the full release process for the opi Rust workspace — publishes to GitHub Releases and crates.io with phased safety gates

Perform an independent code audit of a specific opi implementation phase. Given a phase number, automatically extract the task graph, design spec, and commit range from impl-state.json, then systematically compare spec against actual implementation. Use this skill whenever the user mentions "audit", "code review", "审计", "审查", "review phase N", "compare spec and implementation", or asks to verify whether a phase was implemented correctly. Also use when the user wants to check spec compliance, find implementation gaps, or produce a structured audit report for any phase.

Use when the user wants to confirm, verify, or fix issues from audit reports for a specific opi implementation phase. Triggers on "remediate phase N", "verify audit findings", "fix audit issues", "confirm audit", "修复审计", "验证审计发现", "审计修复", or any request to cross-reference multiple audit reports and produce a verified remediation plan. Also use when the user asks to act on findings from docs/snapshots/phase<N>/audit.*.md files.

Compare a current implementation with a target/reference project and produce an architecture, feature, design-philosophy, package-boundary, and roadmap realignment review. Use when the user asks to realign, audit drift, compare a port/reimplementation, check whether planned phases match an upstream project, or evaluate cross-language architecture against a target project path.