medTech-group
@medTech-group Organization
Public Skills
upgrade-setup
by medTech-group
Move a project from solo mode to the full set-up, one upgrade at a time. "Protect main" makes a ruleset and the merge settings on the base branch with gh after one confirmation on the owner's own computer, or guides the person click by click to them everywhere else, reads them back with workflow protection, and opens the pull request that leaves solo mode. "Require these checks", once CI has run on the base branch, adds the ticked checks that ran to the ruleset protecting it (with "up to date" on) and to the profile's ci.required_checks. "Set up unattended runs" asks the questions only runs need, guides the two cloud environments, and writes the answers to the profile in one pull request. "Add try-it links" takes the owner through Cloudflare one screen at a time, then opens a pull request that turns previews on in the profile and reports its own try-it link once it has built. Use when the person asks to protect main, to require the checks, to set up unattended runs or to add try-it links, or picks one where the kit offers it.
check-setup
by medTech-group
Check the set-up - gather what only a Claude session can see (the rulesets and repository settings through the GitHub tools, the base branch's latest check runs and statuses, the open pull requests, the cloud environments, the workflow:run issues, Claude Code's version), hand it to workflow doctor --json as files, show the report worded by the person's experience with the most serious first, and offer each upgrade it names as a choice with "Not now". Changes nothing itself. Use when the person asks to "check the set-up" (or "check the workflow set-up", "is my project set up properly?"), or picks it where the guided start offers it.
merge-check
by medTech-group
Answer "is #12 ready to merge?", "can I merge this?" or "is my change ready?" in the chat, from workflow merge-check --json. "Not yet" gives each reason in plain words and offers the fixes as choices ("Review it now", "Bring it up to date", "Resolve the conflict", "Ask Claude to fix it"); "Ready" gives the try-it link first, then "Merge it now", which checks again on the same head commit and merges with a merge commit pinned to it. Posts nothing on GitHub. Use when someone asks whether a pull request is ready or can be merged, or picks "Check whether #N is ready to merge".
build-ticket
by medTech-group
Build one ready ticket from claim to merge - tdd at the spec's seams, the review panel in rounds until clean, a pull request with its findings table, CI green, the local suite's evidence, and the merge under the merge rule. Use for "implement #N", "build #N", "build #N with a light review" ("quick build #N"), or a ticket session's briefing.
conductor
by medTech-group
Run an unattended build run - ask the owner the run charter's questions once, then hand each ready ticket to its own cloud session, check in on a schedule, keep PRs moving to merge, release as the charter allows, and write the final report. Also resumes or stops a run. Use for "run the backlog unattended", "work over the weekend", "conductor resume", "stop the run".
start
by medTech-group
The guided start - ask what we're working on with clickable choices, split a request into items, propose a path for each (a quick ticket, finding a bug's cause, a spec, a map), record the plan as issues, and offer every next step as a choice, so the person never has to remember a command. Use at the first message of an attended session, on /start, or when the person isn't sure what to do next, and when they say "explain less" or "explain more".
setup-workflow
by medTech-group
Set a project up for the pairnexus workflow in solo mode - explore it, ask only what attended work needs (experience, sensitive data, the explorer, the mode, the owner), read the rulesets back, write the profile, vendor the kit for cloud sessions, write the Matt Pocock skills' per-repo docs, labels, issue templates, the pull request template and CODEOWNERS, and open one pull request to merge and start working. Run once per project.
update-workflow
by medTech-group
Update a project's vendored copy of the pairnexus workflow kit (and its Matt Pocock skills) to a newer release, keeping the project's own edits, through a reviewed pull request.
setup-workflow
by medTech-group
Set a project up for the pairnexus workflow in solo mode - explore it, ask only what attended work needs (experience, sensitive data, the explorer, the mode, the owner), read the rulesets back, write the profile, vendor the kit for cloud sessions, write the Matt Pocock skills' per-repo docs, labels, issue templates, the pull request template and CODEOWNERS, and open one pull request to merge and start working. Run once per project.
update-workflow
by medTech-group
Update a project's vendored copy of the pairnexus workflow kit (and its Matt Pocock skills) to a newer release, keeping the project's own edits, through a reviewed pull request.
build-ticket
by medTech-group
Build one ready ticket from claim to merge - tdd at the spec's seams, the review panel in rounds until clean, a pull request with its findings table, CI green, the local suite's evidence, and the merge under the merge rule. Use for "implement #N", "build #N", "build #N with a light review" ("quick build #N"), or a ticket session's briefing.
upgrade-setup
by medTech-group
Move a project from solo mode to the full set-up, one upgrade at a time. "Protect main" makes a ruleset and the merge settings on the base branch with gh after one confirmation on the owner's own computer, or guides the person click by click to them everywhere else, reads them back with workflow protection, and opens the pull request that leaves solo mode. "Require these checks", once CI has run on the base branch, adds the ticked checks that ran to the ruleset protecting it (with "up to date" on) and to the profile's ci.required_checks. "Set up unattended runs" asks the questions only runs need, guides the two cloud environments, and writes the answers to the profile in one pull request. Use when the person asks to protect main, to require the checks, or to set up unattended runs, or picks one where the kit offers it.
conductor
by medTech-group
Run an unattended build run - ask the owner the run charter's questions once, then hand each ready ticket to its own cloud session, check in on a schedule, keep PRs moving to merge, release as the charter allows, and write the final report. Also resumes or stops a run. Use for "run the backlog unattended", "work over the weekend", "conductor resume", "stop the run".
start
by medTech-group
The guided start - ask what we're working on with clickable choices, split a request into items, propose a path for each (a quick ticket, finding a bug's cause, a spec, a map), record the plan as issues, and offer every next step as a choice, so the person never has to remember a command. Use at the first message of an attended session, on /start, or when the person isn't sure what to do next, and when they say "explain less" or "explain more".
merge-check
by medTech-group
Answer "is #12 ready to merge?", "can I merge this?" or "is my change ready?" in the chat, from workflow merge-check --json. "Not yet" gives each reason in plain words and offers the fixes as choices ("Review it now", "Bring it up to date", "Resolve the conflict", "Ask Claude to fix it"); "Ready" gives the try-it link first, then "Merge it now", which checks again on the same head commit and merges with a merge commit pinned to it. Posts nothing on GitHub. Use when someone asks whether a pull request is ready or can be merged, or picks "Check whether #N is ready to merge".
review-panel
by medTech-group
Review a diff or pull request with independent agents in parallel - Standards, Spec, Correctness (with a security review where it applies) and, for UI, API or CLI changes, an explorer that uses the change from outside. Use on any branch or PR, inside build-ticket or alone.
next
by medTech-group
Find the next ready piece of work (a map decision, a spec to write, or a build ticket) and do it under the workflow's flow. Optional argument - "map", "spec", "build", or an issue number.
run-report
by medTech-group
Write the final report of an unattended run (or a progress report mid-run) - what merged, what was set aside and why, what's live, the outward changes to confirm or undo, the decisions for the owner, the by-hand checks and the follow-ups. Used by the conductor at the end of a run, or alone.
implement
by medTech-group
"Implement a piece of work based on a spec or set of tickets."
implement-spec
by medTech-group
"Implement the result of /to-spec and /to-tickets in code."