agentsclimarketplace

Time energy management

Skill Dragoon0x/product-skills/skills/organisation-prioritization/time-energy-management

The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.

Install
npx -y skills add Dragoon0x/product-skills --skill time-energy-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Manage PM time and energy across competing demands without burning out or dropping critical work. Covers prioritization of PM activities, calendar discipline, and sustainable pace. Use when overwhelmed by meetings, losing time to reactive work, or when important strategic work keeps getting pushed.

SKILL.md

2.9 KB, 555 tokens by cl100k_base, as published. Nobody here has run it

Time & Energy Management

Protect your time so you can do the work that actually matters.

How to use

  • /time-energy-management Apply time management constraints to this conversation.
  • /time-energy-management <situation> Optimize time allocation for the described PM workload.

Constraints

Activity Prioritization

PMs do four types of work. MUST allocate time intentionally:

  • Strategic work (roadmap, research, analysis): high impact, easily crowded out. Protect this.
  • Execution work (sprint support, blocker removal, decisions): urgent, necessary, but shouldn't dominate.
  • Communication work (updates, alignment, stakeholder management): important but expandable. Timebox it.
  • Reactive work (fire drills, escalations, ad hoc requests): unavoidable but must be contained.
  • SHOULD aim for 30%+ on strategic work. If it's under 10%, you're a project manager, not a product manager.

Calendar Discipline

  • MUST block focus time for strategic and deep work. If it's not on the calendar, it won't happen.
  • SHOULD batch meetings into specific days or time blocks
  • MUST decline meetings that don't have a clear agenda or your required input
  • SHOULD audit your calendar weekly: which meetings were actually valuable?
  • NEVER fill every available slot. Buffer time between meetings prevents burnout and allows processing.

Delegation and Saying No

  • MUST identify work that only the PM can do vs. work others can own
  • SHOULD delegate decisions that don't require PM judgment
  • MUST say no to requests that don't connect to current priorities — with explanation
  • SHOULD have a default answer of "not now" rather than "yes" for new requests
  • NEVER take on work to be helpful when it means dropping something more important

Sustainable Pace

  • MUST recognize that sustained overwork degrades decision quality — the most important PM tool
  • SHOULD set boundaries on after-hours work and model this for the team
  • MUST take breaks and recovery time. Burnout doesn't arrive suddenly — it accumulates.
  • SHOULD distinguish between crunch periods (acceptable if rare) and chronic overwork (unsustainable)
  • NEVER wear busyness as a badge of honor. Being busy and being effective are different things.

Anti-Patterns

  • The Always-Available PM: in every meeting, answering every Slack, never doing deep work
  • Calendar Tetris: filling every 30-minute gap with another meeting
  • Strategic Work "Tomorrow": always planning to do the important stuff next week
  • The Hero Complex: doing everything yourself because "it's faster"
  • Reactive-Only Mode: spending all day on fire drills and never getting ahead of problems

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.