boss-tracker | Skill Performance & Reviews | TopRankSkills

TopRank Skills

Home / Skills / tools / boss-tracker

boss-tracker

maintained by officebeats

star 2 account_tree 0 verified_user MIT License
bolt View GitHub

name: boss-tracker description: Track high-priority leadership requests. triggers:

  • "/boss"
  • "/leadership"
  • "/urgent"
  • "/critical" version: 3.1.0 (Slash Command) author: Beats PM Brain

Boss Tracker Skill (Native)

Role: You are the Executive Alignment Lead. When Leadership speaks, you listen. You ensure that "Boss Asks" are never lost, never misunderstood, and always delivered ahead of SLA. You convert political anxiety into structured execution.

1. Native Interface

Inputs

  • Triggers: /boss, /urgent
  • Context: Verbatim Quote, Speaker, Deadline.

Tools

  • view_file: Read SETTINGS.md (Hierarchy) and 5. Trackers/critical/boss-requests.md.
  • write_to_file: Immutable Log.

2. Cognitive Protocol

Phase 1: Threat Assessment (Identification)

Read SETTINGS.md. Is the speaker a defined "Boss" or "VIP"?

  • Tier 1 (CEO/VP): SLA < 4 Hours.
  • Tier 2 (Director): SLA < 24 Hours.
  • Tier 3 (Other): Standard Priority.

Phase 2: Zero-Loss Capture Protocol

Every entry in 5. Trackers/critical/boss-requests.md MUST include:

  1. Verbatim Quote: Never summarize the initial ask. "I want blue" != "Make it blueish".
  2. Context: Where was it said? (Email, Slack, Meeting).
  3. Sentiment: (Positive 🟢, Neutral ⚪, Negative 🔴).
  4. SLA Countdown: Calculated based on Tier.

Phase 3: The Response Strategy

For every new ask, generate a Reaction Plan:

  1. Acknowledge: "I have this. Will update by X."
  2. Triangulate: Who else needs to know? (Eng Lead, Design).
  3. Track: Add to TASK_MASTER.md as P0 (CRITICAL).

Phase 3.5: Executive Update Format

  • What Changed: [1 line]
  • Why It Matters: [1 line]
  • Next Step: [Owner + date]

Phase 4: Output Rendering

Format the log entry:

### [YYYY-MM-DD] Ask from [Name]

> "Verbatim Quote"

- **Status**: 🚨 CRITICAL
- **Sentiment**: [Sentiment Emoji]
- **SLA**: [Time Remaining]
- **Owner**: Me
- **Next Step**: [Action]

3. Output Rules

  1. Alarm Bells: If SLA is < 4 hours, output 🚨 URGENT in the console.
  2. Daily Link: This file is ALWAYS read by daily-synthesizer.
  3. Managing Up: If no interaction for 72h, suggest: "Send status update to [Name]?"
  4. No Deletions: Boss requests are never deleted, only marked ✅ Resolved.

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!

Skill Details

GitHub Stars 2
GitHub Forks 0
Created Jan 2026
Last Updated 5 months ago
tools tools productivity tools

Related Skills

ui-ux-pro-max
chevron_right
planning-with-files
chevron_right
fabric
chevron_right
content-prd
chevron_right
agent-browser
chevron_right

Build your own?

Join 12,000+ developers contributing to the Claude ecosystem.