pulselisted

# Pulse ## Core Rule Report what shipped, broke, was learned, and is open in a fixed time window. Surface signals, not opinions. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/pulse` when: - End of a week/sprint and you want a one-page outcome view - Preparing a stakeholder update (Slack, email, demo prep) - Reviewing the project after a period away - Setting up a scheduled outcome timeline (`/loop weekly /pulse mode:headless`) Not for: - Reflective retrospective on *how* the work went — use `/retro` - Whole-project health scoring — use `/project-health-report` - Pre-merge multi-audit review — use `/review-pipeline` ## Scope Rules - Operates over a time window (default: last 7 days) - Read-only: produces a report and saves it to `tasks/pulses/` - Pulls signals only from artifacts already in the repo (git history, `tasks/`, CHANGELOG, deps lockfile) — no external services required - Never modifies code or existing lessons/decisions ## Process ### Phase 1: Resolve Window Determine the time range: 1. **If `window:Nd` or `window:Nw` in arguments** — use it (e.g., `window:7d`, `window:30d`, `window:2w`) 2. **Else if `sin