@neurodock/cli 0.8.2 → 0.9.0

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # @neurodock/cli changelog
 
+## 0.9.0
+
+### Minor Changes
+
+- 1c76c2c: add `neurodock install-skills` and bundle the per-neurotype skills into the cli
+
+  the cli now ships the six per-neurotype skills (their `SKILL.md` files,
+  generated into `dist/assets/skills/` at build time from `packages/skills/`).
+  the new `neurodock install-skills` command copies them into the client's
+  personal skills directory (`~/.claude/skills/neurodock-<name>/` for claude code
+  and claude desktop; cursor is skipped). it supports `--client`, `--dry-run`,
+  and `--yes`, and is idempotent.
+
+  `install-all`, `setup`, and `update` now install the skills as part of the
+  one-command happy path; opt out with `--no-skills` (mirrors `--no-native-host`).
+  the skills step is best-effort — a failure warns but does not fail the command.
+
 ## 0.8.2
 
 ### Patch Changes

package/README.md

@@ -2,7 +2,7 @@
 
 The `neurodock` installer and diagnostic CLI for [NeuroDock](https://neurodock.org/) — a local-first cognitive substrate for neurodivergent professionals.
 
-Status: **v0.6.2**.
+Status: **v0.8.2**.
 
 ## Quickstart
 
@@ -34,8 +34,9 @@ install, `install-all` runs the `pip install` step automatically.
 
 | Command                      | What it does                                                                                                                                                    |
 | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `neurodock install-all`      | One-command first-time install: pip-install the six servers, wire every detected client, copy the starter profile.                                              |
+| `neurodock install-all`      | One-command first-time install: pip-install the six servers, wire every detected client, copy the starter profile, install the per-neurotype skills.            |
 | `neurodock init`             | Install MCP servers into Claude Desktop / Claude Code / Cursor (the wiring half of `install-all`).                                                              |
+| `neurodock install-skills`   | Copy the per-neurotype skills into your client's personal skills directory (`~/.claude/skills` for Claude Code / Claude Desktop). Cursor is skipped.            |
 | `neurodock doctor`           | Diagnose your install — profile validity, client wiring, tool availability.                                                                                     |
 | `neurodock validate`         | Schema-validate a profile file (`~/.neurodock/profile.yaml` by default).                                                                                        |
 | `neurodock update`           | Upgrade NeuroDock to the latest version — re-installs the six MCP servers via pip/uv and re-wires client configs.                                               |
@@ -60,16 +61,47 @@ install, `install-all` runs the `pip install` step automatically.
 neurodock install-all [--client=claude-desktop|claude-code|cursor|all] \
                       [--profile=minimal|example] \
                       [--installer=uv|pip|auto] \
-                      [--skip-install] [--yes] [--dry-run]
+                      [--skip-install] [--yes] [--dry-run] \
+                      [--no-native-host] [--no-skills]
 ```
 
 Single-command first-time install. Prefers `uv` if it is on PATH; falls
 back to `python -m pip`. After install, verifies each server entrypoint
-is on PATH with `<command> --help`, then delegates to `init` to wire
-clients.
+is on PATH with `<command> --help`, delegates to `init` to wire clients,
+registers the optional native-messaging host, and installs the
+per-neurotype skills into `~/.claude/skills`.
 
-Exit codes: `0` ok, `1` an entrypoint is missing from PATH after
-install, `2` init failed.
+- `--no-native-host` skips registering the native-messaging host.
+- `--no-skills` skips copying the per-neurotype skills.
+
+Both steps are best-effort: a failure in either emits a warning but does
+not fail the command (the six MCP servers are the core). Exit codes:
+`0` ok, `1` an entrypoint is missing from PATH after install, `2` init
+failed.
+
+### `neurodock install-skills`
+
+```
+neurodock install-skills [--client=claude-desktop|claude-code|cursor|all] \
+                         [--dry-run] [--yes]
+```
+
+Copies the six per-neurotype skills bundled in the CLI tarball into the
+client's personal skills directory so Claude Code / Claude Desktop
+discover them. Each skill installs as
+`~/.claude/skills/neurodock-<name>/SKILL.md` (namespaced so it is
+collision-free and recognisably NeuroDock's).
+
+- Claude Code and Claude Desktop share `~/.claude/skills`; the command
+  de-duplicates so the files are written once.
+- Cursor has no skills system today and is skipped with a notice (never
+  an error).
+- `--dry-run` prints the planned targets and exits 0 without writing.
+- Idempotent: re-running refreshes each `SKILL.md` in place.
+
+This is also run automatically by `install-all` / `setup` / `update`
+unless you pass `--no-skills`. Exit codes: `0` ok, `1` no bundled skills
+were found (a packaging bug).
 
 ### `neurodock init`
 
@@ -100,14 +132,16 @@ key are skipped unless `--yes` is supplied.
 neurodock update [--client=claude-desktop|claude-code|cursor|all] \
                  [--profile=minimal|example] \
                  [--installer=uv|pip|auto] \
-                 [--skip-install] [--yes] [--dry-run] [--no-native-host]
+                 [--skip-install] [--yes] [--dry-run] \
+                 [--no-native-host] [--no-skills]
 ```
 
 One-command upgrade. Same code path as `install-all` — re-runs
 `pip install --upgrade` (or `uv tool install`) for every NeuroDock MCP
-server, re-wires the detected MCP clients, and re-registers the
-optional native-messaging host. Exit codes match `install-all`:
-`0` ok, `1` an entrypoint is missing from PATH, `2` init failed.
+server, re-wires the detected MCP clients, re-registers the optional
+native-messaging host, and refreshes the per-neurotype skills (skip with
+`--no-skills`). Exit codes match `install-all`: `0` ok, `1` an
+entrypoint is missing from PATH, `2` init failed.
 
 ### `neurodock sync`
 

package/dist/assets/schemas/neurotype-addenda.schema.json

@@ -0,0 +1,167 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://schemas.neurodock.org/neurotype-addenda/v1/neurotype-addenda.schema.json",
+  "title": "NeuroDock Neurotype Addenda Artifact",
+  "description": "Validates the language-neutral, enum-keyed prompt-shaping content artifact (data/neurotype-addenda/v1.json). This artifact is CONTENT, not schema shape (ADR 0011): it carries the per-(tool x neurotype) prose blocks that NeuroDock surfaces append to a model prompt, plus the fusion rule, priority ordering, framing, output-format guidance, and the cross-cutting voice-input / tourette / other / generic-fallback blocks. Additive-only versioning: new tools, new neurotypes, and new optional top-level keys are non-breaking. Unknown keys are permitted for forward-compatibility where appropriate.",
+  "type": "object",
+  "additionalProperties": true,
+  "required": [
+    "artifact_version",
+    "fusion",
+    "priority",
+    "framing",
+    "output_format",
+    "voice_input",
+    "tourette",
+    "other",
+    "generic",
+    "tools"
+  ],
+  "properties": {
+    "$schema": {
+      "type": "string",
+      "description": "Optional pointer back to this schema's $id."
+    },
+    "artifact_version": {
+      "type": "string",
+      "description": "Semantic version of the artifact content. Additive changes bump minor; a breaking re-shape forks to a new vN.json + a new schema $id.",
+      "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+$",
+      "examples": ["1.0.0"]
+    },
+    "description": {
+      "type": "string"
+    },
+    "tokens": {
+      "type": "array",
+      "description": "The complete set of interpolation tokens any block may contain. Documentation only; the assembler is the authority.",
+      "items": { "type": "string" }
+    },
+    "fusion": {
+      "type": "object",
+      "description": "The AuDHD substitution rule. When the input set lists the `result` neurotype directly, OR lists every neurotype in `all_of`, the `result` block is substituted and every neurotype in `remove` is dropped.",
+      "additionalProperties": true,
+      "required": ["result", "all_of", "remove"],
+      "properties": {
+        "description": { "type": "string" },
+        "result": { "type": "string" },
+        "any_of": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "all_of": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "remove": {
+          "type": "array",
+          "items": { "type": "string" }
+        }
+      }
+    },
+    "priority": {
+      "type": "array",
+      "description": "Neurotype ordering. Higher-priority addenda are placed LATER in the assembled prompt (recency bias). Neurotypes are sorted by their index in this list.",
+      "items": { "type": "string" },
+      "minItems": 1
+    },
+    "framing": {
+      "type": "object",
+      "description": "The wrapper, header, footer, separators, and conflict footer that surround the per-neurotype blocks.",
+      "additionalProperties": true,
+      "required": [
+        "wrapper_prefix",
+        "wrapper_suffix",
+        "section_separator",
+        "block_line_separator",
+        "header",
+        "footer",
+        "conflict_footer_min_neurotypes",
+        "conflict_footer"
+      ],
+      "properties": {
+        "wrapper_prefix": { "type": "string" },
+        "wrapper_suffix": { "type": "string" },
+        "section_separator": { "type": "string" },
+        "block_line_separator": { "type": "string" },
+        "header": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "footer": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "conflict_footer_min_neurotypes": {
+          "type": "integer",
+          "minimum": 1
+        },
+        "conflict_footer": { "type": "string" }
+      }
+    },
+    "output_format": {
+      "type": "object",
+      "description": "Per-output-format guidance. The assembler renders `prefix + format + separator + descriptions[format]`.",
+      "additionalProperties": true,
+      "required": ["prefix", "separator", "descriptions", "default"],
+      "properties": {
+        "prefix": { "type": "string" },
+        "separator": { "type": "string" },
+        "descriptions": {
+          "type": "object",
+          "description": "Map of output-format enum value to its one-line description.",
+          "additionalProperties": { "type": "string" },
+          "minProperties": 1
+        },
+        "default": { "type": "string" }
+      }
+    },
+    "voice_input": {
+      "type": "object",
+      "description": "Cross-cutting voice-input block. Emitted when voice input is preferred, before the per-neurotype blocks.",
+      "additionalProperties": true,
+      "required": ["block"],
+      "properties": {
+        "block": { "$ref": "#/$defs/block" }
+      }
+    },
+    "tourette": {
+      "type": "object",
+      "description": "Tourette special block. Tool-independent; rendered whenever `tourette` is in the effective set.",
+      "additionalProperties": true,
+      "required": ["block"],
+      "properties": {
+        "block": { "$ref": "#/$defs/block" }
+      }
+    },
+    "other": {
+      "type": "object",
+      "description": "Self-described block. Carries the {notes} interpolation token; rendered when `other` is selected with notes, or appended as a footer when notes are present without `other`.",
+      "additionalProperties": true,
+      "required": ["block"],
+      "properties": {
+        "block": { "$ref": "#/$defs/block" }
+      }
+    },
+    "generic": {
+      "type": "object",
+      "description": "Generic per-neurotype fallback blocks (no tool context, or no concrete per-tool block for the pair). Keyed by neurotype enum value.",
+      "additionalProperties": { "$ref": "#/$defs/block" }
+    },
+    "tools": {
+      "type": "object",
+      "description": "Per-tool matrices of concrete per-neurotype blocks. Keyed by tool name, then by neurotype enum value. Additive: a new tool or a new neurotype within a tool is non-breaking.",
+      "additionalProperties": {
+        "type": "object",
+        "additionalProperties": { "$ref": "#/$defs/block" }
+      }
+    }
+  },
+  "$defs": {
+    "block": {
+      "type": "array",
+      "description": "A prose block: an ordered list of lines joined with the framing block_line_separator. Lines may contain {max_chunk_size} and/or {notes} interpolation tokens.",
+      "items": { "type": "string" },
+      "minItems": 1
+    }
+  }
+}

