managing-urgency

Guide engineering managers through a five-question evaluation of urgent deadlines.

104|7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/manager-dot-dev/manager-skills --skill managing-urgency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-urgency
Source: https://github.com/manager-dot-dev/manager-skills/tree/main/skills/managing-urgency
Command: npx skills add https://github.com/manager-dot-dev/manager-skills --skill managing-urgency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps engineering managers respond to high-urgency requests and use deadlines effectively — produces a five-question framework for evaluating unreasonable deadlines, guidance on scope/staffing/intensity decisions under pressure, Parkinson's Law applied to engineering, and five common deadline mistakes to avoid. Use when the user says "urgent deadline," "everything is on fire," "we need to ship fast," "fake deadline," "unreasonable timeline," "crisis mode," "working weekends," "Parkinson's Law," or "leadership is pushing for faster delivery."

Core Features & Use Cases

  • Five-question evaluation framework to determine if a deadline is real, fake, or a panic-driven constraint.
  • Guidance on scope, staffing, and intensity decisions under pressure to balance speed and quality.
  • Application of Parkinson's Law to engineering work to improve focus and avoid unnecessary work expansion.
  • Clear avoidance guidance for the five most common deadline mistakes to prevent burnout and quality degradation.
  • Use cases include crisis-mode responses, prioritization during crunch periods, and stakeholder negotiation scenarios.

Quick Start

Describe the urgent deadline you face, and I will apply the five-question framework to guide your response.

Frequently Asked Questions about managing-urgency

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

FAQPage Schema
How do I evaluate if an urgent engineering deadline is real or fake?

Evaluate urgent deadlines using a five-question framework to determine if the timeline is a real constraint, a fake deadline, or a panic-driven response. This identifies whether the urgency is justified or artificially imposed.

What is the best way to manage scope and staffing decisions during an engineering crisis?

Manage scope and staffing during a crisis by applying structured tradeoff guidance to balance speed and quality. This framework helps engineering managers adjust workload intensity and resources under pressure without degrading output.

How does Parkinson's Law apply to software engineering deadlines?

Parkinson's Law applies to software engineering by explaining how work expands to fill available time, leading to unnecessary scope creep. Applying this principle helps managers improve team focus and avoid artificial work expansion during crunch periods.

What are the most common deadline mistakes engineering managers should avoid?

Common deadline mistakes include failing to negotiate scope, ignoring staffing constraints, and succumbing to panic-driven timelines. Avoiding these five specific errors prevents team burnout and protects engineering quality under pressure.

How do I handle leadership pushing for faster delivery on unreasonable timelines?

Handle leadership pushing for faster delivery by using the five-question evaluation framework to clarify tradeoffs. This provides structured guidance for stakeholder negotiation scenarios, ensuring clear communication of risks and scope adjustments.

When should I adjust workload intensity to meet an urgent engineering deadline?

Adjust workload intensity when the five-question framework confirms a real deadline requires immediate action. Use the provided tradeoff guidance to balance necessary speed with sustainable team performance during crunch periods.