@chinhae/atw-cli 0.3.4 → 0.3.5

package/dist/migrations/manifests/0.3.5.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.3.5",
+  "description": "Noob mode now says back what the user asked for, with the usual name for it, before starting work.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "atw-noob-mode and workflow.md: a user who is not an engineer describes what they want by how it looks or behaves ('a little hint when the mouse is over the button') because they do not have the name for it. While noob mode is on, the AI now opens with one sentence saying what it understood and gives the thing its usual name with the meaning beside it ('文字提示（Tooltip）——鼠标停上去时冒出来的那行小字'), then carries on without waiting for an answer. A wrong reading can be stopped before the work is done instead of after, and the user has the word next time. It is plain text in the reply, not a question and not an approval step. Limits: one name per reply unless the request really rests on more; only a name in common use that surely fits, and none when the user already used the right word; nothing is added that the user did not mention (a framework, a component library, a setting, an approach); a request that can be read two ways with different results is put to the user as a choice instead. The per-turn reminder in workflow.md's [workflow-state:noob_mode] block carries the rule in one line, so it holds in long conversations and new sessions.",
+  "migrations": [],
+  "notes": "No migration required and no files added, deleted or renamed. Two templates changed: .atw/workflow.md (one line added to the [workflow-state:noob_mode] block) and the atw-noob-mode skill (a new section, 'Saying back what they asked for'). They update as Template updated where the project left them untouched; where a project edited them locally, atw update asks before replacing — keep the edit and noob mode stays as it was for that project. Nothing changes for a developer who has noob mode off."
+}

package/dist/templates/atw/workflow.md

@@ -284,6 +284,7 @@ Preserve existing task fields and artifacts. If the correct status cannot be det
 [workflow-state:noob_mode]
 Noob mode is ON — this user is not an engineer. Hold to these rules in every reply, in every stage (the full set is `/atw-noob-mode`):
 - Plain words in the user's language. Explain any unavoidable term, command, path or flag in the same sentence it appears in.
+- When they describe what they want by how it looks or behaves, open with one sentence saying what you understood and its usual name with the meaning beside it, then carry on without waiting.
 - Before anything they must approve or that is hard to undo: what will happen, why, how risky it is, and what approving or declining leads to.
 - Say who did what, what you actually ran versus what you only expect, and every decision you made for them.
 - Retell sub-agent reports, command output and errors the same way: what happened, what it affects, what comes next.

package/dist/templates/common/bundled-skills/atw-noob-mode/SKILL.md

@@ -34,6 +34,15 @@ Reply in the user's language. Keep commands, paths, file names, flags and error
 7. **Name the decisions you made for them.** A shortcut, a placeholder standing in for the real thing, a skipped check, a silenced warning, an outside package, a change wider than asked, a pick between two defensible options — report each one where it happened: what you chose, why, and what it costs later. They cannot overrule a decision they never heard about.
 8. **Alarming words are usually routine.** An error, a failed build, a conflict — name it calmly and say what it means for them right now.
 
+## Saying back what they asked for
+
+The user describes what they want by how it looks or behaves — "a little hint when the mouse is over the button" — because they do not have the name for it. Before you start on a request like that, say in one sentence what you understood, and give the thing its usual name with the meaning beside it: "我理解你要的是给下载按钮加文字提示（Tooltip）——鼠标停上去时冒出来的那行小字。" Then carry on. This is not a question and you do not wait for an answer: if you understood wrong they can stop you before the work is done instead of after, and next time they have the word.
+
+- **One name.** The one that would have made the request clearest. Two or three only when the request really rests on each of them.
+- **Only a name you are sure fits.** If there is none in common use, or the user already used the right word, say back what you understood in plain words and add no name. A request that is already exact needs no saying back at all.
+- **What they asked, no more.** Do not slip in a framework, a component library, a setting or an approach they did not mention. A choice like that is a decision you made for them — rule 7 above.
+- **Two readings are a choice.** When the request could mean two different things and the difference changes the result, do not pick one and say it back; put it to them as in "When they must choose".
+
 ## Before you act
 
 Before any step the user must approve, and before anything hard to undo even when no approval is asked, say four things:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chinhae/atw-cli",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "description": "A Team Workflow — an AI coding workflow framework that encodes your team's conventions into the process",
   "type": "module",
   "main": "./dist/index.js",
@@ -33,7 +33,7 @@
     "inquirer": "^9.3.7",
     "undici": "^6.21.0",
     "zod": "^4.4.2",
-    "@chinhae/atw-core": "0.3.4"
+    "@chinhae/atw-core": "0.3.5"
   },
   "devDependencies": {
     "@eslint/js": "^9.18.0",