@rubytech/create-maxy-lite 0.1.4 → 0.1.5

package/payload/skills/work/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: work
+description: Capture, find, and update to-dos in the vault. Use when the user asks to remember a task, add a to-do, note something they need to do, mark a task done, change a due date, assign work to someone, or asks what is on their list or what is outstanding. Owns the Task entity of the maxy-lite SCHEMA.
+---
+
+# Work
+
+A to-do is a **Task** file in `activities/`, one task per file. It is YAML frontmatter plus a markdown body for the detail (context, sub-steps, notes). The authoritative field list is [`SCHEMA.md`](../../schema/SCHEMA.md) under *Activities*, the *Task* entity.
+
+## Task (`activities/<Title>.md`)
+
+Required: `type: task` and `title`. Optional: `due` (`YYYY-MM-DD`), `priority`, `status`, `taskType`, `assignee` (a single link to a Person), `about` (a single link to anything the task concerns), `project` (a single link to a Project), `area`. Set only what you know.
+
+```yaml
+---
+type: task
+title: Call the surveyor
+due: 2026-07-01
+status: not started
+priority: high
+assignee: "[[Jane Doe]]"
+project: "[[House Move]]"
+area: home
+---
+Surveyor quoted last spring. Ask about the loft conversion before booking.
+```
+
+`status` and `priority` are free text the assistant keeps consistent (e.g. `not started` / `in progress` / `done`); `area` must be one of the controlled areas in the SCHEMA. The links resolve to files that must already exist: `assignee` to a Person in `people/`, `project` to a Project in `projects/`, `about` to any entity. Create the target file first if it is not in the vault yet.
+
+## Finding what is outstanding
+
+Grep the frontmatter rather than recalling from memory:
+
+- open tasks: `grep -rL "status: done" activities/ | xargs grep -l "type: task"`
+- tasks for one project: `grep -rl "\[\[House Move\]\]" activities/`
+- tasks assigned to someone: `grep -rl "assignee:.*Jane Doe" activities/`
+- due dates: `grep -rh "^due:" activities/`
+
+Read the matched files for the detail. To mark a task done, edit its `status` field; do not delete the file.
+
+## After every write, validate
+
+After creating or editing any task file, run the deterministic validator over the vault:
+
+```sh
+maxy-lite-validate "$HOME/maxy"
+```
+
+It exits 0 only when every file conforms. If a line names the task you just wrote with `ok=false`, the bracketed error names the violation: `title:missing` (the required title is absent), `area:area` (an area outside the controlled vocabulary), `due:type` (a malformed date), `assignee:dangling` or `project:dangling` (the linked file does not exist), `assignee:target` (the link points at a file of the wrong type). Fix the named field and re-run until that file is `ok=true`. Never leave a task you wrote in a failing state.