10x-init

To set up project context directories without overwriting files, use an idempotent scaffolding process that creates missing folders like context/changes, context/archive, and context/foundation only when they do not already exist.

The standard directory structure for foundation documentation and archival storage uses a context/ parent folder containing changes, archive, and foundation subdirectories, each initialized with canonical README files to guide structured workflows.

Yes, you can add context scaffolding to a partially configured repository by applying create-if-absent behavior, which generates missing directories and parent paths while strictly preserving any existing configuration files.

You can generate README files for new project scaffolding folders by running an initialization process that automatically creates canonical guidance documents inside context/changes, context/archive, and context/foundation directories during setup.

You need a context directory structure before executing structured workflows because it establishes predictable read and write locations for change tracking, archival records, and foundation documents, ensuring workflow skills operate consistently.

The best way to ensure idempotent project scaffolding across multiple runs is to use a setup process that checks for missing directories, creates parent paths as needed, and reports status without modifying existing files.