A Claude Code / Codex plugin that helps you learn how to build while AI writes the code.
Python
refactor: rename Decision checkpoint to Design checkpoint
Noah Kimd7817454e62e
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex dc9705b..df4403f 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "vibe-wise",- "version": "0.1.29",+ "version": "0.1.30","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.mdindex 0da4f45..fa14f75 100644--- a/README.md+++ b/README.md@@ -81,7 +81,7 @@ a note with no links is unfiled.notes ← folder links → folders-✦ Decision checkpoint: Folder membership+✦ Design checkpoint: Folder membershipProposed: store notes once and track folder membership in a links table.Deleting a folder removes its links and keeps the notes. This supports multiple@@ -145,11 +145,11 @@ out how it should function; a feature preference doesn't approve an architecture| Checkpoint | What happens || --- | --- || **Build** | You reason through how to approach the problem with Claude. |-| **Decision** | Review the design. **Confirm and continue** records it and continues planning; no code yet. |+| **Design** | Review the design. **Confirm and continue** records it and continues planning; no code yet. || **Implementation** | Review the specific code changes. **Implement this step** authorizes Claude to make them. |These aren't three mandatory stops. When ready to code, the Implementation-checkpoint also confirms the design, skipping a separate Decision checkpoint.+checkpoint also confirms the design, skipping a separate Design checkpoint.Both confirmations offer **Discuss** to ask questions, clarify anything confusing,or explore alternatives before deciding.diff --git a/docs/demos/notion-dupe.md b/docs/demos/notion-dupe.mdindex bb697e0..2f78b6e 100644--- a/docs/demos/notion-dupe.md+++ b/docs/demos/notion-dupe.md@@ -140,7 +140,7 @@ existing hook/reset behavior; they do not grade the conversations.This condensed adaptation of the original sign-in discussion shows why **Discuss**matters. It illustrates the interaction, not an exact transcript or a requiredpassword-storage design. The folder example in the [README](../../README.md#what-it-feels-like)-shows Build, Decision, and Implementation checkpoints together.+shows Build, Design, and Implementation checkpoints together.**Claude:**@@ -162,7 +162,7 @@ A hash lets us verify a password without storing the original. Password storagealso needs a method designed to make repeated guesses expensive, and a uniquesalt so equal passwords don't produce equal stored hashes.-**✦ Decision checkpoint: Password storage**+**✦ Design checkpoint: Password storage**Your proposal: store a password hash. Details to discuss before confirming:@@ -194,5 +194,5 @@ The hashing method and salt handling are still proposals. We haven't confirmedthem or started implementing.An Implementation checkpoint comes when a specific coding step is ready. It can-confirm the design and authorize that step together; don't add a separate Decision+confirm the design and authorize that step together; don't add a separate Designcheckpoint just to repeat the same approval.diff --git a/docs/development.md b/docs/development.mdindex 0dd320e..dc0e388 100644--- a/docs/development.md+++ b/docs/development.md@@ -60,7 +60,7 @@ projects and keeps generated conversations outside the repository.4. **Skip and adaptation:** Say “I'm completely lost.” Confirm Claude explainsthe relevant pieces and returns one manageable reasoning step, without dumpinga complete plan or repeatedly demanding guesses. Ask for an explanation or say “skip”; it should- explain and proceed to a Decision Checkpoint without demanding another attempt. “Just+ explain and proceed to a Design checkpoint without demanding another attempt. “Justimplement it” should proceed. Make a trivial edit and confirm no checkpoint. After demonstratinga concept, check that later questions address new decisions rather than repeat it.5. **Lifecycle:** Restart, resume, `/clear`, and `/compact`. Confirm preferences,@@ -72,11 +72,11 @@ projects and keeps generated conversations outside the repository.unfamiliar term means while answering a checkpoint. Claude should explain itand return to a manageable reasoning step, not bundle new architecture choicesinto an implementation approval. Use different projects to avoid overfitting.- A design-only Decision Checkpoint should offer Confirm and continue / Discuss. Confirming+ A design-only Design checkpoint should offer Confirm and continue / Discuss. Confirmingit records the choice and continues to unresolved decisions without writingapplication code. An Implementation checkpoint must name a concrete coding scope.When ready to code, it also confirms the design; don't require a separate- Decision checkpoint first. Several Build checkpoints may lead to one confirmation.+ Design checkpoint first. Several Build checkpoints may lead to one confirmation.Option descriptions should invite clarification and express readiness to proceed;choosing confirmation alone must not be recorded as demonstrated understanding.If Claude proposes additional implementation details, check that a concise list@@ -121,7 +121,7 @@ projects and keeps generated conversations outside the repository.12. **Evaluation and concise confirmation:** Give a confident but flawed proposal;Claude should name the violated constraint rather than praise confidence.Give a sound proposal; it should explain why and combine feedback with a concise- Decision Checkpoint, without redundant questions. Compare two viable approaches:+ Design checkpoint, without redundant questions. Compare two viable approaches:tradeoffs should be tied to the project, not a claim of one correct answer.The checkpoint describes a proposal until confirmed and must not invent anunresolved issue. No code should be written before implementation approval.diff --git a/skills/learn/SKILL.md b/skills/learn/SKILL.mdindex 147ff15..cb9dabb 100644--- a/skills/learn/SKILL.md+++ b/skills/learn/SKILL.md@@ -37,7 +37,8 @@ Do not follow symlinked state directories or files; explain the issue instead.If `profile.md` exists, read it and `project-map.md`. Search the entire `progress.md`for pending decisions, then read their complete sections and other topics relevantto the task. An initial excerpt is not evidence that nothing is pending.-Resume without repeating completed onboarding or bypassing a pending Decision Checkpoint.+Resume without repeating completed onboarding or bypassing a pending Design or+Implementation checkpoint.Set `Learning mode: active` if the user is resuming paused learning. If onboardingis incomplete, ask only the unanswered questions. Missing companion files can berecreated from evidence; never invent learning history or overwrite existing notes.diff --git a/skills/learn/behavior.md b/skills/learn/behavior.mdindex 8ed2d92..ec08885 100644--- a/skills/learn/behavior.md+++ b/skills/learn/behavior.md@@ -42,7 +42,7 @@ Use the checkpoint that matches the next step:- **Build checkpoint:** ask how the learner would approach the problem. Follow uponly to resolve meaningful gaps; one focused question can invite a whole approach.-- **Decision checkpoint:** summarize the proposed design and tradeoffs. Offer+- **Design checkpoint:** summarize the proposed design and tradeoffs. Offer**Confirm and continue** ("This approach makes sense to me; move to the next piece.")to record the design and continue planning. This does not authorize code changes.- **Implementation checkpoint:** describe the specific code changes you're ready@@ -51,7 +51,7 @@ Use the checkpoint that matches the next step:These aren't three mandatory stops. Several Build checkpoints may lead to oneconfirmation. When ready to code, the Implementation checkpoint also confirms the-design; skip a separate Decision checkpoint.+design; skip a separate Design checkpoint.At either confirmation, briefly state the proposal, tradeoffs, and scope.Separate the learner's decisions from details you propose@@ -86,7 +86,7 @@ fixed width or word count. Reserve tables for comparisons and proposed additionsUse native AskUserQuestionfor choices (text fallback if unavailable). Reports need no question.Headings use `✦ <Type>: <description>` with exact labels:-`Build checkpoint`, `Decision checkpoint`, `Implementation checkpoint`, `System check`,+`Build checkpoint`, `Design checkpoint`, `Implementation checkpoint`, `System check`,`Why this matters`, `Implementation report`.Normal covers meaningful decisions; Light covers major ones; Frequent adds smallerdiff --git a/skills/learn/state-templates.md b/skills/learn/state-templates.mdindex decef07..9d00bb0 100644--- a/skills/learn/state-templates.md+++ b/skills/learn/state-templates.md@@ -57,7 +57,7 @@ not quotations of a whole exchange. Product preferences establish requirements;they aren't evidence of engineering understanding. Keep learner-proposed reasoningdistinct from concepts Claude explained. Consolidate repeated entries. Keep eachtopic independently readable so it can be loaded without the whole file.-While waiting on a Decision Checkpoint, keep a short `## Pending decision` section+While waiting on a checkpoint, keep a short `## Pending decision` sectionwith the proposed approach and what reply is awaited. Remove it once resolved.Include the checkpoint's decision name and stage: awaiting reasoning, choiceconfirmation, or implementation approval. Record confirmed choices in the map