Pulse

Skill mshadmanrahman/pm-operating-system/_context/skills/pulse

An opinionated workflow system that restructures how product managers work with Claude Code. 16 PM skills, 9 agents, 10 coding rules, 13 slash commands, 6 automation hooks, product brain system, and session lifecycle with memory/handoffs.

Install

npx -y skills add mshadmanrahman/pm-operating-system --skill pulse

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Cross-project dashboard generator. Reads all living PPP documents in _product-brain/ and generates a unified view of what needs attention, what's active, and what's blocked. Triggers on: "pulse", "project pulse", "what needs my attention", "what's happening across projects", "/pulse", "give me the pulse".

SKILL.md

2.9 KB, as published. Nobody here has run it

Pulse Skill

Reads all project documents in _product-brain/ and generates a cross-project dashboard showing what needs attention right now.

When to Activate

User says "pulse", "project pulse", "what needs my attention"
User says "what's happening across projects"
User says "/pulse"
Start of day / start of week context gathering
Complements /meeting-prep (which preps for one meeting) and /weekly-status (which looks backward)

Execution

Step 1: Read All Project Docs

Glob: _product-brain/*.md (exclude PULSE.md)
Read each file

Step 2: Classify Each Project

For each project doc, determine:

Classification	Criteria
Needs Attention	Has Problems with no clear plan, overdue commitments, stale (not updated in 7+ days), or explicitly flagged escalations
Active	Updated recently, has Plans in motion, no critical blockers
On Hold	Status explicitly says "On Hold"
Complete	Status says "Complete"

Step 3: Generate PULSE.md

Rewrite _product-brain/PULSE.md with:

# Pulse

> Cross-project dashboard. Auto-generated by `/pulse`. Do not edit manually.

**Last generated:** {datetime}
**Projects tracked:** {count}

## Needs Attention

### {Project Name} - {Status}
- **Problem:** {most critical problem}
- **Since:** {last updated date}
- **Action needed:** {what you should do}

### ...

## Active

| Project | Status | Last Updated | Next Action |
|:--------|:-------|:-------------|:------------|
| {name} | {status} | {date} | {first item from Plans} |

## On Hold

| Project | Since | Reason |
|:--------|:------|:-------|
| {name} | {date} | {why on hold} |

## This Week's Changelog

{Aggregate changelog entries from all projects for the current week, sorted by date descending}

Step 4: Present

Show the Pulse output directly in conversation. Focus on:

What needs attention (if anything)
Quick status of all active projects
This week's cross-project changelog

Keep it scannable. No long paragraphs.

Relationship to Other Skills

/meeting-prep: Preps for one meeting. Pulse gives the full picture.
/weekly-status: Looks backward at accomplishments. Pulse looks at current state.
/post-meeting: Feeds data into project docs. Pulse reads from them.
/deep-context: Deep dive on one topic. Pulse is the surface scan across all.

Staleness Detection

If a project hasn't been updated in 7+ days but its status isn't "On Hold" or "Complete", flag it:

⚠️ {project} hasn't been updated since {date}. Still active? Consider running /post-meeting or updating manually.