What problem does it solve? When PMs review published specs directly in Lark (Feishu) Docx documents, their edits and comments drift away from the authoritative local spec. This Skill recovers those review inputs, reconciles baseline/local/remote versions, and routes each change by product impact back into the correct lifecycle stage. ## Core Features & Use Cases - Three-way version reconciliation: Aligns the published baseline, local spec, and current Lark document into a single target version with 100% content and format coverage accounting. - Impact-based routing: Classifies feedback as minor fixes, product-level changes, module-level changes, or in-scope build adjustments, and hands off to Proposal, design, quick-fix, or the active build accordingly. - Controlled write-back and comment closure: Applies the sealed target to the authoritative spec, syncs the same Lark document with native block-level edits, and replies to or resolves comments only after implementation is verified. - Use Case: A PM says "I reviewed and annotated the spec in Feishu." The Skill collects all body edits and unresolved comment threads, asks one batched confirmation question, updates the authoritative spec, syncs the same Lark doc, and closes the comments after the product result is verified. ## Quick Start Ask the agent to run /pmai-lark-review with the Lark document URL or the local spec markdown path to pull the Feishu review back into the product workflow.
