daily-workstream-update

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# Daily Workstream Update Skill

Runs the `/daily-workstream-update` workflow for the Obsidian vault at
`/home/gbencke/git.work/331.obsidian-scripts`.

Today's date (or the argument provided) is the target date `D`.
If no argument is given, use today.

Helper script for all mechanical operations:

```bash
python3 05.Scripts/daily_workstream_update.py <subcommand> [--date D]
```

Available subcommands: `today`, `meetings`, `workstreams`, `hierarchies-path`,
`daily-summary-path`, `daily-note-path`, `workstream-file <name>`,
`list-workstream-files`, `verify`, `move-daily-summary`,
`git-publish "<msg>"`.

Run `python3 05.Scripts/daily_workstream_update.py -h` to recheck at any time.

Use the script for every date / path / file-listing / verification / git
operation. Do not hand-roll those.

---

## Step A — Generate today's workstream summary

1. Resolve the date:
   ```bash
   python3 05.Scripts/daily_workstream_update.py today [--date D]
   ```
2. List today's meeting summaries:
   ```bash
   python3 05.Scripts/daily_workstream_update.py meetings --date D
   ```
   If the list is empty, stop and tell the user there are no meetings for `D`.
3. Read the workstream reference:
   ```bash
   python3 05.Scripts/daily_workstream_update.py workstreams
   ```
   This is `00.Tasks/Workstreams.SubTasks.Hierarchies.md`.
4. Read the most recent existing file in `00.Tasks/Daily.Summary/` (sorted by
   date) — this is the **formatting model**. Match its frontmatter, heading
   hierarchy, source-meeting wikilinks, "What was discussed" / "Action Items"
   sections, and `---` separators exactly.
5. Read each meeting summary file from step 2 in full.
6. Write `<repo-root>/<D>.WorkstreamUpdates.Summary.md` (at the repo root, not
   yet in `00.Tasks/Daily.Summary/`). Include a `## <Workstream Name>` section
   **only** for workstreams from the hierarchies reference that were actually
   discussed in today's meetings. Use the exact workstream names from the
   hierarchies file as the `## ` headings — never an older name or a workstream
   file's alias (e.g. `## SchedulerIQ - Scope.Open.Beta`, not
   `## SchedulerIQ - Open Beta`). Write **one** section per workstream: if
   content fits two headings that are the same workstream, merge it into one.
   Content that fits no workstream row (one-off intake or refinement items)
   goes under the closest workstream, not under a new ad-hoc heading.
7. Move the file into place:
   ```bash
   python3 05.Scripts/daily_workstream_update.py move-daily-summary --date D
   ```

---

## Step B — Verify workstream files contain today's entry, then publish

1. Run:
   ```bash
   python3 05.Scripts/daily_workstream_update.py verify --date D
   ```
2. For every `MISSING` line: open the workstream file shown and add a new
   `### <D-dashed>` section directly under the `#workstream/...` tag line (as
   the newest entry). Use the same per-day structure already in that file:
   `##### Meetings` block with summary + source links, body bullets grouped by
   topic, `##### Action Items`. Pull content from the corresponding
   `## <Workstream>` section in the daily summary produced in Step A. End the
   new section with a `---` separator before the previously-newest section.
3. For every `RENAME` line: the heading resolves (via an alias) but is not the
   hierarchies name. Rename the `## ` heading in the daily summary to the name
   shown. If that creates two sections with the same heading, merge them:
   combine the `> Source meetings:` lines (dedupe), the "What was discussed"
   bodies, and the action items.
4. For every `UNKNOWN` line: no workstream file matches that heading.
   - If the heading is a row in the hierarchies file, create the missing file
     as `00.Tasks/WorkStreams/<Product>/<Workstream Name>.md` (exact row name)
     with frontmatter `category: workstream`, `description`, `creation`,
     `last updated`, `product`, `status: open`, then a
     `#workstream/<product>/<workstream-slug>` tag line. Re-run `verify`; it
     now reports `MISSING`, which step 2 fills.
   - Otherwise it is an ad-hoc heading: move its content under the closest
     hierarchies workstream (step A.6). Only if nothing fits, print a short
     note for the user.
5. Re-run `verify` until it exits clean (only `OK` lines and any genuinely
   unresolvable `UNKNOWN` cases).
6. Publish:
   ```bash
   python3 05.Scripts/daily_workstream_update.py git-publish "Daily workstream summary <D-dashed>"
   ```

---

## Step C — Copy daily-note workstream entries into workstream files

1. Get today's daily note path:
   ```bash
   python3 05.Scripts/daily_workstream_update.py daily-note-path --date D
   ```
2. **Re-read** that file from disk now — the user may have updated it since
   this run started. Do not rely on cached content.
3. The daily note is organised as `### <Section Name>` blocks. For each section:
   - Map the section name to a workstream from the hierarchies reference (names
     are usually close but not identical — e.g. `### NewGen Performance` →
     `NewGen - Performance.Improvements`). Skip and note any section with no
     clear workstream mapping.
   - Resolve the workstream file:
     ```bash
     python3 05.Scripts/daily_workstream_update.py workstream-file "<workstream name>"
     ```
   - In that workstream file, locate today's `### <D-dashed>` section (created

From gbencke/dotfiles, MIT.

More from gbencke/dotfiles