beyondessential

Review this card's specs with fresh eyes for gaps, contradictions, and cross-spec impact

中文简介正在准备中。当前显示原文说明。

Split a working doc into the card's specs, plan, and test cases once its shape is clear

中文简介正在准备中。当前显示原文说明。

Run a support investigation as a suggest-and-interpret loop, never executing anything yourself — orient to the product's support pack and follow the signal with judgment. Use when someone asks for help triaging, investigating, or resolving an operational or support issue on a deployment. Not for feature-development cards (see investigate-and-fix and implement-this).

中文简介正在准备中。当前显示原文说明。

Check upgrade safety for a Tamanu upgrade that spans many versions: verify that every intermediate hotfix is included in the target version, and surface the new configuration/settings, data migrations, and FHIR rematerialisation impact the upgrade brings. Use when the user wants to check an upgrade from one Tamanu version to another (e.g. "check hotfixes from v2.31 to v2.47"), confirm no intermediate hotfix was dropped, or understand what config, migrations, and FHIR rework a multi-version jump requires. Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for cutting a release (see release-cutoff-checks) or deciding which tests to run (see scope-tamanu-release-tests).

中文简介正在准备中。当前显示原文说明。

Produce or refine a project-level mockup illustrating a section of the PRD

中文简介正在准备中。当前显示原文说明。

Workshop the shape of this project — audience, components, ambiguities — before drafting the PRD

中文简介正在准备中。当前显示原文说明。

Draft edits to existing specs (or a new spec if no existing one fits) from the card description

中文简介正在准备中。当前显示原文说明。

Draft or refine the test-cases checklist for this card

中文简介正在准备中。当前显示原文说明。

Interview me about this card to develop the acceptance criteria

中文简介正在准备中。当前显示原文说明。

Run Tamanu pre-release verification checks: verify that hotfixes on the current release branch are merged forward to main, and that hotfixes from prior release branches are included in the current release. Use when the user wants to run "pre-release checks", verify hotfix integrity before cutting or shipping a Tamanu release, confirm a release/X.YY branch is safe to release, or check that no hotfix has been orphaned (left on neither main nor the current release). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for deciding which tests to run (see scope-tamanu-release-tests).

中文简介正在准备中。当前显示原文说明。

Drive the card's Review Hero loop by hand — trigger a review, address its comments, rerun until clean, then merge. Use in an external tool (Claude Code, Cursor) where Workhorse's automated loop isn't running.

中文简介正在准备中。当前显示原文说明。

Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases

中文简介正在准备中。当前显示原文说明。

Workshop the technical approach and capture notes in the plan

中文简介正在准备中。当前显示原文说明。

Update npm/yarn/pnpm dependencies using manifest-first, lockfile-aware workflows. Prefer declared version bumps over resolution overrides. Use when updating, upgrading, or patching dependencies; fixing transitive dependency versions; addressing npm audit or CVE findings; or removing stale overrides.

中文简介正在准备中。当前显示原文说明。

Workshop this idea with me

中文简介正在准备中。当前显示原文说明。