TypingMindTypingMindThe best frontend for AI
Priority Planner logo

Priority Planner

Organization
techwolf-ai
priority-planner

Helps managers cut through noise and identify their highest-leverage actions for the day or week. Aggregates signals from calendar, triage, team context, and OKRs/goals. Presents a suggested focus list grouped by urgency, importance, and investment. The manager reviews and adjusts. Supports effective execution and prioritisation.

Overview

Publishertechwolf-ai
Repositoryai-first-toolkit
Skill namepriority-planner
Stars
138
Forks
7
Bundled files
2
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by techwolf-ai on GitHub. Read the source before you install it.

Installation

Install the Priority Planner 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/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/priority-planner
  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/techwolf-ai/ai-first-toolkit.git /tmp/ai-first-toolkit
mkdir -p .claude/skills
cp -r /tmp/ai-first-toolkit/plugins/people-management/skills/priority-planner .claude/skills/priority-planner
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Priority Planner 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 Priority Planner 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 Priority Planner 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.

Priority Planner

Principle: "You are responsible." The skill proposes, the manager decides. This is not a task manager. It's a thinking partner for prioritisation.

Aggregates signals from multiple sources to surface the manager's highest-leverage actions.

When to Use

  • Start of day: "what should I focus on today?"
  • Start of week: "plan my week"
  • When overwhelmed: "help me prioritise"
  • After a triage: "fold these into my priorities"

Instructions

If any MCP connector is unavailable, follow the connector unavailability protocol in references/operating-principles.md.

1. Determine Scope

Ask or infer whether this is a daily or weekly plan:

  • Daily: focus on today's calendar, current triage, immediate needs
  • Weekly: broader view including upcoming deadlines, OKRs, team development

2. Load Goals

Before gathering signals, load the manager's goals. These are the lens through which everything gets prioritised.

From manager-context/manager-goals.md:

  • The manager's own OKRs and goals
  • Their manager's key priorities
  • Upcoming personal milestones and deadlines

From Notion/Drive (if goals location is known):

  • Pull the latest version of OKRs in case they've been updated since setup

If no goals are found:

⚠️ I don't have your goals on file. Without them I can prioritise by urgency, but not by impact alignment.
Run /setup or tell me your current OKRs so I can connect your priorities to what matters most.

3. Gather Signals

Pull from multiple sources:

Calendar (today or this week):

  • Meetings scheduled and their topics
  • Free blocks (potential focus time)
  • Deadlines tied to calendar events

Triage results (if /triage-messages was recently run):

  • Any 🔴 "Needs Decision" items still unresolved
  • 🟡 Team needs awaiting attention
  • Customer items flagged

Manager Context (from manager-context/):

  • Team members' current projects and any known blockers
  • Development conversations due
  • 1:1s this week and prep status
  • Triage rules (VIPs, hot channels) from triage-rules.md

Notion:

  • Search for OKRs, quarterly goals, team priorities docs
  • Any pages tagged with deadlines or milestones

Slack:

  • Threads where the manager promised to follow up
  • Open questions directed at the manager

4. Categorise into Buckets

Group everything into three categories (inspired by Eisenhower):

🔴 Urgent: Time-Sensitive Decisions Things where someone is blocked or a deadline is imminent:

  • Decisions only the manager can make
  • Escalations that need resolution today
  • Deadlines within 24-48 hours
  • Framework: Execution

🟡 Important: High-Impact Work Things that move OKRs and team goals forward:

  • Strategic work (planning, decision-making, alignment)
  • Cross-functional alignment needed
  • Customer-related actions that affect account health
  • Framework: Delegation & Execution

🟢 Invest: Development & Strategic Thinking Things that compound over time but rarely feel urgent:

  • 1:1 preparation and development conversations
  • Team health check-ins
  • Hiring pipeline attention
  • Strategic thinking and planning
  • Framework: People Development

5. Produce the Plan

Read references/output-template.md for the full output template structure.

6. Present and Iterate

Here's a suggested priority plan. This is a starting point. Adjust based on your judgment. Want me to:
- Move anything between categories?
- Add something I missed?
- Prep for any of these items?

Important Notes

Read references/operating-principles.md for shared operating principles (data scope, DM flagging, signals vs diagnoses, connector unavailability).

Additional notes specific to this skill:

  • Never prescribe. Use "I'd suggest", "Consider". The manager knows context the tool doesn't.
  • The Invest bucket is crucial. Don't let it be empty. Great managers always invest time in development, even when busy.
  • Connect to frameworks. Note which management framework dimension (from manager-context/management-framework.md) an action supports.
  • Don't just list everything. The "What I'd Deprioritise" section is often more valuable than the priority list itself.
  • Time-box awareness. If the calendar is packed, don't suggest 8 hours of focus work. Be realistic.
  • Goal alignment is the core insight. If there's persistent drift between daily activity and goals, say so clearly.
  • Be honest about drift. Don't sugarcoat. If 80% of time is reactive and 0% on OKRs, name it.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Priority Planner AI skill do?

Helps managers cut through noise and identify their highest-leverage actions for the day or week. Aggregates signals from calendar, triage, team context, and OKRs/goals. Presents a suggested focus list grouped by urgency, importance, and investment. The manager reviews and adjusts. Supports effective execution and prioritisation.

Why use Priority Planner on TypingMind?

Because you install it once and use it with any model. Priority Planner 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 Priority Planner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/priority-planner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Priority Planner?

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 Priority Planner?

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

Is the Priority Planner AI skill free?

Yes. It is published on GitHub by techwolf-ai 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.

Related AI Skills

View all
openclaw logo

Discord User Post

openclaw
OrganizationPopular

Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…

82.2K
391K
1 files
View
openclaw logo

Test Audit

openclaw
OrganizationPopular

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only…

82.2K
391K
1 files
View
openclaw logo

Feishu Perm

openclaw
OrganizationPopular

Feishu collaborator and permission workflows. Activate when the user explicitly asks to inspect or change sharing, permissions, or collaborators.

82.2K
391K
Instructions
View
openclaw logo

Block Kit

openclaw
OrganizationPopular

Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.

82.2K
391K
2 files
View

Set up your own AI workspace now

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