workstream
Read the workstream for the current herdr space (the user's linked PRs, Linear issues, Slack threads and brief) with the `ws` CLI. Use when working inside a herdr pane and you need to know which PRs, issues or Slack threads belong to the current work, when the user mentions "the workstream", "my PRs for this", or the home page, or when you open, finish or find a PR, Linear issue or Slack thread that belongs to this work and should be linked.
Source facts
- Repository
- joshdholtz/herdr-setup
- Last source activity
- October 15, 2026 at 15:02
- Detected SKILL.md language
- English
- Stars
- 0
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- workstream
- description
- Read the workstream for the current herdr space (the user's linked PRs, Linear issues, Slack threads and brief) with the `ws` CLI. Use when working inside a herdr pane and you need to know which PRs, issues or Slack threads belong to the current work, when the user mentions "the workstream", "my PRs for this", or the home page, or when you open, finish or find a PR, Linear issue or Slack thread that belongs to this work and should be linked.
# Workstream (`ws`)
The user organizes work in herdr: **one herdr space = one workstream** (for example "Checkout redesign"). Each space has a `home` tab, a home page listing everything the user linked to that workstream: their PRs across repos (with live CI and review status), Linear issues and projects, and Slack channels and threads, plus a short brief describing the work.
`ws` is the command-line tool behind that page (source: github.com/joshdholtz/herdr-setup). Inside a herdr pane it knows the space from `HERDR_WORKSPACE_ID`; no arguments needed.
## When you start in a herdr space
If a "# Workstream: …" block is already in your context (a SessionStart hook adds it), you have the current list. Otherwise run:
```bash
ws context
```
It prints markdown: the brief, each PR with state, CI, review, and a `NEEDS YOU:` note when something needs the user, then Linear and Slack with links. Run it again whenever you need fresh status (it fetches live PR status from GitHub). `ws context --json` gives the raw links.
`ws context` only works inside a herdr pane (`HERDR_WORKSPACE_ID` set). Outside herdr it exits 1 with "not inside a herdr pane"; in a space without a workstream it exits 1 with "this herdr space has no workstream yet". Both are normal; carry on without it. If `ws` is not found, tell the user `~/.local/bin` is not on their PATH.
## Using it
- Treat the listed items as the scope of the work. Read the linked Slack threads and Linear issues (with your Slack and Linear tools) for decisions and context before changing related code.
- Items are links, not copies: GitHub, Linear and Slack are the source of truth.
- Unreviewed suggestions are not part of the workstream; ignore them unless the user asks.
## Linking something new
When you open a PR for this work, or find an issue or thread that clearly belongs, link it:
```bash
ws add <url>
```
It accepts GitHub PR links, Linear issue or project links, Slack channel or thread links, `#channel-name`, and Linear IDs like `ABC-123` (prefer full URLs: a bare ID only becomes a link when `linear_workspace` is set). Tell the user what you linked. Only link things that clearly belong; when unsure, ask instead.
Never run `ws rm`, `ws find`, `ws home` or `ws open` unless the user asks: removing changes their list, finding costs usage, and the home page is an interactive screen in its own tab.
View on GitHub