Make scaffold target explicit: ask, default to sibling, offer git init

README.md

@@ -61,7 +61,7 @@ Inside Claude Code:
 /clify-scaffold https://docs.example.com/api
 ```
 
-The skill walks the 13-step pipeline (fetch → parse → consult → init → substitute → validate → simplify → report) and produces `<api-name>-cli/` next to the current directory.
+The skill walks the 13-step pipeline (fetch → parse → consult → **ask where to put it** → init → substitute → validate → simplify → report). The generated CLI is **its own project**, in its own directory, with its own `git init` — by default a sibling of your current directory, but the skill asks before creating files. Output is `<chosen-parent>/<api-name>-cli/`, never nested inside the calling repo unless you explicitly ask for that.
 
 You can also call the binary verbs directly:
 

bin/clify.mjs

@@ -107,7 +107,7 @@ function runScaffoldInit(args) {
   try {
     const result = scaffoldInit({ apiName, target });
     if (json) process.stdout.write(JSON.stringify(result, null, 2) + "\n");
-    else process.stdout.write(`scaffolded ${result.apiName} → ${result.dir}\n`);
+    else process.stdout.write(`scaffolded ${result.apiName} → ${result.dir}\n  (next: cd into the dir, git init if you want history, then run /clify-scaffold's substitution phase)\n`);
   } catch (err) {
     process.stderr.write(`error: ${err.message}\n`);
     process.exit(1);

skills/clify-scaffold/SKILL.md

@@ -62,13 +62,34 @@ Second prose pass for non-endpoint rules (units, formats, defaults, sequencing,
 
 Present findings to the user with opinionated recommendations. Use `AskUserQuestion` for unresolved tradeoffs (resource grouping, ambiguous verbs, what to drop). Record dropped endpoints with one of the allowed reasons (`user-excluded-step-7`, `deprecated-in-docs`, etc.) — never silently drop.
 
-### 8. Init repo from exemplar (binary verb)
+### 8. Decide where the new repo lives, then init from exemplar
+
+The generated CLI is its own project — a separate directory, not nested inside whatever repo the user happened to invoke `/clify-scaffold` from. Before running the binary verb, **ask the user with `AskUserQuestion`**:
+
+> "Where should I put `<api-name>-cli/`? Default is `<parent-of-cwd>` (sibling of your current directory). I'll also `git init` the new repo unless you say otherwise."
+
+Options to offer:
+- **Default** — parent of cwd (`..`), so the layout is `parent/<original-cwd>/` next to `parent/<api-name>-cli/`. Right answer for almost every case, including when the user runs the skill from inside the clify repo itself.
+- **Custom path** — user supplies an absolute or relative directory.
+- **Here (nested)** — only when the user is explicit; warn that this couples the new CLI's git history to the parent.
+
+Then run the binary verb with the chosen target:
+
+```
+clify scaffold-init <api-name> --target <chosen-parent-dir>
+```
+
+This is the **deterministic copy + rename phase** — never do it by hand. Copies `examples/jsonplaceholder-cli/` to `<chosen-parent-dir>/<api-name>-cli/` and rewrites `jsonplaceholder` → `<api-name>`, `JSONPLACEHOLDER` → `<API_NAME>`, `JSONPlaceholder` → `<API Title>` everywhere.
+
+Print the resolved absolute path to the user so they can confirm before substantive content lands.
+
+After the copy, `git init` the new repo (skip if the user opted out):
 
 ```
-clify scaffold-init <api-name> --target <parent-dir>
+cd <chosen-parent-dir>/<api-name>-cli && git init -q && git add -A && git commit -q -m "Initial scaffold from clify exemplar"
 ```
 
-This is the **deterministic copy + rename phase** — never do it by hand. Copies `examples/jsonplaceholder-cli/` to `<parent-dir>/<api-name>-cli/` and rewrites `jsonplaceholder` → `<api-name>`, `JSONPLACEHOLDER` → `<API_NAME>`, `JSONPlaceholder` → `<API Title>` everywhere.
+The initial commit makes step 9's substitutions a clean diff the user can review.
 
 ### 9. Substitute API-specific content