projects
FoundationKeeps 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.
Home / Skills
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.
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.
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.
Every chat message and thread lands in Threads without duplicates, and after each pass you can see whose turn it is to answer.
Your mail, incoming and sent, arrives in Threads as full conversations, sorted by project. Works from Mail.app on your Mac.
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.
Shows you which conversations should have become tickets, and turns the ones you pick into developer tasks.
You walk into the internal sync already knowing board movement, blockers, chat topics, open action items and new errors since the last prep.
Status and talking points for each client meeting, matched to who attends and what kind of meeting it is.
Short hints during the call when something matters, and a transcript with a wrap-up afterwards. Audio stays on your Mac.
Drop a meeting link and get a detailed bilingual report with decisions and action items, on the same page.
On Monday morning: what happened last week across all projects, what is still open, where the risks are and what is ahead.
A client report in English, weekly, monthly or for steering, ready for you to proofread.
Monthly numbers on throughput, cycle time, workload and estimate accuracy, compared with the month before.
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.
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.
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.
Pulls meetings and threads about the same subject together, so you can see how a topic has moved over the weeks.
Walks you through starting a project, taking over a project from another PM, the monthly health check and closing it.
Create, update and move tickets with a sentence, following the keys, labels and transitions set for your project.
A clean board before the review: stale tickets, missing labels, Done without a version and long blocks, found for you.
A weekly digest of unresolved errors and logs across services, with tickets for new defects. If a source was unreachable, it says so.
Ask about errors in your self-hosted Sentry in plain words and change their status, within the scope set for the project.
What is on stage but not yet on production, with release notes. Reads local branches only.
projects, daily-team-prep, client-meeting-prep, weekly-overview. Add the next when a routine starts to hurt.
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