status

Aggregate multi-source work items into an auditable status snapshot.

Updated Aug 27, 2026

Search Tags:#dependencies #multi-source #diff #reconciliation #product-management #workstreams #status-tracking

Ready to run

npx skills add https://github.com/namankumar/product-os --skill status-namankumar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: status
Source: https://github.com/namankumar/product-os/tree/main/.claude/skills/status
Command: npx skills add https://github.com/namankumar/product-os --skill status-namankumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track the live status of every item across every workstream in a project. Scans Linear, Monday, Slack, Google Docs, Signal, and call notes to build an item-level status snapshot. Output is usable for leadership updates, keeping {{YOUR_NAME}} informed across parallel workstreams, spotting stalls and dependency risks before they bite.

Core Features & Use Cases

Scans and reconciles across multiple sources to produce a single status of work items.
Maintains per-item metadata (ID, Title, Owner, Status, Sources) and persists daily caches.
Supports dependency tracking, stale-item detection, and untracked commitments for escalation.

Quick Start

Use the status skill to generate today’s item-level status snapshot by aggregating data from Linear, Monday, Slack, and docs and writing it to the daily cache file.

Frequently Asked Questions about status

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

FAQPage Schema

How do I reconcile work items across Linear, Monday, and Slack into a single status snapshot?▼

Multi-source status reconciliation scans Linear, Monday, Slack, Google Docs, Signal, and meeting notes to aggregate item-level data into a single auditable status snapshot. It matches per-item metadata like ID, title, owner, and status to resolve discrepancies.

What is the best way to track dependencies and blockers across multiple parallel workstreams?▼

Tracking dependencies and blockers across parallel workstreams is handled by aggregating multi-source work items into a dated cache file. This snapshot flags dependency risks, stale items, and untracked commitments for escalation before they impact the project.

How does work item status tracking detect discrepancies from prior states?▼

Work item status tracking detects discrepancies by implementing a deterministic diff against the prior state. It compares the current multi-source aggregate with the previous daily cache file to identify status changes, stalls, and newly introduced blockers.

Can I generate leadership updates from unstructured meeting notes and chat signals?▼

Yes, generating leadership updates from unstructured meeting notes and chat signals is supported. The skill scans Signal messages and call notes alongside project management tools to produce a clean, auditable status snapshot for leadership consumption.

Does multi-source status tracking persist historical data for downstream consumption?▼

Multi-source status tracking persists historical data by writing a dated cache file for downstream consumption. This daily cache maintains per-item metadata, enabling deterministic diffs against prior states to track workstream health over time.

When do I need multi-source workstream reconciliation instead of checking individual project boards?▼

Multi-source workstream reconciliation is needed when work items span Linear, Monday, Slack, and documents simultaneously. Checking individual boards misses untracked commitments and dependency risks that only surface by aggregating items into a single auditable snapshot.