@winton979/task-cli 1.2.1 → 1.3.0

package/README.md

@@ -129,6 +129,7 @@ BUG_READY
 ### Other
 
 * decision-log
+* decision-sweep-weekly
 
 ---
 
@@ -153,6 +154,18 @@ BUG_READY
 
 ---
 
+## Weekly Decision Sweep
+
+Calling `/decision-log` after every task is easy to forget. As a lower-friction alternative, run `decision-sweep-weekly` once per week (Friday is a natural fit):
+
+```
+/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`.
+
+Use `decision-log` for in-the-moment recording and `decision-sweep-weekly` for periodic cleanup. Either alone is enough; using both is fine.
+
 ## Philosophy
 
 Task CLI is intentionally lightweight.
@@ -223,7 +236,7 @@ task refresh
 This will:
 
 * keep `.ai/tasks`, `.ai/bugs`, and `.ai/decisions`
-* remove only these managed skills from `.claude/skills/` and `.codex/skills/`: `task-fast`, `task-explore`, `task-implement`, `task-review`, `task-cancel`, `bug-explore`, `bug-fix`, `bug-review`, `bug-cancel`, `decision-log`
+* remove only these managed skills from `.claude/skills/` and `.codex/skills/`: `task-fast`, `task-explore`, `task-implement`, `task-review`, `task-cancel`, `bug-explore`, `bug-fix`, `bug-review`, `bug-cancel`, `decision-log`, `decision-sweep-weekly`
 * reinstall the latest versions of those skills
 
 This avoids touching unrelated custom skills in the same project.

package/package.json

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

package/src/init.js

@@ -485,6 +485,79 @@ Requirements
 * Maximum 10 lines per decision
 * Append only
 * Keep concise
+`,
+  },
+
+  'decision-sweep-weekly': {
+    name: 'decision-sweep-weekly',
+    description: 'Weekly sweep of recent task and bug briefs to decide which deserve a decision-log entry. Proposes entries for confirmation before appending.',
+    content: `---
+name: decision-sweep-weekly
+description: Weekly sweep of recent task and bug briefs to decide which deserve a decision-log entry. Proposes entries for confirmation before appending.
+user-invocable: true
+---
+
+Purpose
+
+Batch-review the past week of work and sediment only the decisions that outlive a single task. Replaces per-task reminders with one weekly pass.
+
+When to Run
+
+Run once per week, ideally on Friday. May also run ad-hoc after a busy stretch.
+
+Workflow
+
+1. Scan briefs created in the last 7 days under .ai/tasks/archive/ and .ai/bugs/archive/. Filter by filename date prefix YYYY-MM-DD. If a brief lacks a date prefix, fall back to filesystem mtime.
+2. For cancelled briefs in either archive, treat the abandonment itself as potential decision material.
+3. Evaluate each brief against the Sediment Conditions below.
+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.
+
+Sediment Conditions
+
+A brief becomes a decision entry if it satisfies any of:
+
+* Cross-task impact: the choice constrains how future tasks must be written.
+* A concrete alternative was rejected and someone could plausibly pick it later.
+* Counter-intuitive choice: code reads like an anti-pattern but is intentional.
+* Externally driven: compliance, performance, compatibility, or a third-party API limit forced the call.
+* A cancelled attempt whose failure is itself a useful conclusion.
+
+Skip Conditions
+
+* Affects only the implementation detail of one task.
+* A temporary or unsettled conclusion.
+* A bare fact with no decision behind it.
+
+Entry Format
+
+## YYYY-MM-DD
+
+### Problem
+
+What issue was encountered.
+
+### Decision
+
+What was chosen.
+
+### Reason
+
+Why this choice was made.
+
+### Alternatives Considered
+
+What alternatives were rejected.
+
+Requirements
+
+* Maximum 10 lines per decision
+* Append only
+* One date section per day; multiple decisions on the same day stack under the same heading
+* Never edit or delete prior entries
 `,
   },
 };
@@ -649,7 +722,8 @@ export function init(cwd, { fs, path, log }) {
   fast:  task-fast
   task:  task-explore -> task-implement -> task-review | task-cancel
   bug:   bug-explore -> bug-fix -> bug-review | bug-cancel
-  other: decision-log`);
+  other: decision-log
+  sweep: decision-sweep-weekly`);
 }
 
 export function refresh(cwd, { fs, path, log }) {
@@ -683,7 +757,8 @@ export function refresh(cwd, { fs, path, log }) {
   fast:  task-fast
   task:  task-explore -> task-implement -> task-review | task-cancel
   bug:   bug-explore -> bug-fix -> bug-review | bug-cancel
-  other: decision-log`);
+  other: decision-log
+  sweep: decision-sweep-weekly`);
 }
 
 export function doctor(cwd, { fs, path, log }) {