From 1794cd1b38b7bb74dc37a2e79825141cfb62fcfe Mon Sep 17 00:00:00 2001 From: Jenny Ferries Date: Fri, 17 Jul 2026 12:46:31 -0700 Subject: [PATCH] fix: desk-open includes .signals/ dir, signal-write documents subtype contract - desk-open: standard desk structure now creates .signals/ directory (prevents first signal-write from failing on missing parent dir) - signal-write: note that dashboard reads subtype field, falls back to signal_type for backward compat Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 26faf13e-639c-4a21-ac05-c0dc2bff7c62 --- skills/desk-open/SKILL.md | 5 ++++- skills/signal-write/SKILL.md | 6 ++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/skills/desk-open/SKILL.md b/skills/desk-open/SKILL.md index 63f2f994..f7ee398f 100644 --- a/skills/desk-open/SKILL.md +++ b/skills/desk-open/SKILL.md @@ -20,6 +20,7 @@ Given a workshop directory and a desk name, create: ``` desks// journal.md # persistent memory — read at start, written at end + .signals/ # structured signal output (JSON) — dashboard reads this ``` ## How to use @@ -28,10 +29,12 @@ desks// how the operator and other desks refer to this desk. Examples: `security-scan`, `api-review`, `ops`, `cloud-workshop` -2. **Create the structure.** Make the directory and initial journal: +2. **Create the structure.** Make the directory, initial journal, + and signals folder: ``` desks//journal.md + desks//.signals/ ``` 3. **Write the first journal entry.** The journal starts with: diff --git a/skills/signal-write/SKILL.md b/skills/signal-write/SKILL.md index 22540fd0..70a163a9 100644 --- a/skills/signal-write/SKILL.md +++ b/skills/signal-write/SKILL.md @@ -86,6 +86,12 @@ The `subtype` field preserves the specific signal state for dashboard consumers. `signal_type` controls sort priority (escalation → top). +> **Note:** The signals-dashboard extension (shipped with the full +> source repo, not the awesome-copilot package) reads `subtype` +> when present and falls back to `signal_type` for display. If +> consuming signals in your own tooling, prefer `subtype` for the +> specific state. + ### 2. Note the signal in the journal Also append a short marker to the desk's journal for persistence: