What problem does it solve? Architecture decisions in bilingual projects often get recorded inconsistently, with invented API signatures, stale SRS line references, and out-of-sync English/Chinese documents. This Skill enforces a verified, repeatable ADR authoring workflow so every decision record is accurate, traceable, and reviewable. ## Core Features & Use Cases - Mandatory ADR Structure: Enforces the six-section format (Context, Decision, Alternatives, Consequences, Verification, Supersession) with frontmatter status gating at Proposed until maintainer approval. - Source-Verified Authoring: Requires checking real framework source code for API signatures and grepping actual SRS requirement IDs before citing them, preventing compile-breaking or mis-anchored ADRs. - Bilingual Synchronization: Produces the English canonical ADR plus Chinese translation, updates both README index tables, and runs an identifier-consistency diff between the pair. - Use Case: When a public API change needs an ADR, the Skill reads the real contract code, drafts the decision with alternatives and explicit supersession statements, prepares a numbered maintainer decision list with recommended defaults, and keeps both language versions in sync. ## Quick Start Ask the agent to write an ADR for a proposed architecture change, verifying the real API signatures and SRS anchors first and producing both the English and Chinese versions with updated README indexes.
