What problem does it solve? Starting a new unit of work in a structured change-management workflow requires consistent folder scaffolding, naming conventions, and lifecycle metadata; doing this by hand leads to inconsistent change-ids, missing frontmatter, and collisions with existing or archived changes. ## Core Features & Use Cases - Change folder bootstrapping: Creates context/changes/<change-id>/ with a change.md identity file containing validated frontmatter (change_id, title, status, created, updated, archived_at). - Argument parsing and validation: Accepts plain slugs, path-style references (with or without @), and freeform intent; enforces kebab-case and uniqueness across context/changes/ and context/archive/. - Next-step routing: Suggests and copies to clipboard the appropriate follow-up skill (/10x-plan, /10x-research, or /10x-frame) based on signals in the stated intent. - Use Case: A developer wants to start work on OAuth login. They invoke the skill with oauth-login add Google sign-in for faster onboarding, and it creates the change folder, writes a titled change.md seeded with the intent as Notes, and copies /10x-plan oauth-login to the clipboard. ## Quick Start Ask the assistant to start a new change called oauth-login with the intent to add Google sign-in for faster onboarding.
