What problem does it solve? Starting a new unit of work often lacks structure: notes, plans, and reviews end up scattered. This Skill bootstraps a consistent change folder under context/changes/<change-id> with a standardized change.md identity file, so every change has a traceable lifecycle from the start. ## Core Features & Use Cases - Change Folder Bootstrap: Creates context/changes/<change-id>/ with a change.md file containing frontmatter (change_id, title, status, created, updated, archived_at) and a Notes section. - Input Validation: Enforces kebab-case change-ids, checks uniqueness against context/changes/ and context/archive/, and verifies the repo is set up for the 10x context structure. - Next-Step Guidance: Suggests the appropriate follow-up skill (/10x-plan, /10x-research, or /10x-frame) based on the parsed intent and copies it to the clipboard. - Use Case: A developer wants to add OAuth login. They invoke the skill with "oauth-login add Google sign-in", and it creates context/changes/oauth-login/change.md with a derived title and the intent captured in Notes, ready for planning. ## Quick Start Ask the assistant to start a new change with a kebab-case id and optional intent, for example: run /10x-new oauth-login add Google sign-in so users skip the email-password step.