{"version":"2.1.77","anchor":"enhanced-init-command-gradual-rollout","canonical_anchor":"enhanced-init-command-gradual-rollout","heading":"Enhanced \/init Command [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.77\/e\/enhanced-init-command-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.77","markdown":"### Enhanced `\/init` Command [Gradual Rollout]\n\nThe `\/init` command has a significantly expanded multi-phase workflow (gated behind the `CLAUDE_CODE_NEW_INIT` environment variable):\n\n- Phase 1: Choose between project CLAUDE.md, personal CLAUDE.local.md, or both\n- Phase 2: Codebase exploration (build\/test commands, frameworks, project structure)\n- Phase 3: Gap-fill interview with the user, synthesize proposals for hooks\/skills\/notes\n- Phase 4: Write minimal, high-signal CLAUDE.md\n- Phase 5: Write personal CLAUDE.local.md (added to `.gitignore`)\n- Phase 6: Suggest and create skills in `.claude\/skills\/`\n- Phase 7: Suggest optimizations (GitHub CLI, linting, format-on-edit hooks)\n- Phase 8: Summary with plugin recommendations (skill-creator, frontend-design, playwright)\n\n**Evidence**\n\nMulti-phase flow (search for `\"Phase 1: Ask what to set up\"`) and env var gate (search for `\"CLAUDE_CODE_NEW_INIT\"`)"}