dsh-task-ledger 0.1.10 → 0.1.12

package/README.md

@@ -29,7 +29,7 @@ Requirements: dsh. The plugin reads Git repositories; multi-user synchronisation
 | Task list | In-flight tasks with state, tags, owner and last update; tabs for all, unclaimed, in progress, backlog, overdue and stalled |
 | Filters | Workspace, owner and free-text search |
 
-Overdue means seven days elapsed since the task was claimed; stalled means three days without an update. Both are derived from timestamps, never entered by hand.
+Overdue means fourteen days elapsed since the task was claimed; stalled means three days without an update. Both are derived from timestamps, never entered by hand.
 
 ![Unclaimed tasks](https://raw.githubusercontent.com/cq-guojia/dsh-task-ledger/main/assets/screenshots/board-unclaimed.png)
 
@@ -72,6 +72,18 @@ The plugin only reads this structure, except for the actions listed above, which
 
 The board is a view over the ledger; the ledger itself is driven by what you say to the agent — open a task, claim it, record progress, hand it back, close it, cancel it. Which phrase triggers which operation, and the rules the agent follows, are listed in the [`task-ledger`](https://www.npmjs.com/package/task-ledger) README.
 
+### Recommended: put it in your rules file
+
+The skill only loads when a request matches an explicit task intent, and "should this piece of work be tracked" is not one of them. A standing rule in the project's `AGENTS.md` (or whichever rules file your agent reads) is far more reliable on its own. Copy this block:
+
+```markdown
+- **Every piece of task progress, work item and work log (create / advance / query / close) goes through the `task-ledger` skill**; answer progress and history questions from it, never from conversation memory or a hand-rolled list.
+- **Creation anchor**: hand something to `task-ledger` only when the user explicitly asks for a new task ("open a task", "log this first", "create a task"). Questions, queries, discussion and small incidental edits do not count — ask when unsure, and never create a task without an explicit instruction.
+- **Ask in passing**: when the user is pushing forward work that spans turns (this turn ends with actions still on your plate) and has never mentioned tracking it, ask once after answering: "你现在这个任务是需要帮你建一个台账吗？（如果无需，忽略这句话，也不用去回复。）" Once asked in a session, do not ask again; no reply means ignore it.
+```
+
+Without it the skill still works — it just acts only when you mention the task yourself.
+
 ## Other agents
 
 Agents that are not dsh can install the same skill on its own — with the skills CLI, or by copying `packages/skill` into their skills directory; see the [`task-ledger`](https://www.npmjs.com/package/task-ledger) package for per-agent installation.

package/README.zh-CN.md

@@ -29,7 +29,7 @@ dsh plugin add dsh-task-ledger
 | 任务列表 | 在办任务的状态、标签、责任人与最后更新时间；可按全部、待认领、进行中、积压、逾期、停滞切换 |
 | 筛选 | 工作区、执行人与关键词检索 |
 
-「逾期」指认领后已过七天；「停滞」指三天没有进展。两者均由时间戳推导，不可手工填写。
+「逾期」指认领后已过十四天；「停滞」指三天没有进展。两者均由时间戳推导，不可手工填写。
 
 ![待认领任务](https://raw.githubusercontent.com/cq-guojia/dsh-task-ledger/main/assets/screenshots/board-unclaimed.png)
 
@@ -72,6 +72,18 @@ ledger/
 
 看板只是台账之上的一层视图；台账本身由你对代理说的话驱动 —— 建任务、认领、记进度、退回、结案、取消。哪句话触发哪个操作，以及代理必须遵守的约束，见 [`task-ledger`](https://www.npmjs.com/package/task-ledger) 包的 README。
 
+### 建议把它写进规则文件
+
+skill 只在请求命中意图时才加载 —— 你手上这件活该不该记账，不在这几个触发词里。所以在项目的 `AGENTS.md`（或等价的代理规则文件）里放一段常驻规则，比只装 skill 稳得多。复制下面这块即可：
+
+```markdown
+- **凡任务进度、工作事项与工作日志（新建 / 推进 / 查询 / 结案）一律调用 `task-ledger` skill 管理**；进度 / 历史类问题一律走它作答，不凭对话记忆或自建清单顶替。
+- **开工锚点**：仅当用户明确说要新建（如「开个新坑」「先记一下」「建个任务」）才交给 `task-ledger` 登记；提问 / 查询 / 讨论 / 顺手小改不算，拿不准先问，未经用户明确指令不得擅自新建任务。
+- **顺手问一句**：用户在推进一件跨轮的事（这轮答完、手上还有下一步动作没做完）、却从没提过记账时，答完问一次「你现在这个任务是需要帮你建一个台账吗？（如果无需，忽略这句话，也不用去回复。）」；本会话问过一次就别再问，无回复就忽略。
+```
+
+不写这段也能用，只是它只在你明确提到任务时才会动。
+
 ## 其他代理
 
 非 dsh 的代理可单独安装同一份 skill —— 用 skills CLI，或把 `packages/skill` 复制进其技能目录；各代理的安装方式见 [`task-ledger`](https://www.npmjs.com/package/task-ledger) 包。