Scrummy Skill banner
frty2-ai frty2-ai

Scrummy Skill

Development community

Description

Chief of staff for a Scrummy (Plane) workspace — a Claude skill that turns conversations and code into board state, says what's next, briefs stakeholders, and flags deadlines that cannot absorb a late start.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

scrummy — a chief of staff for your Scrummy workspace

A skill for Claude that sits on top of the Scrummy (Plane) MCP and behaves like a chief of staff rather than a tool wrapper. The MCP exposes the raw surface: work items, states, labels, modules, cycles, comments, pages, relations, members. This skill supplies the judgment: what to write down after a conversation, what to do next, who is idle, which deadline cannot absorb a late start, and how to say all of it in five lines.

It is built for people who do not want to operate a project tool: solo developers running ten repos, developers who would rather the board followed their commits, product managers who keep decisions in chat, marketers with launch dates, salespeople with follow-ups, founders with everything parked on themselves, agencies with many clients, and enterprise teams that need the trail to survive an audit.

What it does

You talk. It does the bookkeeping, then tells you the one thing that changes your day.

You say It does
dump: and five minutes of meeting residue Updates what changed, creates what is new, records decisions on the items they affect, flags risks, lists what it could not place
"done with the auth branch, what's next" Reads git, moves the items the commits and PRs prove, links the PR, then recommends the next item with its context loaded
"standup me" / "update for the board" / "status for the client" A brief at the right altitude for that reader, as text you can paste
"reviewed the landing page, two changes then good" Records the verdict and feedback, moves the state, creates the follow-ups, drafts the note to the owner
"we should launch Apple Pay by October" A module with items, owners and dates that work backwards from the target, and the last safe start date said out loud
"who's idle" / "what's on my plate that shouldn't be" One specific handoff, with a name and a reason
"are we on track" The one deadline that matters a