package/dist/assets/schemas/profile.example.yaml

@@ -62,6 +62,15 @@ preferences:
   #   system_default          — your OS choice
   reading_font_hint: "atkinson_hyperlegible"
 
+  # How much space do you want between lines of text?
+  # This is a hint for apps that show NeuroDock's output as styled text.
+  # Options:
+  #   compact  — lines sit closer together (more text fits on screen)
+  #   default  — the app's own everyday spacing
+  #   relaxed  — extra space between lines; pairs with atkinson_hyperlegible
+  # Leave it out and the app just uses its own spacing.
+  line_height_hint: "relaxed"
+
   # Do you want visual animations turned on?
   # Options:
   #   reduced  — no animations (default; safest for vestibular sensitivity)

package/dist/assets/schemas/profile.schema.json

@@ -90,6 +90,17 @@
           "enum": ["reduced", "system", "full"],
           "default": "reduced",
           "description": "Animation policy hint. 'reduced' = no animation, no transitions, no auto-scroll (default). 'system' = follow the OS prefers-reduced-motion setting. 'full' = animations allowed."
+        },
+        "line_height_hint": {
+          "type": "string",
+          "enum": ["compact", "default", "relaxed"],
+          "description": "Optional (added v0.1.x per ADR 0011). Line-height hint for any client that renders NeuroDock output as HTML or rich text, sitting alongside 'reading_font_hint'. A categorical band rather than a raw multiplier so each client maps it to its own CSS line-height. CONFORMANCE FLOOR: clients MUST NOT render body-paragraph line spacing below 1.5 regardless of band (WCAG 1.4.8 Visual Presentation / 1.4.12 Text Spacing). The bands are advisory line-height ratios relative to font size for body paragraphs; headings and other non-body text MAY be tighter. Per-band anchors: 'compact' ≈ 1.5 — the floor itself, a power-user opt-in for more text per viewport that still respects the 1.5 minimum (for readers who find generous spacing scatters their eye-line and prefer denser text, the dual of why 'relaxed' exists); 'default' ≈ 1.5–1.6 — the client's own comfortable default within the conformant range; 'relaxed' ≈ 1.65–1.8 — generous line spacing (~1.65 is the project body line-height) and the evidence-based pairing with 'atkinson_hyperlegible' for dyslexia, which is why dyslexia-aware presets set it. Read-when-present, neutral-when-absent: an untailored client ignores it; absence is NOT an error. The loader applies no value when absent. Self-ID never gates this (ADR 0004/0011).",
+          "examples": ["relaxed", "default"]
+        },
+        "voice_input_preferred": {
+          "type": "boolean",
+          "description": "Optional (added v0.1.x per ADR 0011). When true, the user predominantly dictates rather than types for sustained work (common for dyspraxic users). Downstream skills that emit code or structured text MUST NOT assume the user can hand-edit fiddly punctuation cheaply: keep examples copy-pasteable as a single block rather than scattered across inline edits. Read by the shaping layer; absence means 'no preference' and is the same as today's behaviour. Consumer pending; schema-only in this release.",
+          "examples": [true]
         }
       }
     },
