Stats
Actions
Tags
From pandahrms
Manually invoked as `/close` to close a finished piece of Pandahrms work after every card is executed. Verifies every card is already in the per-work `done/` folder and STOPS if any card remains in `active/`; for ticket-driven work invokes `/resolve-ticket` to move the ticket to a resolved, ready-for-release state (status + solution, dev status, Developer Resolution, customer comment); writes the docspace dev-diary log and updates progress; marks the work closed in the per-work `_overview`. Mutating -- it changes ticket state and writes the log. Does NOT move cards. Does NOT raise PRs (that is `/pr`). Does NOT auto-trigger -- only on the slash command or an explicit "close this work" mention.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pandahrms:closeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Mutating close of a finished piece of work. Verifies every card is already in `done/`, updates the ticket status for ticket work, writes the dev-diary log, marks the work closed. Manual. Stops if any card is still in `active/`.
Mutating close of a finished piece of work. Verifies every card is already in done/, updates the ticket status for ticket work, writes the dev-diary log, marks the work closed. Manual. Stops if any card is still in active/.
If pandahrms:optimise-prompt has not run on the current user message, invoke it via the Skill tool with no arguments. Wait for it to return, then continue with the confirmed intent.
Skip when:
Read work_folder from the per-work _overview.md frontmatter -- single source of truth for the path. Scan <work-folder>/active/ and <work-folder>/done/.
<work-folder>/active/ -> list each one (name + the sequence step it sits on) and STOP. Print: Cannot close -- N card(s) still in active/. followed by the list. Do not run any later phase. Do not touch the ticket or the log.<work-folder>/done/ -> continue to Phase 2.Read the per-work _overview.md intake. Detect ticket work by the presence of a Source/ticket field. No ticket field -> skip this phase.
Ticket field present -> invoke /resolve-ticket <ticket-ref> via the Skill tool, passing the ticket ref from the _overview. Draft the field content from the _overview intake + the session's card work, then hand it to /resolve-ticket. That skill owns the full ticket update: dev status -> ready-for-release, status -> resolved with a plain customer-facing solution, resolutionNotes (Developer Resolution), and a customer-facing resolved comment -- with the relevance gate, plain-text rule, customer-facing tone rule, and the confirm-before-mutate gate. Wait for it to return before Phase 3.
/resolve-ticket STOPS on a rejected required transition -> if it stops, do not run Phase 3; report and let the user resolve the ticket state first.
_overview (once).active/./close does NOT move cards and does NOT stamp ## Closed: on cards -- it only verifies they are already in done/./commit./resolve-ticket -- /close does not call the workspace-prod ticket tools directly. The field rules (relevance gate, plain text, customer-facing tone, confirm-before-mutate) are owned by /resolve-ticket.End by telling the user: to raise a PR for the work, run /pr (optional).
npx claudepluginhub pandaworks-software-plt/pandahrms-skills --plugin pandahrmsProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.