10x-init

Scaffolds the context directory skeleton with changes, archive, and foundation subdirectories plus README files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects using the 10x change-tracking workflow need a consistent /context directory structure before they can create, archive, or document changes. Setting up the three subdirectories and their canonical README files by hand is repetitive and error-prone. ## Core Features & Use Cases - Directory Scaffolding: Creates context/changes/, context/archive/, and context/foundation/ with mkdir -p semantics, including implicit parent creation. - Canonical README Generation: Writes a standard README.md into each directory explaining its purpose and conventions, with content embedded inline in the skill. - Idempotent Execution: Each of the six artifacts (3 directories + 3 READMEs) is independently create-if-absent, so re-running on an initialized project is a safe no-op that never overwrites existing content. - Use Case: A developer starting a new project runs the initialization once to establish the change-tracking skeleton, then uses /10x-new to create change folders and /10x-archive to move completed work. ## Quick Start Initialize the context directory structure for this project so I can start tracking changes.

Frequently Asked Questions about 10x-init

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

FAQPage Schema
How do I initialize a context directory for change tracking?

Run the initialization skill once in your project root. It creates context/changes/, context/archive/, and context/foundation/ along with a README.md in each, using mkdir -p so missing parent directories are created automatically.

What is the context directory structure in the 10x workflow?

The structure has three parts: context/changes/ holds in-flight changes with one folder per change, context/archive/ holds completed changes moved there by the archive step, and context/foundation/ holds cross-change living documents like product requirements and tech-stack notes.

Is it safe to re-run the context initialization on an existing project?

Yes, the initialization is idempotent. Each of the six artifacts is independently create-if-absent, so existing directories and README files are left untouched and reported as present in the status summary.

Do I need to run initialization before creating a new change?

No, initialization is not a precondition. The change-creation skill refuses if context/changes/ is missing, and the archive skill lazily creates context/archive/ on demand, so initialization is only for users who prefer setting up the skeleton up-front.

Why are lessons.md and contract-surfaces.md not created during initialization?

Those files are owned end-to-end by the lesson, contract, and implementation-review skills, which self-bootstrap them with canonical headers on first use. The initialization skill only scaffolds the three directories and their README files.