Focus And Priority Management logo

Focus And Priority Management

Community
fatihguner
focus-and-priority-management

Delivers daily scheduling habits, meeting hygiene, attention management, and boundary-setting techniques for leaders whose calendars have become their strategy by default. Use when urgent tasks crowd out important ones, when meeting load exceeds productive work time, when a leader cannot recall their last hour of uninterrupted deep work, or when data presentations fail to land because preparation time was consumed by low-value obligations.

Overview

Publisherfatihguner
Repositoryforeman
Skill namefocus-and-priority-management
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Focus And Priority Management AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/focus-and-priority-management
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/focus-and-priority-management .claude/skills/focus-and-priority-management
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Focus And Priority Management in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Focus And Priority Management on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Focus And Priority Management is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Focus and Priority Management

Perform an autopsy on your calendar from last week. Categorise every entry into four buckets: meetings you led, meetings you attended, blocks of focused individual work, and everything else. Now calculate the percentages. If focused work occupies less than 20% of your week, you are not leading -- you are being led, by other people's agendas, by the tyranny of the next notification, and by the organisational fiction that presence in a room equals contribution to an outcome.

Michael Porter and Nitin Nohria's research on how CEOs manage time reveals a sobering truth: calendars are not neutral organisational tools. They are symbols. The tasks and people a leader shows up for communicate what matters more clearly than any strategy memo. An executive who spends 80% of the week in meetings and 3% on strategic thinking has, in effect, declared that reaction is the company's strategy.

The Eisenhower matrix -- urgent versus important -- provides the theoretical scaffolding for this problem (see eisenhower-matrix.md for the framework). This skill concerns itself with the mechanical, behavioural, and social dimensions of actually living by that distinction: how to schedule deep work, how to run meetings that earn the time they consume, how to say no without damaging relationships, and how to present data so the meetings you do attend produce decisions rather than more meetings.


The Practice

Scheduling Deep Work

Alice Boyes's research distils the scheduling challenge to a single principle: decide in advance when you will do important work, and then protect that time as though it were an unmovable meeting. The specific method matters less than the commitment.

Effective approaches include:

  • Morning fortress. Reserve the first 90 minutes of each day for strategic work. No email, no Slack, no meetings. The brain's prefrontal cortex is freshest in the morning for most people; squandering that window on inbox triage is a neurological misallocation.
  • One sacred day. Block an entire day per week -- typically Wednesday or Thursday -- for deep work. Communicate the block to the team so they do not interpret absence as unavailability.
  • Bite-size progress. When full blocks are impossible, break strategic projects into 20-minute tasks that can fit between meetings. Keep a running list of these micro-tasks so that a sudden 15-minute gap becomes an opportunity, not dead time.

Meeting Hygiene

Meetings are the largest single consumer of leadership time. Most of them underperform because they lack one or more of the following:

Clear decision-making process. Bob Frisch and Cary Greene's research shows that confusion about who decides and how produces tension. Before any meeting begins, state the ground rules: Will there be a vote? Does someone hold veto power? Is the meeting for input or for ratification? Ambiguity on these questions turns a 30-minute discussion into a 90-minute argument.

Question-based agendas. Steven Rogelberg recommends replacing topic-based agenda items with questions the group must answer. "Budget problems" becomes "How will we reduce spending by $100K this year?" Questions focus attention on outcomes, clarify who should be in the room, and signal when the meeting is done -- when the questions are answered.

Hybrid discipline. When presenting to both in-person and remote audiences, leaders reliably neglect the screen. Sarah Gershman and Rae Ringel advise alternating eye contact between the room and the camera, moving closer to the camera periodically, mixing in-person and remote participants in breakout groups, and keeping the presentation short. Virtual fatigue is real; every presentation feels longer through a screen.

The Art of Saying No

Elizabeth Grace Saunders identifies the core difficulty: saying no feels like a social transgression. The solution is scripted phrases practised until they feel natural.

  • Redirecting: "This might be a great growth opportunity for someone. I am happy to connect you with Kei, who is looking to develop in that area."
  • Capacity boundary: "Thanks, but I have to decline. My schedule is at capacity."
  • Temporal boundary: "I cannot take this on this quarter, but ask me again in Q3."

The key is specificity. Vague resistance ("I'm pretty busy") invites negotiation. A clear, named reason closes the loop gracefully.

Attention as Muscle

Daniel Goleman frames attention as the foundation of emotional, organisational, and strategic intelligence -- and argues that it can be strengthened through deliberate practice.

