open-supply-hub

Create business-oriented Confluence release notes (draft) and a Slack post draft from GitHub doc/release/RELEASE-NOTES.md. Files the Confluence page via Atlassian MCP (createConfluencePage) after user approval; Slack post is chat-only. Page structure: metadata table (Description row), Programs warning panel, issue table with Jira inline previews. GitHub is source of truth for tickets; Jira provides business context.

Draft, review, and file Jira tickets in OS Hub's house style — Stories (sprint-ready work with Requirements + Given/When/Then Acceptance Criteria) and Epics (feature groups with Background, Scope, and Requirements table). Coaches the user through the body and pushes for specificity, then prompts for parent, priority, labels, and other Jira fields so tickets never float. Files to OSDEV via the Atlassian MCP with two user checkpoints. Auto-loads on requests like "write a Jira ticket", "draft a story for X", "scope this as an epic", "write requirements".

Draft, review, improve, and file user stories in OS Hub's house style — 4-line format (As a / I want to / So that / What is hard today). Coaches the user through it: asks questions, proposes drafts to react to, iterates. Adapts to what they bring — a near-final draft, customer ask, persona+situation, or nothing yet. Files to OSDEV as an Initiative when they confirm. Auto-loads on requests like "write a user story", "draft stories for X", "fix this story", "what's the real need here".

Read a Jira ticket and produce a written plan saved as a markdown file. No code, no branches, no commits — just a quality plan. Use when the user asks to plan, scope, or think through an OSDEV ticket before building.

Full ticket pipeline for OS Hub — read a Jira ticket, plan, implement, test, preview, create PR. Use ONLY when the user explicitly invokes the /ship command or asks to "ship a ticket" with an OSDEV key. Do not auto-invoke on general mentions of planning, building, or implementing — /ship is a deliberate multi-step pipeline that requires explicit user trigger.

Make a copy edit anywhere on the OS Hub platform — change visible text on the website, in a form label, button, error message, navbar item, email template, or anywhere user-facing text appears. Use ONLY when the user explicitly invokes /copy-ship. Do not auto-invoke on general edit language. This skill exists so any teammate (engineer or not) can ship a text-only change end-to-end without manual file hunting.

Answer "can OS Hub do X today?" or "is X on our site / docs / codebase?" questions. Use when a salesperson, partner, customer success rep, executive, or any non-engineer needs to know whether a capability or piece of information exists today — across the codebase (what's deployed), Confluence (internal how-tos like moderation, claims, list upload), the info site (info.opensupplyhub.org — customer-facing docs), or Jira (in-flight work). Returns paths to the answer ranked from "I can pull it now" to "would need to be built." Auto-loads on questions like "can OS Hub...", "does the platform support...", "is X possible today...", "do we have a page on...", "where would I find...".

Explain a file, function, system, API, database, lambda, or any piece of OS Hub code or infrastructure in plain English, calibrated to the reader's experience level. Use when the user asks to explain, walk through, break down, or describe how something works.

Update release notes entries in doc/release/RELEASE-NOTES.md. Use when the user asks to write, draft, add, or update release notes, or when preparing a new release entry.

Write high-quality pull request descriptions based on Google's CL description best practices. Use when creating a pull request, writing a PR description, or when the user asks to describe changes for a PR or merge request.