managing-urgency

Evaluate high-urgency engineering deadlines using a five-question framework.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill managing-urgency-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-urgency
Source: https://github.com/imsus/cto/tree/main/.agents/skills/managing-urgency
Command: npx skills add https://github.com/imsus/cto --skill managing-urgency-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps engineering managers respond to high-urgency pressure by distinguishing unreasonable deadlines from necessary ones and preventing burnout, scope creep, and quality failures during crunch.

Core Features & Use Cases

  • Five-question deadline triage: Quickly assess whether the deadline is real vs fake, what team capacity is needed, how hard to ask people to work, whether the team is on the right path, and what “return to normal” must look like.
  • Tradeoff-driven action menu: Choose among reducing scope, adding capacity, accepting risk, moving the date, or stopping other work—rather than reflexively pushing back or overworking the team.
  • Parkinson’s Law for proactive focus: Use deadlines strategically to drive prioritization in healthy environments while recognizing how toxic environments lead to shortcuts and fear.
  • Five common deadline mistakes to avoid: Prevent failure modes like not telling the team what happens next, skipping team scoping, asking for too much effort without support, or being rigid when scope/date changes.

Quick Start

Use this skill when someone says the team is under an urgent deadline and you need a concrete way to evaluate it and respond with clear stakeholder tradeoffs.

Frequently Asked Questions about managing-urgency

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

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

To evaluate urgent engineering deadlines, use a five-question triage framework that distinguishes fake urgency from necessary crisis mode delivery, assessing team capacity, required intensity, and return-to-normal conditions to prevent burnout.

What is the best way to handle stakeholder communication during a crisis mode deadline?

Handling stakeholder communication during crisis mode deadlines requires presenting clear scope tradeoffs using a tradeoff-driven action menu, choosing among reducing scope, adding capacity, accepting risk, moving the date, or stopping other work.

How do I manage scope tradeoffs and staffing decisions under high-urgency pressure?

Managing scope tradeoffs and staffing under high-urgency pressure involves applying a structured framework to determine whether to reduce project scope, add team capacity, or move the deadline rather than reflexively overworking the engineering team.

What are common engineering deadline mistakes that lead to team burnout?

Common engineering deadline mistakes causing burnout include skipping team scoping, demanding excessive effort without support, failing to communicate next steps, and remaining rigid when scope or date changes, all of which force toxic shortcuts under pressure.

When should I use Parkinson's Law to drive engineering prioritization?

Apply Parkinson's Law to drive prioritization in healthy engineering environments by using deadlines strategically to maintain focus, while recognizing that toxic environments instead breed fear, shortcuts, and quality failures during crunch.