Three dimensions of attention matter for leaders:

  1. Self-focus -- Monitoring internal signals, maintaining self-control, and sustaining coherent self-awareness across time.
  2. Other-focus -- Reading people's perspectives, sensing what they need, and building relationships that function under pressure.
  3. World-focus -- Listening broadly, connecting disparate information, and imagining how today's decisions play out at longer time horizons.

The constant onslaught of incoming data -- email, messages, notifications, headlines -- attacks all three. Goleman's prescription is not willpower but structure: controlled environments, technology boundaries, and scheduled reflection time.

Productivity Versus Busyness

Adam Waytz's research on overwork cultures identifies a pernicious dynamic: organisations that reward visible effort over measurable output create employees who optimise for the appearance of work. Leaders dismantle this by rewarding output, promoting based on results, fostering deep work by eliminating low-value tasks, and modelling the behaviour themselves -- including visibly signing off when meaningful work is done.

Data That Lands

When a meeting requires data to drive a decision, presentation quality determines whether the data is heard or ignored.

Nancy Duarte recommends making numbers relatable through concrete analogies: a time span compared to a familiar flight, a size compared to a local landmark. Joel Schwartzberg adds precision: label chart elements exactly, avoid abbreviations, replace generic titles with takeaway titles ("Millennials Prefer Mobile" rather than "Millennial Preferences"), and highlight the aha zones with visual emphasis and verbal callouts.


Prompts

Prompt 1 -- Calendar Autopsy:

Here is a summary of how I spent my time last week: [describe or paste calendar entries]. Categorise each entry as (a) deep strategic work, (b) meeting I led, (c) meeting I attended, (d) reactive/administrative, (e) other. Calculate percentages. Identify the three lowest-value time blocks and recommend what to eliminate, delegate, or restructure. Propose a revised calendar template that increases deep work to at least 25% of the week.

Prompt 2 -- Meeting Redesign:

I run a recurring [frequency] team meeting that currently lasts [duration] and covers [topics]. Attendance is [number] people. Redesign it using question-based agendas, explicit decision-making rules, and a hybrid-friendly format. Include a template agenda, ground rules, and guidance on reducing the meeting by at least 25%.

Prompt 3 -- Strategic No:

I have been asked to [describe the request]. My current priorities are [list top 3 priorities]. Draft three versions of a polite, clear decline: one for a peer, one for a senior leader, and one for a direct report. Each should redirect the request constructively without ambiguity.

Prompt 4 -- Data Presentation Overhaul:

I have the following data to present: [describe data, audience, and context]. Restructure the presentation so that: (a) each slide has a takeaway title, (b) key numbers are contextualised with concrete analogies, (c) aha zones are highlighted visually, and (d) the total presentation is under [target duration]. Draft the slide-by-slide outline.


Use Cases

Early-traction founder drowning in meetings

A founder of a 20-person startup spends 35 of 45 working hours per week in meetings. A calendar autopsy reveals that 40% of those meetings are status updates that could be replaced by asynchronous Slack summaries, and another 20% are one-on-ones that lack structure and routinely run over. The intervention: status meetings become written updates; one-on-ones are capped at 25 minutes with a standing agenda; and two mornings per week are declared meeting-free. Within a month, the founder reports having time to think about strategy for the first time in six months.

Growth-stage VP who cannot say no

A vice president at a 200-person company has accepted every cross-functional committee invitation, every mentorship request, and every "quick coffee" for two years. Her direct reports are underperforming because she has no time to coach them. With practised scripts, she declines three recurring committee roles (redirecting to capable direct reports), consolidates mentorship into a monthly group session, and reclaims seven hours per week. Her team's quarterly metrics improve within one cycle.

Scale-stage leader whose data presentations fail

A director presents quarterly business reviews to the executive team, but decisions are consistently deferred. Analysis reveals the problem: slides are dense with data, titles are generic, and no visual hierarchy guides the eye to the key findings. A redesign using takeaway titles, contextual analogies, and highlighted aha zones transforms a 45-minute data dump into a 20-minute decision-ready briefing.


Anti-Patterns

1. Protecting deep-work time but filling it with low-value work. Blocking two hours for "strategic thinking" and then spending it reorganising a spreadsheet is a scheduling victory and a priority defeat. Deep-work blocks require advance clarity on what will be accomplished.

2. Saying no to everything. The overcorrection from chronic overcommitment is hermit-like isolation. Leaders who decline every request erode social capital and lose access to information. The goal is selective engagement, not withdrawal.

