pulse-projects

name	pulse-projects
description	Use when the user mentions a customer, deal, engagement, initiative, or stakeholder by name; describes a meeting/email/conversation that affects a known engagement; or asks about commitments, status, or who-said-what for named work.

Pulse Projects

Persistent project memory: one YAML file per customer engagement, stored in OneDrive. The schema, the file location, and the rules for what's worth tracking.

Path

<PULSE_HOME> is the Pulse folder under the user's OneDrive Documents/. Resolve once at start, picking the first existing path for the user's OS:

Windows (PowerShell):

if ($env:OneDriveCommercial) { "$env:OneDriveCommercial\Documents\Pulse" } elseif ($env:OneDrive) { "$env:OneDrive\Documents\Pulse" } else { "$env:USERPROFILE\Documents\Pulse" }

macOS (zsh/bash):

# Modern (macOS 12.3+): OneDrive for Business under Library/CloudStorage
ls -d "$HOME/Library/CloudStorage/OneDrive-"*/Documents 2>/dev/null | head -1
# Older convention
ls -d "$HOME/OneDrive - "*/Documents 2>/dev/null | head -1
# Personal OneDrive
[ -d "$HOME/OneDrive/Documents" ] && echo "$HOME/OneDrive/Documents"
# Last resort
echo "$HOME/Documents"

Take the first non-empty result, append /Pulse.

Linux: $HOME/OneDrive/Documents/Pulse if it exists, else $HOME/Documents/Pulse.

If none exists, create under the last-resort path. Path examples in this skill use Windows-style \ — on macOS/Linux, use / instead.

Files live at <PULSE_HOME>\projects\<slug>.yaml. Slug is lowercase-hyphenated. One file per customer — workshops, reviews, sub-meetings are timeline entries, never separate files.

Schema

project: "Human-readable name"          # required
involvement: lead                        # lead | contributor | observer (default: observer)
status: active                           # active | blocked | on-hold | completed
risk_level: medium                       # low | medium | high | critical
summary: "1–2 sentences current state"
last_verified: "2026-05-05"
stakeholders:                            # max 6
  - {name, role, org?, last_interaction?}
commitments:
  - what: "Send pricing proposal"
    who: "You" | "<name>"
    to: "<recipient>"
    due: "2026-05-12"                    # YYYY-MM-DD, ONLY if explicitly stated
    due_confidence: explicit             # explicit | inferred
    status: open                         # open | done | overdue | cancelled
    source: "<artifact reference>"
timeline:                                # max 10 entries
  - {date, event, }
                       
   {, , }
                            
                               
                           
     
     
 [, ]    
 [, ]               
              

Discovery — when to create a NEW project

ALL THREE conditions must be met:

1. 3+ mentions of the customer/initiative across user data
2. 2+ different source types (transcript + email — not two emails from the same thread)
3. At least one actionable element — commitment, deliverable, meeting series, deadline, or explicit ask directed at the user

Passive mentions and CC'd emails do NOT meet the threshold.

Before creating, search existing slugs. If a file already exists, update it. Default involvement: observer unless the user clearly owns it.

Team context broadcast — automatic on key events

Teammates running their own Pulse may have relevant context on the same customer. On qualifying events, fan out a query to every reachable teammate and let their Pulses respond asynchronously. Their answers populate team_context on this project YAML — /pulse-collaboration ingests responses (which can arrive minutes or hours later).

When to broadcast:

• Always on new project creation (discovery threshold met for a customer not yet tracked)
• On major updates: status escalation to blocked, risk_level raised to high/critical, project moves from on-hold back to active
• 7-day cooldown per project — don't re-broadcast on minor changes (timeline entries, refresh, stakeholder pruning)

How:

1. Run discovery via the /pulse-collaboration skill's discovery step → get [{handle, inbox_path}].

2. For each reachable teammate, write an agent_request YAML to their inbox_path:

   type: agent_request
   request_id: "<fresh uuid>"
   project_id: "<this project's slug>"
   from_handle: "<your handle>"
   task: |
     New engagement: <Customer> / <Initiative>.
     Have you had activity on this in the LAST 30 DAYS? Looking for: ongoing meetings,
     commitments, key contacts, anything pertinent right now.
     Context (1 line): <summary>
   created_at: "<ISO>"
   

   Filename: YYYY-MM-DD-request-<your-handle>-<first8charsOfUUID>.yaml.

3. Seed a team_context entry per teammate in the project YAML:

   team_context:
     - from: <handle>
       relevance: pending
       summary: "Asked <today>, no response yet."
       last_updated: "<today>"
   

4. Continue creating/updating the project. Don't block waiting for replies.

If no teammates are reachable (no shared folders), skip silently — leave team_context empty.

Read-before-write

Always: list directory → read existing file → merge new info → apply curation limits → set updated_at → write the full file. Never overwrite blindly.

Curation limits (HARD)

Stakeholders ≤6 · Timeline ≤10 · Tags ≤4 · Watch queries ≤3 · Artifacts ≤6 · team_context ≤5 · Summary ≤2 sentences. When exceeded, prune oldest low-value entries first — never the newest.

Commitment lifecycle

open + due past today + due_confidence: explicit → overdue. Inferred dates never trigger overdue (false alarms erode trust). overdue >5 days unresolved → cancelled with cancelled_reason. Mark done with completion source when fulfilled.

Auto-archive observer projects

involvement: observer + status: active + no activity in 14+ days → set status: completed with timeline entry [AUTO-ARCHIVED] No activity in 14+ days and involvement is observer. Observer projects must prove they're worth tracking.

Never

• Invent dates, names, amounts, or commitments — only persist what's explicit in source
• Create a second file for the same customer
• Mark lead from a single email or meeting attendance
• Treat inferred due dates as overdue
• Delete history when uncertain — add a [STALE] or [INFO] timeline entry instead
• Broadcast on minor updates — that spams teammates