What problem does it solve? Starting a new unit of work often lacks structure: notes scatter across chats, and there is no consistent place to track a change from idea to archive. This Skill bootstraps a standardized change folder so every piece of work begins with a consistent identity file and a clear next step. ## Core Features & Use Cases - Change folder bootstrap: Creates context/changes/<change-id>/ with a change.md file containing frontmatter (change_id, title, status, dates) and a Notes section. - Input validation: Enforces kebab-case change-ids, checks uniqueness against existing and archived changes, and verifies the repo has the expected context structure. - Intent-aware setup: Parses freeform intent text to derive a human-readable title and seed the Notes section, then suggests the right next skill (plan, research, or frame) and copies it to the clipboard. - Use Case: A developer wants to add OAuth login. They run the skill with oauth-login add Google sign-in, and get a ready-to-use change folder with status new plus a suggested /10x-plan oauth-login command on their clipboard. ## Quick Start Ask the assistant to start a new change with a kebab-case id and a short description, for example: create a new change called oauth-login for adding Google sign-in.