3. Optimising meetings without questioning their existence. Making a meeting 20% shorter is useful; asking whether the meeting should exist at all is transformative. The best meeting hygiene is the meeting that never happens because its purpose is served by a written summary.

4. Treating busyness as a personal failing rather than a systemic one. Individual time-management techniques cannot overcome an organisational culture that rewards visible effort over output. If the system incentivises busyness, fixing the individual is treating the symptom.

5. Buying back time without investing it. Outsourcing chores, hiring an assistant, or automating routine tasks creates capacity. If that capacity is immediately consumed by more meetings and more email, the investment yields no return. Freed time must be deliberately allocated to high-value work.


By Stage

StageFocusKey Difference
ValidationFounder's personal time allocationEvery hour has outsized impact; discipline here compounds dramatically
Early TractionMeeting culture, first scheduling normsThe habits set in a 15-person company become the culture of a 150-person company
GrowthCalendar delegation, manager enablementLeaders must teach others to manage their own focus, not just manage their own
ScaleOrganisational time architecture, meeting auditsTime management becomes a systems problem requiring policy-level intervention

At validation, the founder's calendar is the company's strategy. A founder who spends 80% of the week on sales has a sales-driven company. A founder who spends 80% on product has a product-driven company. Whether either is correct depends on context, but the allocation should be deliberate, not accidental.

At scale, individual time-management skills are necessary but insufficient. The organisation needs institutional interventions: meeting-free days across the company, default 25-minute meeting slots, mandatory agenda requirements, and quarterly meeting audits that identify and eliminate recurring meetings whose purpose has expired.


Output Template

markdown
# Calendar Audit Report -- [Name / Team]

**Period:** [Week of Date]
**Total working hours:** [N]

## Time Allocation

| Category | Hours | Percentage | Assessment |
|----------|-------|------------|------------|
| Deep strategic work | [N] | [%] | [Target: >25%] |
| Meetings led | [N] | [%] | [Note] |
| Meetings attended | [N] | [%] | [Note] |
| Reactive/administrative | [N] | [%] | [Target: <20%] |
| Other | [N] | [%] | [Note] |

## Three Lowest-Value Time Blocks
1. [Description] -- [Recommendation: eliminate / delegate / restructure]
2. [Description] -- [Recommendation]
3. [Description] -- [Recommendation]

## Proposed Weekly Template

| Time | Mon | Tue | Wed | Thu | Fri |
|------|-----|-----|-----|-----|-----|
| 8-10 | [Block type] | | | | |
| 10-12 | | | | | |
| 12-1 | | | | | |
| 1-3 | | | | | |
| 3-5 | | | | | |

## Meeting Hygiene Checklist
- [ ] Every recurring meeting has a question-based agenda
- [ ] Decision-making process stated at the start of each meeting
- [ ] Default meeting duration is 25 minutes, not 30 or 60
- [ ] At least two meeting-free blocks per week protected
- [ ] Quarterly meeting audit scheduled

## Commitments to Decline
- [Commitment] -- [Redirect plan]
- [Commitment] -- [Redirect plan]

Related Skills

  • Eisenhower Matrix -- The theoretical framework for urgent-versus-important prioritisation; this skill provides the daily execution layer.
  • Flow State -- Deep work is the scheduling precondition for flow; without protected time, flow states cannot occur.
  • Covey's Seven Habits -- "Put first things first" is the Covey habit most directly addressed by calendar audits and meeting hygiene.
  • Leader Resilience and Wellbeing -- Poor time management is a primary driver of leader burnout; protecting focus protects health.
  • Delegation and Empowerment -- Reclaiming calendar time requires delegating tasks that do not need the leader's personal involvement; the delegation audit directly feeds the calendar autopsy.
  • Stoic Control and Clarity -- The Stoic dichotomy of control provides the philosophical discipline for releasing low-value commitments that consume focus without advancing priorities.

Frequently asked questions

What does the Focus And Priority Management AI skill do?

Delivers daily scheduling habits, meeting hygiene, attention management, and boundary-setting techniques for leaders whose calendars have become their strategy by default. Use when urgent tasks crowd out important ones, when meeting load exceeds productive work time, when a leader cannot recall their last hour of uninterrupted deep work, or when data presentations fail to land because preparation time was consumed by low-value obligations.

Why use Focus And Priority Management on TypingMind?

Because you install it once and use it with any model. Focus And Priority Management is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Focus And Priority Management in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/focus-and-priority-management. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Focus And Priority Management?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Focus And Priority Management?

As many as you like. As long as a model supports skills, you can use Focus And Priority Management with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Focus And Priority Management AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