createlisted

# Create a worktree Use the name and options supplied in the user's request. A name is required: if absent, ask for it rather than inventing one. Recommend short kebab-case names. An optional base branch maps to `--from`; preserve requested `--dest`, `--env`/`--no-env`, `--composer`/`--no-composer`, and `--npm`/`--no-npm` options. Resolve the bundled [worktree runtime](../../scripts/worktree.sh) relative to this skill file, then use its absolute path for every invocation. Run from the repository that owns the requested work: for a submodule, run inside that submodule. Read applicable repository instructions before choosing a branch or destination. 1. Inspect `.worktree.json` when present and show resolved settings with `bash "$worktree_runtime" config` where resolvable, with `worktree_runtime` set to the absolute script path. A requested `--from` or `--dest` can override an invalid configured base or destination; a diagnostic `config` failure alone does not rule out that valid create invocation. The engine honours configuration and otherwise uses the shared `wt/` branch prefix. There is no prefix flag or environment override. If repository instructions require a different prefix and configuration does not provide it, explain the configuration prerequisite before creating anything. Configure the required prefix through the init workflow when authorized; do not silently rewrite repository settings or rename a branch after creation. Existing configuration