---
name: work-journal-weekly-for-slack
description: Create or refresh a bullets-only Slack summary from the comprehensive weekly vournal entry. Use for Slack-ready weekly updates; include Ships and Admin only, plus confirmed impact they support.
---

# Weekly work journal for Slack

Create a concise Slack-ready derivative of the comprehensive weekly journal. Completion means the file contains only eligible, source-supported bullets and matches the approved preview.

## Workflow

1. Resolve the supplied date to its containing Monday. Default to the week containing today in the Mac's local timezone, ask for a full date when only a month and day are given, and stop when the resolved Monday is in the future.
2. Use the Monday's year and full English month name for both paths:
   - Source: `/Users/skull/personal/vournal/YYYY/MonthLongName/Week_of_YYYY-MM-DD.md`
   - Output: `/Users/skull/personal/vournal/YYYY/MonthLongName/Week_of_YYYY-MM-DD_Slack.md`
3. If the source does not exist, invoke `work-journal-weekly` and complete its grouping and impact gates first. Resume this workflow only after the comprehensive file exists. The Slack file is never synthesized from daily entries.
4. Read the comprehensive file and any existing Slack file. Select eligible material, synthesize the full proposed output, and compare it with the current Slack file.
5. Show the exact proposed file as a preview. For an existing file, also show the meaningful replacement delta. Wait for approval.
6. Write the approved preview with a trailing newline. Report the path and bullet count. If there is no eligible content, do not create an empty file. If the regenerated content is unchanged, leave the file untouched.

## Eligibility filter

Use task content only from `### Ships` and `### Admin`, including their `####` workstreams. Calls, Reviews, and Personal content has no path into the Slack output.

An approved `## Impact` statement is eligible when at least one Ships or Admin task supports it. Integrate only the portion still supported after excluded task categories are removed. Keep impact next to its related work. Tasks without approved impact remain factual task bullets.

Apply the filter before synthesis. Do not create substitute summaries or hints for filtered work.

## Output contract

- The file contains only top-level Markdown list items beginning with `- `. It has no heading, date, label, divider, introduction, or signoff.
- Each bullet carries one concise idea. Merge overlapping work and routine detail when the result preserves every meaningful eligible task. There is no fixed bullet cap.
- Preserve concrete project, component, and proper-noun names chosen by the user. Match the journal's lowercase style elsewhere.
- State only source-supported work and approved effects.
- Convert every standard Markdown link `[text](URL)` to Slack mrkdwn `<URL|text>`. Keep readable PR labels such as `<https://github.com/vercel/front/pull/81861|#81861>` or `<https://github.com/owner/repo/pull/123|owner/repo#123>`.
- Remove markdown syntax that adds noise in Slack while keeping component and technical names readable.

## Hard boundaries

- The comprehensive weekly file is the sole source.
- Candidate or inferred impact is ineligible until approved in the comprehensive journal.
- The written file must equal the user-approved preview.
- Output stays under `/Users/skull/personal/vournal/YYYY/MonthLongName/`.