10x-new

Creates a new change folder with a change.md identity file under context/changes.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Assamir/ai-toolkit --skill 10x-new-assamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-new
Source: https://github.com/Assamir/ai-toolkit/tree/main/.cursor/skills/10x-new
Command: npx skills add https://github.com/Assamir/ai-toolkit --skill 10x-new-assamir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about 10x-new

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a new change folder for a feature?

Invoke the skill with a kebab-case change-id and optional intent text, such as `oauth-login add Google sign-in`. It creates context/changes/<change-id>/change.md with status new and suggests the next step.

What naming rules apply to a change-id?

The change-id must be kebab-case: start with a lowercase letter, use lowercase letters, digits, and single hyphens, with no leading or trailing hyphens and no double hyphens. Invalid ids are rejected with an error message.

What happens if the change-id already exists?

The skill checks both context/changes/ and context/archive/ for collisions. If the id exists in either location, it stops with an error telling you to pick a different id or work inside the existing folder.

Does this skill create the context/changes directory?

No. If context/changes/ is missing, the skill stops with an error indicating the repo is not set up for the 10x context structure. You must bootstrap that parent directory yourself first.

What files does the new change skill create?

It creates only one file: change.md inside the new change folder, containing frontmatter (change_id, title, status, created, updated, archived_at) and a Notes section. Artifacts like frame.md, research.md, and plan.md come from other skills.