XIP Sync Skill

Source of truth: GitHub issues (label xip).
Backup: docs/proposals/xip/ folder (generated from GitHub via sync).

Create and edit XIPs in GitHub; keep a local backup in docs/proposals/xip/ by running sync. Do not treat the local folder as the primary place to write XIPs.

For XIP structure, templates, and writing patterns, use XIP writing reference. This skill is the operational workflow for issue creation, issue editing, sync, and recovery.

Principles

1. Create and edit XIPs in GitHub – Use gh issue create / gh issue edit (or the GitHub UI). The issue body holds the full XIP markdown. Status (open/closed/parked) lives only in GitHub via issue state and labels.
2. Sync GitHub → docs/proposals/xip – Run the sync script to write one .md file per XIP under docs/proposals/xip/ (single folder). Files do not move; status is not reflected in paths.
3. docs/proposals/xip folder is read-only for XIP content – Do not edit XIP content in the local folder; edit the GitHub issue, then sync.
4. Recovery – If the only copy of a XIP is in docs/proposals/xip/, create a new issue with that content and then sync.