workstream-map

Consolidate Slack DMs, GitHub PRs, and git worktrees into a prioritized Markdown map.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/arnavsurve/dotfiles --skill workstream-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workstream-map
Source: https://github.com/arnavsurve/dotfiles/tree/main/agents/skills/workstream-map
Command: npx skills add https://github.com/arnavsurve/dotfiles --skill workstream-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams turn scattered updates from Slack DMs and project channels, open GitHub PRs, and local git worktrees into a single, prioritized workstream map, reducing context switching and missed commitments.

Core Features & Use Cases

  • Consolidation: Correlates conversations, project status, and code activity to surface active workstreams and blockers.
  • Stakeholder Visibility: Identifies who cares about each item and what actions are needed.
  • Output & Scheduling: Generates a timestamped Markdown file saved to the Desktop for archival and sharing.

Quick Start

Generate a timestamped workstream map by aggregating Slack conversations, GitHub PRs, and local git worktrees, and save the result to the Desktop.

Frequently Asked Questions about workstream-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate Slack messages, GitHub PRs, and git worktrees into a single project map?

To consolidate Slack messages, GitHub PRs, and git worktrees into a single project map, this Skill analyzes Slack conversations, open pull requests, and local worktree statuses to classify and surface ongoing work streams, blockers, and stakeholders.

Can I automatically identify project blockers and commitments from Slack DMs and GitHub PRs?

Yes, you can identify project blockers and commitments from Slack DMs and GitHub PRs by analyzing Slack API conversations_history and gh pr list outputs, correlating leadership messages and code activity to surface actionable items and stakeholders.

What is the best way to track active workstreams across Slack channels and local git worktrees?

The best way to track active workstreams across Slack and local git worktrees is to analyze channels_list and worktree status checks, correlating recent messages and code branches to generate a prioritized map of ongoing tasks and commitments.

Does this workstream mapping tool require specific Slack API or GitHub CLI setup?

Yes, workstream mapping requires Slack API access for users_search, channels_list, and conversations_history calls, alongside the GitHub CLI (gh pr list) and local git worktree capabilities to aggregate and classify project data.

How do I generate a timestamped Markdown summary of my open pull requests and Slack conversations?

To generate a timestamped Markdown summary of open pull requests and Slack conversations, the Skill aggregates GitHub PR listings and Slack message history, outputting a prioritized workstream map saved directly to your Desktop.

Why are my scattered Slack updates and git worktrees not reflecting my actual project priorities?

Scattered Slack updates and git worktrees fail to reflect project priorities because they lack correlation; this Skill resolves the issue by consolidating conversations, PR statuses, and worktree classifications into a single prioritized map.