Home / Skills

Skills: ask in plain words

22 written instructions for PM routine. Each skill reads your project file first, runs when you ask or on a schedule, and most save their result to Notion. Ask in English or Ukrainian.

You ask for a prep or a report the way you would ask a colleague, and you get it in minutes, saved where you will look for it. Start with 4 skills and add the next when a routine starts to hurt.

Where each skill runs

Built and tested on macOS. Cowork itself also runs on Windows; the skills marked Mac only will not work there, the rest should, but Windows is not tested yet.

Mac only 2
Needs a Mac: reads Mail.app or captures call audio on the machine.
Your computer, any OS 6
Needs something on your computer: local files, git or a locally installed connector. Mac or Windows does not matter.
Cloud or local 3
Cloud if your tracker has a cloud connector, local if it is self-hosted.
Cloud 11
Uses only cloud connectors such as Notion, Slack or Gmail. Nothing to install on your computer.

projects

Foundation

Keeps a short file per project with everything the other skills need to know, plus the shared rules. Change a fact here and every skill follows.

Say"what projects do I have"
on demandprojects/*.mdCloud

slack-collector

Catch every message

Every chat message and thread lands in Threads without duplicates, and after each pass you can see whose turn it is to answer.

Say"collect slack for Orbit"
dailyThreadsCloud

mac-mail-collector

Catch every message

Your mail, incoming and sent, arrives in Threads as full conversations, sorted by project. Works from Mail.app on your Mac.

Say"collect mail"
dailyThreadsMac only

inbox-responder

Catch every message

A reply draft for every open thread, in the language of the thread, with context from the tracker, errors and topics already pulled in. You edit and send.

Say"draft replies for Orbit"
dailyDraft ResponseCloud

thread-ticket-sync

Catch every message

Shows you which conversations should have become tickets, and turns the ones you pick into developer tasks.

Say"which threads need tickets"
on demandtasksYour computer, any OS

daily-team-prep

Before and during calls

You walk into the internal sync already knowing board movement, blockers, chat topics, open action items and new errors since the last prep.

Say"prep me for the sync on Orbit"
before syncReportsCloud

client-meeting-prep

Before and during calls

Status and talking points for each client meeting, matched to who attends and what kind of meeting it is.

Say"prep the client call"
before meetingReportsCloud

live-tips

Before and during calls

Short hints during the call when something matters, and a transcript with a wrap-up afterwards. Audio stays on your Mac.

Say"live tips"
during the callMeetingsMac only

notion-meeting-topics

Before and during calls

Drop a meeting link and get a detailed bilingual report with decisions and action items, on the same page.

Say"meeting + link"
after meetingMeetingsCloud

weekly-overview

Reports

On Monday morning: what happened last week across all projects, what is still open, where the risks are and what is ahead.

Say"weekly overview"
weeklyReportsCloud

client-report

Reports

A client report in English, weekly, monthly or for steering, ready for you to proofread.

Say"monthly client report for Orbit"
monthlyReportsYour computer, any OS

velocity-report

Reports

Monthly numbers on throughput, cycle time, workload and estimate accuracy, compared with the month before.

Say"velocity for Orbit"
monthlyReportsCloud or local

client-satisfaction-tracker

Reports

Catches early signs that the client is getting frustrated or cooling off, from the tone of chats, mail and calls. Marked internal. Keep these reports in a closed database or on your disk: an internal label does not stop someone from sharing the page.

Say"how is the client"
monthlyReportsCloud

change-request

Scope and risks

Helps you not say yes to scope on the spot: sorts each ask into A, B or C, logs even the free extras and drafts the change request.

Say"the client asks for one more thing"
on demandDecisionsCloud

risk-register

Scope and risks

A risk list that stays current from the tracker, chats, meetings and errors, instead of a list you fill in the night before a review.

Say"check the risks on Orbit"
weeklyRisksCloud

topic-manager

Scope and risks

Pulls meetings and threads about the same subject together, so you can see how a topic has moved over the weeks.

Say"update topics for Orbit"
weeklyTopicsCloud

project-lifecycle

Scope and risks

Walks you through starting a project, taking over a project from another PM, the monthly health check and closing it.

Say"set up a new project Orbit, case A"
on demandconfig + NotionYour computer, any OS

jira-management

Board and stability

Create, update and move tickets with a sentence, following the keys, labels and transitions set for your project.

Say"create a ticket for this bug"
on demandtrackerCloud or local

jira-board-health

Board and stability

A clean board before the review: stale tickets, missing labels, Done without a version and long blocks, found for you.

Say"board health for Orbit"
weeklyReportsCloud or local

stability-scan

Board and stability

A weekly digest of unresolved errors and logs across services, with tickets for new defects. If a source was unreachable, it says so.

Say"stability scan"
weeklyReportsYour computer, any OS

sentry-assistant

Board and stability

Ask about errors in your self-hosted Sentry in plain words and change their status, within the scope set for the project.

Say"what is new in Sentry"
on demandchatYour computer, any OS

deploy-analysis

Board and stability

What is on stage but not yet on production, with release notes. Reads local branches only.

Say"what is on stage but not on prod"
on demandReportsYour computer, any OS

Start with 4

projects, daily-team-prep, client-meeting-prep, weekly-overview. Add the next when a routine starts to hurt.

Set it up

What a skill is

A skill is a text file: when to start, what steps to take, what the result looks like and where to save it. The first step is always the same: read the project file, and ask if no project was named. Most skills work for any project. Skills written for a single client stack stay with that project and are not in the shared plugin.

Read docs/en/04-skills-library.md