What problem does it solve? When a product build workflow is interrupted mid-finalization—by session loss, merge conflicts, or documentation failures—PMs need a safe way to resume exactly where things stopped without re-running completed merges or guessing state from branch names. This Skill provides that compatibility and recovery entry point for the finalize stage. ## Core Features & Use Cases - Checkpoint-based recovery: Reads the build contract lifecycle state (building, iterating, final_check, landed, documenting) and resumes only the missing mechanical or semantic items, never replaying completed work. - Merge conflict retry: Preserves worktree and branch state after merge conflicts so the PM can resolve conflicts and re-run finalization safely. - Documentation recovery: For modules already landed on main with pending or failed docs, it recompiles the context pack, regenerates the doc-impact map, and syncs only affected truth-source documents. - Use Case: A PM's session crashes after a module implementation merged to main but before specs were updated. Invoking this entry point detects the landed + docs_pending state and completes only the documentation alignment without re-merging. ## Quick Start Ask the assistant to resume the interrupted build finalization for the current module using the pmai-build-close entry point.