@@ -121,6 +132,62 @@
           "enum": ["auto_close", "error"],
           "default": "auto_close",
           "description": "Behaviour of mark_session_start when a prior session is still open. 'auto_close' (default, charitable) closes the prior session and returns its metadata so the skill can surface it. 'error' refuses to start a new session until the prior one is explicitly closed. See ADR 0001, open question 3."
+        },
+        "calendar_phase": {
+          "type": "string",
+          "enum": ["teaching", "marking", "exam", "deadlines", "break"],
+          "description": "Optional (added v0.1.x per ADR 0011). Self-declared phase of the user's term/semester so skills can shift defaults across the calendar: tighter break cadence during 'marking' / 'exam', deadline-cluster awareness during 'deadlines' (e.g. week 12), looser during 'break'. Surfaced by the educator-semester and student-university presets. The neurotype is never a branch point (ADR 0004/0011); this is a user input the shaping layer reads, neutral-when-absent. Consumer pending (mcp-chronometric); schema-only in this release.",
+          "examples": ["teaching", "marking"]
+        },
+        "weekday_overrides": {
+          "type": "object",
+          "description": "Optional (added v0.1.x per ADR 0011). Per-weekday overrides for 'end_of_day_local' and 'hyperfocus_break_minutes', covering late-office-hours, Wednesday-afternoon-class, and library-day-vs-lecture-day patterns without forcing a whole-profile swap. Keys are lowercase English weekday names; only the seven weekdays are accepted (a misspelt key is a silent no-op, so unknown keys are rejected here rather than preserved). Each value is an override object reusing the same patterns/ranges as the top-level chronometric fields; an empty override object is valid. A weekday absent from the map inherits the top-level chronometric values. Consumer pending (mcp-chronometric); schema-only in this release.",
+          "additionalProperties": false,
+          "properties": {
+            "monday": { "$ref": "#/$defs/weekdayOverride" },
+            "tuesday": { "$ref": "#/$defs/weekdayOverride" },
+            "wednesday": { "$ref": "#/$defs/weekdayOverride" },
+            "thursday": { "$ref": "#/$defs/weekdayOverride" },
+            "friday": { "$ref": "#/$defs/weekdayOverride" },
+            "saturday": { "$ref": "#/$defs/weekdayOverride" },
+            "sunday": { "$ref": "#/$defs/weekdayOverride" }
+          },
+          "examples": [
+            {
+              "wednesday": { "end_of_day_local": "18:30" },
+              "saturday": { "hyperfocus_break_minutes": 120 }
+            }
+          ]
+        },
+        "protected_windows": {
+          "type": "array",
+          "description": "Optional (added v0.1.x per ADR 0011). Local-time ranges (lunch, post-EOD evening, scheduled lectures, lab times) where the hyperfocus monitor should HARD-SURFACE rather than nudge — the strict rung of the escalation ladder, applied because the window itself is protected, not because a session has run long. Each entry is a 'HH:MM'-'HH:MM' range with an optional human label; ranges are interpreted in the user's local timezone and a range whose 'end' is earlier than its 'start' is treated as wrapping past midnight by the consumer. An empty list is valid. Consumer pending (mcp-chronometric); schema-only in this release.",
+          "items": { "$ref": "#/$defs/protectedWindow" },
+          "examples": [
+            [
+              { "start": "12:00", "end": "12:30", "label": "lunch" },
+              { "start": "17:00", "end": "23:59", "label": "evening" }
+            ]
+          ]
+        },
+        "deadline_cluster_awareness": {
+          "type": "boolean",
+          "description": "Optional (added v0.1.x per ADR 0011). When true, planning skills surface deadline proximity and shift the break-cadence math when work clusters (e.g. three assignments due in a single week). Set by the student-university preset. Read by planning skills; absence means today's behaviour (no clustering adjustment). Consumer pending (task-fractionator); schema-only in this release.",
+          "examples": [true]
+        },
+        "time_buffer_multiplier": {
+          "type": "number",
+          "minimum": 1.0,
+          "maximum": 3.0,
+          "default": 1.0,
+          "description": "Optional (added v0.1.x per ADR 0011). Multiplier that pads presented time estimates because real-world execution time for motor-heavy tasks is systematically underestimated (e.g. 1.3 = +30%, the value the dyspraxia preset sets). Range 1.0..3.0; the neutral default 1.0 reproduces today's unpadded behaviour so an untouched profile is unchanged. Read by planning skills to scale the estimates they present; the underlying estimate is not altered. Consumer pending (task-fractionator); schema-only in this release.",
+          "examples": [1.0, 1.3]
+        },
+        "motor_fatigue_aware": {
+          "type": "boolean",
+          "default": false,
+          "description": "Optional (added v0.1.x per ADR 0011). When true, the hyperfocus monitor weights motor activity (click / keystroke / window-switch volume) into the fatigue signal rather than relying on continuous-session length alone — cognitive sharpness and motor exhaustion can coexist (set by the dyspraxia preset). The neutral default false reproduces today's session-length-only behaviour. Reading motor activity is still gated by 'privacy.os_idle_consent' and the relevant OS-input consents; this flag only declares the preference. Consumer pending (mcp-chronometric); schema-only in this release.",
+          "examples": [true]
         }
       }
     },
