@winton979/task-cli 1.3.1 → 1.3.2

package/README.md

@@ -164,11 +164,11 @@ Calling `/decision-log` after every task is easy to forget. As a lower-friction
 /decision-sweep-weekly
 ```
 
-The skill scans archived task and bug briefs from the past 7 days, judges which ones contain a decision worth keeping (cross-task impact, rejected alternatives, counter-intuitive choices, externally driven calls, or instructive cancellations), drafts the entries, and waits for confirmation before appending to `.ai/decisions/decisions.md`.
+The skill scans archived task and bug briefs from the past 7 days, judges which ones contain a decision worth keeping (cross-task impact, rejected alternatives, counter-intuitive choices, externally driven calls, or instructive cancellations), drafts the entries, and waits for confirmation before writing anything to `.ai/decisions/decisions.md`. When a draft overlaps with or updates an existing decision, it should present the old and new versions together and ask whether to append, revise, merge, supersede, or skip.
 
 Use `decision-log` for in-the-moment recording and `decision-sweep-weekly` for periodic cleanup. Either alone is enough; using both is fine.
 
-The decisions file is intentionally narrow. It is meant to hold durable project invariants and reusable constraints, not a running transcript of every local implementation choice.
+The decisions file is intentionally narrow. It is meant to hold durable project invariants and reusable constraints, not a running transcript of every local implementation choice. The default write mode should still be append, but revisions to existing entries are reasonable when explicitly reviewed and confirmed by the user.
 
 ## Philosophy
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@winton979/task-cli",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "description": "Lightweight task workflow CLI for AI-assisted development",
   "license": "MIT",
   "type": "module",

package/src/init.js

@@ -466,10 +466,10 @@ BUG_CANCELLED
 
   'decision-log': {
     name: 'decision-log',
-    description: 'Record implementation decisions to .ai/decisions/decisions.md. Append-only, max 10 lines per entry.',
+    description: 'Record implementation decisions to .ai/decisions/decisions.md. Default to append; if updating an existing decision, require explicit user confirmation first. Max 10 lines per entry.',
     content: `---
 name: decision-log
-description: Record implementation decisions to .ai/decisions/decisions.md. Append-only, max 10 lines per entry.
+description: Record implementation decisions to .ai/decisions/decisions.md. Default to append; if updating an existing decision, require explicit user confirmation first. Max 10 lines per entry.
 user-invocable: true
 ---
 
@@ -506,7 +506,10 @@ What alternatives were rejected.
 Requirements
 
 * Maximum 10 lines per decision
-* Append only
+* Default to append
+* If a new entry appears to revise, merge with, or supersede an existing decision, do not edit or append yet
+* Instead, show the relevant prior entry, explain the overlap or conflict, and ask the user whether to append, revise, merge, supersede, or skip
+* Only modify an existing entry after explicit user confirmation
 * Keep concise
 `,
   },
@@ -536,8 +539,9 @@ Workflow
 4. For each candidate, draft a decision entry using the four-section format.
 5. Present a single review list: every scanned brief with a verdict (write / skip / insufficient info), then the proposed drafts grouped at the end.
 6. Do NOT append anything yet. Wait for the user to confirm which drafts to keep, edit, or drop.
-7. Only after confirmation, append the approved entries to .ai/decisions/decisions.md, oldest first, under the matching YYYY-MM-DD section heading.
-8. Report what was appended and what was skipped.
+7. If a proposed draft appears to overlap with, conflict with, or refine an existing decision, include that prior entry in the review and present explicit options such as append as new, revise existing, merge, supersede, or skip.
+8. Only after confirmation, apply the approved action for each draft. Default to appending new entries oldest first under the matching YYYY-MM-DD section heading; revise or merge only when the user explicitly selects that action.
+9. Report what was appended, revised, merged, superseded, and skipped.
 
 Sediment Conditions
 
@@ -578,9 +582,9 @@ What alternatives were rejected.
 Requirements
 
 * Maximum 10 lines per decision
-* Append only
+* Default to append
 * One date section per day; multiple decisions on the same day stack under the same heading
-* Never edit or delete prior entries
+* Never edit, merge, supersede, or delete prior entries without explicit user confirmation
 `,
   },
 };