| name | workstream-update |
| description | Propose 3–5 non-overlapping agent workstreams from the AIO Linear board. Use before starting parallel agent batches, when planning a factory work session, or when the user asks for a workstream update / batch plan. Triggers on "workstream update", "batch agents", "parallel workstreams", "/workstream-update". |
| version | 1.0.0 |
| access | team |
| triggers | ["workstream update","batch agents","parallel workstreams","/workstream-update"] |
Workstream update
Produces a workstream update document: 3–5 agent prompts from the current AIO Linear board, aligned with the Linear factory rule.
Run
WS="dotenvx run --quiet -f .env -- node .claude/skills/workstream-update/workstream-update.mjs"
$WS
$WS --json
Requires LINEAR_API_KEY and the aios-linear skill's linear.mjs on the path above.
What it does
- Lists AIO-team issues via
linear.mjs list AIO
- Prioritizes In Progress → Triage → Backlog
- Emits up to 5 workstream prompts (minimum 3 when enough candidates exist)
- Each prompt references the AIO ID, spec-eval gate, PR title convention, and closeout checklist
Operator workflow
- Run
$WS and review proposed workstreams
- Manually de-conflict if two issues touch the same code surface (script does not read file paths yet)
- Paste each prompt into a separate harness (Codex, Claude Code, Cursor, etc.)
- After batch:
aios time capture
When to use
- Starting a parallel agent session
- Sunday/weekly batch planning
- After triage intake moved issues to Backlog
Limitations (v1)
- Does not call an LLM for code-area deconfliction — operator reviews overlap
- AIO team only (not client-engagement boards)
- Does not auto-start agents