@@ -176,6 +243,55 @@
       }
     }
   },
+  "$defs": {
+    "weekdayOverride": {
+      "type": "object",
+      "description": "Per-weekday override for the chronometric fields that vary by day. Both members are optional and reuse the same validation as their top-level counterparts; an empty object means 'this weekday is named but inherits the top-level values'. additionalProperties is false because an unknown key here is almost always a typo that would silently do nothing.",
+      "additionalProperties": false,
+      "properties": {
+        "end_of_day_local": {
+          "type": "string",
+          "pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]$",
+          "description": "Override of 'chronometric.end_of_day_local' for this weekday, as 'HH:MM' (24h) in the user's local timezone. Same pattern as the top-level field.",
+          "examples": ["17:00", "18:30"]
+        },
+        "hyperfocus_break_minutes": {
+          "type": "integer",
+          "minimum": 15,
+          "maximum": 240,
+          "description": "Override of 'chronometric.hyperfocus_break_minutes' for this weekday. Same 15..240 range as the top-level field; re-anchors the 'nudge' rung for this day only.",
+          "examples": [60, 120]
+        }
+      }
+    },
+    "protectedWindow": {
+      "type": "object",
+      "description": "A single local-time range where the hyperfocus monitor hard-surfaces. 'start' and 'end' are required 'HH:MM' (24h) strings; 'label' is an optional human-readable name. additionalProperties is false to catch typos in this small, fixed shape.",
+      "additionalProperties": false,
+      "required": ["start", "end"],
+      "properties": {
+        "start": {
+          "type": "string",
+          "pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]$",
+          "description": "Window start, 'HH:MM' (24h), local timezone.",
+          "examples": ["12:00", "17:00"]
+        },
+        "end": {
+          "type": "string",
+          "pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]$",
+          "description": "Window end, 'HH:MM' (24h), local timezone. An 'end' earlier than 'start' is treated by the consumer as wrapping past midnight.",
+          "examples": ["12:30", "23:59"]
+        },
+        "label": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 80,
+          "description": "Optional human-readable label for the window, surfaced in any notice the monitor emits.",
+          "examples": ["lunch", "evening", "lecture"]
+        }
+      }
+    }
+  },
   "examples": [
     {
       "identity": {

package/dist/assets/skills/adhd-daily-planner/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: adhd-daily-planner
+version: 0.1.0
+description: Morning brief — what changed overnight, what matters today, one next-action per project.
+neurotypes: ["adhd", "audhd"]
+status: stable
+triggers:
+  - command: "/resume monday"
+  - command: "/morning-brief"
+  - phrase: "what's on today"
+  - phrase: "plan my day"
+  - phrase: "what should I do today"
+mcp_dependencies:
+  - server: mcp-chronometric
+    tools: [get_time_context]
+  - server: mcp-cognitive-graph
+    tools: [weekly_rollup, recall_decisions]
+  - server: mcp-task-fractionator
+    tools: [next_one]
+profile_dependencies:
+  - identity.neurotypes
+  - preferences.output_format
+  - preferences.max_chunk_size
+  - chronometric.end_of_day_local
+license: AGPL-3.0-or-later
+authors:
+  - neurodock-core
+---
+
+# adhd-daily-planner
+
+This skill produces a morning brief: what changed overnight in the user's projects, what matters today, and one concrete next-action per project. On Monday it is the full weekly stack. On other weekdays it is a lighter daily-pulse.
+
+## Activation criteria
+
+Activate when any of the following is true:
+
+- The user types `/resume monday` or `/morning-brief`.
+- The user's message contains one of: `what's on today`, `plan my day`, `what should I do today`, `monday morning`.
+- This is the user's first interaction of a new local day AND `preferences.output_format` is `answer_first` (treat as an implicit invitation, not an obligation — see "Do not" below).
+
+Do not activate inside a session that has already been running for more than thirty minutes; that conversation has its own context already.
+
+## Operating instructions
+
+Follow these steps in order. Do not skip steps. Do not improvise additional tool calls.
+
+1. **Anchor the day.** Call `mcp-chronometric.get_time_context()`. Note `day_of_week`, `energy_zone`, and `current_session_length`. If `day_of_week` is `Monday`, this is a **weekly brief**. Otherwise it is a **daily-light brief**.
+
+2. **Pull the weekly rollup, scoped or unscoped.**
+
+   - For a weekly brief: call `mcp-cognitive-graph.weekly_rollup()` with no project filter to discover which projects had activity in the trailing seven days. Rank projects by the most recent `decisions[].decided_on` (falling back to most recent `blockers[].recorded_at` when there are no decisions).
+   - For a daily-light brief: same call, same ranking.
+   - Cap the project list at `preferences.max_chunk_size` (default 5). If more projects had activity, note the count of elided projects in the closing line — do not name them.
+
+3. **For each retained project, get its rollup.** Call `mcp-cognitive-graph.weekly_rollup(project=<name>)` once per project. Use the returned `decisions`, `blockers`, and `next_actions` fields verbatim. Do not paraphrase decision names.
+
+4. **Decide whether to surface decision detail.** If a project has decisions in the last seven days but `weekly_rollup.next_actions` is empty for that project, call `mcp-cognitive-graph.recall_decisions(project=<name>, since=<thirty days ago>)` once to surface up to two recent decisions that may need follow-up. Skip this call when `next_actions` is already populated.
+
+5. **Get one concrete next-action per project.** Call `mcp-task-fractionator.next_one(project=<name>)` for each project. Three outcomes:
+
+   - Success with `confidence >= 0.7` — quote the task title and the confidence value.
+   - Success with `confidence < 0.7` — quote the title and explicitly say "low confidence" with the value. Do not pretend certainty.
+   - Error `NO_TASKS_AVAILABLE` — say "no decomposed tasks for this project; consider `decompose` if it's time to plan it." Do not fabricate a task.
+   - Any other error — note the error code in the project section and move on.
+
+6. **Render the brief.** See "Output format" below.
+
+7. **Stop.** Do not propose a calendar rearrangement, a follow-up question, or "shall I start the first task?". The brief is the deliverable.
+
+## Output format
+
+Strict "Answer First" structure. The first sentence must fit in 80 characters and must name the day's shape in plain prose.
+
+```
+<One paragraph, ≤ 80 chars in the first sentence, plain prose. State which day it is,
+the brief type (weekly or daily-light), and the count of projects covered. No
+exclamation marks. No "let's crush it" register.>
+
+### <Project name>
+- Most recent decision: <decision name> (<decided_on>, conf <confidence>)
+- Blocker: <blocker literal or "none">
+- Next: <next_one.task.title> (<estimated_minutes> min, conf <confidence>)
+
+### <Project name>
+- ...
+
+---
+Elided <N> further projects with activity this week.
+Energy zone right now: <energy_zone>. End-of-day stated as <chronometric.end_of_day_local>.
+This brief is not a productivity scorecard. Yesterday's incomplete items are not graded.
+```
+
+Rules:
+
+- Maximum three bullets per project. If a project has no blocker, write `Blocker: none` — do not invent one.
+- Project sections appear in the order produced by step 2's ranking.
+- Confidence is always rendered as a number with two decimal places, never as a word.
+- The closing block is mandatory. The "not a scorecard" line grounds the LLM and the user.
+
+If `weekly_rollup()` returned zero projects in the trailing seven days, emit the empty-graph response instead:
+
+```
+No projects in the last 30 days. Nothing to brief against.
+
+If you'd like to start one, the next step is `mark_session_start(intent=<your intent>)`
+in mcp-chronometric — that anchors today and gives tomorrow's brief something to draw on.
+```
+
+## Distress signal handling
+
+If the user's invoking message contains overwhelm phrases — `I can't`, `too much`, `everything is on fire`, `I'm stuck`, `exhausted`, `burned out` — reduce the project cap to **3** instead of `preferences.max_chunk_size`, omit the confidence numbers (state "high" / "medium" / "low" instead), and append one sentence to the closing block: `If three is still too many right now, ask for "just one project" and I'll narrow further.` Do not lecture. Do not diagnose.
+
+## Do not
+
+- Do not use the words "superpower", "crusher", "smash", "let's go", "you got this", "differently abled".
+- Do not enumerate yesterday's incomplete items.
+- Do not compute or display a productivity score.
+- Do not propose calendar buffer transitions unless the user's MCP environment surfaces calendar data through a tool you can call. **Calendar integration is not in scope for v0.1.0 of this skill** — if no calendar tool is wired, omit the "buffer transitions" feature silently.
+- Do not call `next_one` for a project with no decisions and no blockers — that project does not need a next-action surfaced, it needs the user to decide whether to retire it.
+- Do not invent project names. Only use names that came back from `weekly_rollup`.
+- Do not exceed three bullets per project even if more data exists.
+- Do not activate inside an ongoing >30 min session.
+
+## What this skill is not
+
+It is not a productivity maximiser. It is not a guilt trip about yesterday. It is a once-a-day surface area for projects, decisions, and one tangible next thing.
+
+## Examples
+
+See `tests/01-monday-morning-brief.md`, `tests/02-empty-graph-fallback.md`, and `tests/03-multi-project-stack.md` for the full invocation traces.