Language variants

planning-with-files ships the planning workflow in six languages. The English skill is the canonical one. Arabic, German, Spanish, Simplified Chinese and Traditional Chinese are full translations: the SKILL.md body, the three templates, and the user-facing output of check-complete, init-session and session-catchup are all translated, and each variant carries the same 20 scripts as the canonical skill.

Installing one

Pass the skill name with --skill. Add -g to install globally rather than into the current project.

npx skills add OthmanAdi/planning-with-files --skill planning-with-files-ar -g
npx skills add OthmanAdi/planning-with-files --skill planning-with-files-de -g
npx skills add OthmanAdi/planning-with-files --skill planning-with-files-es -g
npx skills add OthmanAdi/planning-with-files --skill planning-with-files-zh -g
npx skills add OthmanAdi/planning-with-files --skill planning-with-files-zht -g

Each lands in its own directory, for example ~/.claude/skills/planning-with-files-de/, and registers under its own name. Installing a translation does not install the English skill, and installing the English skill does not install any translation.

Running npx skills add OthmanAdi/planning-with-files with no --skill opens a picker listing all available skills with none preselected, so nothing is installed that you did not choose.

Where they live in the repository

skills/
├── planning-with-files/          canonical English skill
└── i18n/
    ├── planning-with-files-ar/
    ├── planning-with-files-de/
    ├── planning-with-files-es/
    ├── planning-with-files-zh/
    └── planning-with-files-zht/

Since v3.11.0 the translations sit one directory deeper than the canonical skill. npx skills add resolves --skill by skill name across a recursive scan, so every install command above is unchanged by that layout and every skill remains individually installable.

On the Claude Code plugin route

The plugin scan reads skills/*/SKILL.md at a single level and does not recurse, so the plugin registers the canonical skill alone. That is deliberate. Before v3.11.0 the plugin registered all six, and every session paid for five skill descriptions in its system prompt whether or not the user had any use for them.

The five language commands still work on the plugin route. /plan-de and its siblings read the translated SKILL.md from disk, trying $HOME/.claude/skills/planning-with-files-<lang>/SKILL.md first and then ${CLAUDE_PLUGIN_ROOT}/skills/i18n/planning-with-files-<lang>/SKILL.md. If neither exists, the command falls back to the canonical skill with an instruction to keep working in that language.

Because the plugin no longer registers them, there is no planning-with-files:planning-with-files-de skill id to invoke by name on that route. Reach a translation through its command, or install it as its own skill with the command above.

Status tokens stay in English

Every translated task_plan.md template keeps the status markers as literal English:

- **Status:** pending
- **Status:** in_progress
- **Status:** complete

The completion gate matches those exact strings with grep -F. Translating them silently disables the gate, so the surrounding prose is translated and the tokens are not. The five language commands state this explicitly so the model does not translate them either.

Reporting a translation problem

Open an issue naming the language and quoting the text. Translations are contributed and reviewed by speakers, not machine generated, so corrections from native speakers are welcome and land in the next release.