Agent skill · langfuse
linear-work-rhythm
Answer "what should I do today" for a Langfuse maintainer, from the tracker rather than from memory: which projects you lead, which owe an update before the Monday engineering weekly, what shipped but is not finished, what waits on your decision, and what colleagues are working on that overlaps. Use on "what should I do today", "what's on my plate", "what should I work on next", "prep my Monday update", "what did I say last week", "who else is working on this", "who should review this", and whenever someone hands over a bare link — a ticket, a pull request, a Slack permalink — and expects you to take it from there.
What it needs
About 9k tokens when loaded.
What this skill does
The working rhythm, read live Answer from the tracker, never from recall. Ownership, health and dates change daily, and a plausible answer assembled from memory is worse than no answer because nobody can tell it is stale. Who the person is comes from ~/.config/langfuse/me.md. If it is not there, ask — their name and what they work on, in one question — and write the file so it is answered for good. Do not send a colleague of a year through onboarding to find out their name; that skill is for people who are new. Do not guess, and do not answer this question for an outside contributor, who owns none of it. The rules behind every check below are the working agreement, published in content/handbook/tools-and-processes/using-linear.mdx in langfuse/langfuse-docs. Read it rather than trusting this file for what is required; this file is only the set of queries that reveal where you stand against it. When the two disagree, the handbook wins and this file is the bug. Read it from origin/main — git fetch -q origin main then git show origin/main:<path> — because a docs checkout is usually parked on an old branch, and quoting a stale agreement is worse than not quoting one. Read these before ranking anything. They say how the team decides what to work on, and this file deliberately does not restate them: Page What you need from it --- --- content/handbook/product-engineering/how-we-work/how-we-ship.mdx Prioritisation, the P0–P3 levels and their timelines, daily response times, the project-update rhythm content/handbook/product-engineering/principles.mdx What product engineers do and explicitly do not do content/handbook/how-we-work/ownership.mdx That product areas are split between engineers by direct ownership content/handbook/tools-and-processes/using-linear.mdx The working agreement: primitives, project lifecycle, definition of done If what you are about to say contradicts one of them, the handbook wins. Do not hand-maintain the responsibility zone Derive it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills langfuse/linear-work-rhythm