Skip to content

A Claude Code / Codex plugin that helps you learn how to build while AI writes the code.

Python

ux: make decision choices welcoming to learner questions

Noah Kimee420100f736
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 2f4de8c..65e3663 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "vibe-wise",
- "version": "0.1.18",
+ "version": "0.1.19",
"description": "You build. AI writes. Learn how to build software while Claude writes the code.",
"author": { "name": "Noah Kim" },
"repository": "https://github.com/nykooi1/vibe-wise",
diff --git a/README.md b/README.md
index 7a23e19..c7099c6 100644
--- a/README.md
+++ b/README.md
@@ -59,8 +59,10 @@ Claude:
If confirmed, we'll record this access rule. Next, we'll work through how the
server knows who's making the request; we haven't chosen that yet.
- ❯ 1. Confirm approach
- 2. Discuss first
+ ❯ 1. Confirm and continue
+ This approach makes sense to me; move to the next piece.
+ 2. Talk it through
+ Ask questions or clarify anything that doesn't make sense before deciding.
```
You don't need to know the answer already. Claude can explain unfamiliar concepts, sketch the relevant pieces, and help you tackle a smaller question. You stay involved in forming the plan. Answer in plain English; ask for more help or say “skip” whenever you want.
@@ -68,7 +70,7 @@ You don't need to know the answer already. Claude can explain unfamiliar concept
Describing what you want sets the requirements. Build Checkpoints ask you to work
out how it should function; a feature preference doesn't approve an architecture.
-**Confirm approach** records a design decision and continues planning. **Implement this step** writes the specific code Claude just described. **Discuss first** lets you ask questions or explore alternatives before either action.
+**Confirm and continue** means the approach makes sense to you and you're ready for the next design decision. **Implement this step** writes the specific code Claude just described. **Talk it through** gives you room to ask questions, clarify anything confusing, or explore alternatives before deciding.
After implementation, Claude briefly explains what changed, how the key code works,
why it fits your decision, and what was tested. Ask to dig deeper anywhere it's unclear.
diff --git a/docs/development.md b/docs/development.md
index 9cba088..d843762 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -45,8 +45,8 @@ Launch with `claude --plugin-dir /absolute/path/to/vibe-wise`.
question under a title naming the decision, before suggesting its own solution
or implementing the decision. Give a partial answer; check that
it refines the answer, names the coding scope, and offers Implement this step /
- Discuss first. Select Discuss
- first, ask for clarification or propose an alternative, and confirm it stays
+ Talk it through. Select Talk it through,
+ ask for clarification or propose an alternative, and confirm it stays
paused and updates the approach if needed. Select Implement this step;
check it writes the code and records only evidenced learning. Restart while a
Decision Checkpoint is pending and confirm it preserves that pause.
@@ -65,9 +65,11 @@ Launch with `claude --plugin-dir /absolute/path/to/vibe-wise`.
unfamiliar term means while answering a checkpoint. Claude should explain it
and return to a manageable reasoning step, not bundle new architecture choices
into an implementation approval. Use different projects to avoid overfitting.
- A design-only Decision Checkpoint should offer Confirm approach / Discuss first. Confirming
+ A design-only Decision Checkpoint should offer Confirm and continue / Talk it through. Confirming
it records the choice and continues to unresolved decisions without writing
application code. Implementation approval must name a concrete coding scope.
+ Option descriptions should invite clarification and express readiness to proceed;
+ choosing confirmation alone must not be recorded as demonstrated understanding.
7. **Preference versus reasoning:** Answer a checkpoint with a tentative preference
and no rationale. Claude should ask one focused question about implications or
tradeoffs, not invent the learner's reasoning, praise mastery, or immediately
@@ -194,7 +196,7 @@ Tested on 2026-09-28 with Claude Code 2.1.240:
unfamiliar copy of this repository. A new session restored saved preferences.
- The fresh-project session asked about persistence, reviewed the learner's JSON
storage proposal, waited through clarification (the choice was initially named
- Ask a question; now Discuss first), then wrote
+ Ask a question; now Talk it through), then wrote
the CLI after Implement. Its five generated CLI/storage tests passed locally.
Those initial live tests used print mode with file tools and covered the plain-text
diff --git a/skills/learn/behavior.md b/skills/learn/behavior.md
index ddb3598..67e5a1b 100644
--- a/skills/learn/behavior.md
+++ b/skills/learn/behavior.md
@@ -40,10 +40,14 @@ A **BUILD CHECKPOINT** asks one focused reasoning question, which can invite a w
approach. Follow up only to resolve meaningful gaps.
Before acting on a design, use a **DECISION CHECKPOINT**: briefly state the proposal,
-tradeoffs, and scope. **Confirm approach / Discuss first** records a design and
-continues planning. **Implement this step / Discuss first** authorizes the named
-code changes. Wait for the answer; additions need discussion before confirmation.
+tradeoffs, and scope. Offer **Confirm and continue** ("This approach makes sense to
+me; move to the next piece.") to record a design and continue planning, or
+**Implement this step** ("This approach makes sense to me; write the code for this
+step.") to authorize the named code changes. Pair either with **Talk it through**
+("Ask questions or clarify anything that doesn't make sense before deciding.").
+Wait for the answer; additions need discussion before confirmation.
Combine evaluation and confirmation when the reasoning already suffices.
+Confirmation indicates readiness to proceed, not demonstrated understanding.
After implementing, give up to three short, flat bullets: changed files, key code
mechanics and why they fit, and actual verification. Offer deeper detail without