Claude Code skills for ways of working: the records a team keeps, from files you already have

Thirteen skills: change requests, action ledgers, exception and risk registers, RFC lint, a decision log, weekly status notes, a private 1:1 ledger, focus time from a calendar export, a vendor scorecard, a working agreement check, a shift handover note and a ranked next-actions list from mail and chat exports. Offline, standard-library scripts, tested.

ways-of-working-skills is a Claude Code plugin for teams and their leads who keep the records that hold a team to its own process: what a change will do before the board approves it, which actions from last month's meetings are still open, which security exceptions have expired and which risks need a fresh look, which design proposals are stuck in review, which operational decisions are due for a second look, what a lead shipped this week, what each side promised in 1:1s, where the focus time went, whether a vendor choice survives a change of weights, whether the repository settings match the team's working agreement, what the next on-call shift needs to know, and which messages across several inboxes and chats need you next. These records usually live in files nobody re-reads. Each skill here reads those files with a small Python script, applies stated rules, cites the file and line behind every finding, and leaves decisions to people.

Find this when you search for: "meeting overload", "action items", "weekly update".

/plugin marketplace add basitalisandhu/ways-of-working-skills
/plugin install ways-of-working@ways-of-working-skills

Quickstart: open Claude Code in a folder of meeting notes and ask "which actions from our syncs are overdue?". Or run a script directly from a clone of this repository, here on the synthetic mail export that ships with next-actions-sweep:

python3 scripts/cli.py next-actions --source work=plugins/ways-of-working/skills/next-actions-sweep/examples/work-mail.json --me [email protected] --as-of 2026-10-16T09:00:00Z --top 3

Real output (exit code 1, because three items need you):

| Rank | Label | From | Subject or excerpt | Deadline | Why |
|---|---|---|---|---|---|
| 1 | do | Sam Lee | Release notes draft | 2026-10-16 | deadline ("EOD"); sent to you; due within 2 days; flagged (score 85) |
| 2 | decide | Priya Shah | Budget sign-off for Q4 tooling | 2026-10-19 | asks for a decision ("sign-off"); sent to you; due in 3 days; high importance; unread (score 76) |
| 3 | reply | Dana Cole | Conference talk slot | - | request ("would you"); sent to you; unread (score 46) |

Waiting on others (1): RE: Vendor contract, to Taylor Reed, 2.9 days.
Nothing was sent, drafted, moved or marked as read.

The Sources and Link columns are left out here for width. Point --source at your own exports (see the skill's Inputs section for how to save them).

Questions, bugs and ideas: open an issue on this repository. Security reports: see SECURITY.md.

This pack is part of claude-skills, which holds every skill I maintain as one marketplace: /plugin marketplace add basitalisandhu/claude-skills.

When to use this

• A Terraform change is going to the change advisory board and you need the record: what is added, changed, destroyed and replaced, and which IAM, security group, KMS, S3 policy or network changes need a reviewer. change-request-writer
• Actions keep reappearing in meeting notes week after week, and nobody knows which are overdue or have no owner. meeting-actions-ledger
• The security exceptions register is due for review, or an audit is coming, and you need to know what has expired, what has no approver and what keeps being renewed. risk-exception-register
• A design proposal needs writing with a security review, or you want to know which RFCs are stuck in review with unanswered questions. rfc-lifecycle
• The team keeps re-deciding things it already decided, and wants a light record with review dates. decision-log
• The weekly status note is due and you want shipped, in review, blocked and carried-over items from git and GitHub exports, not from memory. weekly-status-rollup
• A 1:1 is coming up and you want the open commitments on both sides and the days since the last one, kept private. one-on-one-ledger
• The week feels full of meetings and you want the real load, the back-to-back runs and the longest free blocks from a calendar export. focus-plan
• The quarterly risk review is due and the register has to be compared with this quarter's findings and last quarter's snapshot. risk-register-refresh
• A tool or supplier selection is close, and you want the weighted scores and whether the winner changes when one weight moves. vendor-scorecard
• The team wrote down "PRs need one review" and "main is protected", and you want to know whether the repository settings still say the same. working-agreement-check
• An on-call shift is ending and the next person needs what is open, what has gone quiet, which alerts are noisy and which silences end soon. shift-handover
• Work mail, personal mail, Teams and Slack all need checking, and you want one ranked list of what to reply to, decide or do, plus who still owes you an answer. next-actions-sweep

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