document360-engine 0.2.2 → 0.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "document360-engine",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Headless documentation agent engine for document360-writer / -desktop. Emits a typed event stream; no UI.",
   "type": "module",
   "main": "./dist/index.js",

package/skills/CLAUDE.md

@@ -126,3 +126,10 @@ Suggestion quality rules:
 - **Only suggest commands that currently apply.** After a run that synced everything, `/publish <path>` is a no-op — don't offer it. Think: what would actually be the user's next move?
 - **After a bulk operation, suggest the bulk form** (`/publish --all`, `/sync pull --all`) — never one arbitrary example article out of thirty.
 - **Suggestions must be consistent with the state you just reported.** If you said "everything is in sync", `/sync pull --all` cannot be the next move. Re-read your own findings before offering commands; an inapplicable suggestion is worse than none.
+
+When the choices are **courses of action, not slash commands** (e.g. "convert all callouts to DFM" vs "convert the FAQ too" vs "leave as GFM"), the auto-numbered quick-run buttons do NOT apply — those only fire on standalone command lines. So number the options yourself and tell the user how to pick:
+
+- Present them as a numbered list — `1.`, `2.`, `3.` — one course of action per item, each a short imperative phrase the user can scan.
+- Close with a single prompt line, e.g. `Reply with the number and I'll action it.` Keep it to one line; no preamble.
+- A bare number in the user's next message refers to the option you numbered — treat "1" as "do option 1", and act on it without re-asking. If your offer has changed since (new turn, new options), renumber and re-present rather than guessing.
+- Cap it at a handful of options (≤4). If there are more, that's a sign the choice is too open — narrow it or recommend one.