Consulting delivery skills for Claude Code: SOW review, status reports, transcript actions, stakeholder prep, change requests, deliverable QA, and a read-only weekly brief.
5 on GitHubby Lee Whieldonv2.0.0MITupdated 1 month ago
Draft a formal change request document from a description of a proposed scope change, with impact assessment, assumptions, exclusions, and an approval block. Use when a scope change needs to be documented and approved. Usage - /change-request describe what is changing and why
code-review-light
Plain-English review of a code file, SQL script, config, or data artifact for a delivery lead who is not an engineer. Explains what it does, what could go wrong, and what to ask the developer. Usage - /code-review-light path/to/file
deliverable-qa
QA a client deliverable, report, or presentation against consulting quality standards before it goes out. Use when asked to review, QA, proofread, or sanity-check anything client-facing. Usage - /deliverable-qa path/to/deliverable
exec-summary
Compress a long document (SOW, report, assessment, change request) into a one-page executive summary for a C-suite or board audience. Use when a decision-maker will not read the full document. Usage - /exec-summary path/to/document.md -- audience notes
meeting-prep
Prepare a full briefing package for a client meeting, stakeholder call, or steering committee, with agenda, key messages, tough questions, a pre-meeting checklist, and a follow-up email draft. Use when planning or preparing for any meeting. Usage - /meeting-prep describe the meeting
sow-review
Review a Statement of Work for scope risks, ambiguous language, missing protections, and negotiation points. Use before signing or whenever a client sends a new or revised SOW. Usage - /sow-review path/to/sow.md
stakeholder-prep
Prepare for a stakeholder meeting with an agenda, talking points, anticipated objections with responses, and a follow-up email draft. Use 30 to 60 minutes before a client or executive call. Usage - /stakeholder-prep describe the meeting and who is in it
status-comms
Draft the same project status story in multiple formats - a status email, slide bullets, or a dashboard narrative - tuned to the audience. Use when asked for a status email, executive update, or slide-ready status. Usage - /status-comms audience and format, plus the data source
status-report
Generate a weekly project status report from a status CSV or free-text notes, with RAG status, accomplishments, upcoming work, risks, and actions. Use when you need a client-ready update from raw project data. Usage - /status-report path/to/status-data.csv
transcript-actions
Extract action items, decisions, open questions, and risks from a meeting transcript or rough notes, with a short summary. Use after any client or internal call. Usage - /transcript-actions path/to/transcript.txt
weekly-brief
Monday brief for a project folder - what changed in the last 7 days, overdue and due-this-week actions, open decisions, and the meetings to prepare for. Read-only, safe to run on a schedule. Usage - /weekly-brief path/to/project-folder
Shippo connects you to USPS, UPS, FedEx, DHL, and 40+ carriers, so you can handle a shipment end to end right inside Claude. Compare live rates and pick the cheapest or best option, buy and print labels (domestic and international, with customs declarations), validate and standardize addresses, and track packages across carriers. Just ask in plain language: rate-shop a parcel, buy the right label, check a delivery status, or confirm an address before you ship. Whether you run a store or just need to send a package, Shippo turns a pile of carrier accounts into one simple conversation.
The official monday.com plugin for Claude Cowork. Manage boards, items, docs, and forms across work management, CRM, dev, service, and campaigns. Full read and write access via OAuth.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.