Skip to content

fix(productivity): prevent date-label drift and name-variant duplicates in update skill #263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hp-8 wants to merge 1 commit into
base: main
Choose a base branch
from
+16 −0
Open

fix(productivity): prevent date-label drift and name-variant duplicates in update skill #263

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions productivity/skills/update/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,15 @@ Keep your task list and memory current. Two modes:
/productivity:update --comprehensive
```

## Date discipline

Every output reference to a past meeting, a deadline, "yesterday," or a schedule window must resolve cleanly to an ISO date. Two rules:

1. **Cite past events as `YYYY-MM-DD (DayOfWeek)`** — e.g. `2026-05-05 (Tue)`, never bare `Mon May 5` or `May 5`. Compute the day-of-week from the date string (against the current date in `<env>` or via `date -d "<YYYY-MM-DD>" +%a`). Never use a day-of-week label without verifying it from the date.
2. **Never write "yesterday," "Monday," or "this week" without first anchoring on the ISO date.** When a tool returns `2026-05-05T14:00:00Z`, fix the date first, then translate to relative phrasing. The relative wording is output convenience; the ISO date is the source of truth.

This catches a recurring drift mode where a scheduled run mis-labels Tuesday as Monday because the prior day's update used "Monday" and the model carries the phrasing forward without recomputing.

## Default Mode

### 1. Load Current State
Expand Down Expand Up @@ -139,6 +148,13 @@ Let user pick which to add.

### Extra Step: Suggest New Memories

Before flagging any new entity, **fuzzy-match against existing memory** — this catches the drift mode where two name variants of the same person get treated as two people across recurring runs.

- **For people:** search `memory/people/` (and the People table in CLAUDE.md) by (a) full name, (b) email handle / Slack username, and (c) last name alone. First names often surface as nicknames or full forms — "Mike" and "Michael," or "Sue" and "Susan," can refer to the same person. If the email handle or last name matches anyone in memory, treat the name as already-known and update the existing record instead of flagging a new one.
- **For projects/topics:** match against `memory/projects/` and the Active Projects context, including acronym ↔ full-name pairs.

Only after the fuzzy match comes back empty should the entity surface as a new-memory suggestion.

Surface new entities not in memory:

```
Expand Down