What problem does it solve? Keeping a Notion-hosted specification in sync with a local working copy is error-prone: concurrent edits get silently overwritten, approvals bind to stale content, and cached mirrors masquerade as current remote state. This Skill coordinates three copies of the specification—an immutable recorded base, the work-local authored copy, and a fresh remote staging pull—so changes are detected by direct content comparison and publication only happens against verified, approved content. ## Core Features & Use Cases - Materialize mode: Pulls a fresh remote view and creates or refreshes the requested page tree under .state/works/<work-id>/spec/, classifying the result as initial, unchanged, metadata-only, local-only, remote-only, structural change, or conflict. - Complete mode: Acts as a publication gate that reconciles the authored copy with a fresh remote view, verifies stage-specific approval (specification approval or clean implementation review), delegates guarded transport to sync-notion, and verification-pulls after every push. - Immutable evidence: Creates base snapshots and receipts keyed by a stable base identifier derived from the full accepted byte set, never overwriting earlier receipts. - Use Case: Before planning implementation against a Notion spec, run materialize to confirm the local copy matches the recorded base; after the spec is approved, run complete with the specification stage to publish it and refresh dependent work. ## Quick Start Ask the agent to sync the Notion specification at a given URL into the active work directory using sync-spec before starting specification planning.
