Menu
Create a checkbox task plan for a feature or fix. Output is a markdown file that `/work` executes one task at a time.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Check recent HL7v2 processing errors in Aidbox, diagnose root causes, suggest fixes. Use when asked to check errors, diagnose failures, or troubleshoot message processing.
Look up FHIR R4 resource/datatype fields, types, cardinality, reference targets, and coded enums (including custom resources like IncomingHL7v2Message, OutgoingBarMessage). Use when writing converters or verifying FHIR compliance.
Build a new HL7v2→FHIR message converter or extend an existing one. Orchestrates requirements gathering, then delegates to `/plan` and `/work`.
Execute a plan produced by `/plan` — one task at a time, with tests and an independent review after each task.
Authenticate ad-hoc curl requests to the local Aidbox using the root Client secret from docker-compose.yaml. Use for debugging and one-off queries from the shell (not from app code — `src/aidbox.ts` already wraps auth).
Look up HL7v2 segment fields, datatypes, components, tables, and message structures. Use when writing converters, checking field positions/optionality, or verifying HL7v2 spec compliance.
| name | plan |
| description | Create a checkbox task plan for a feature or fix. Output is a markdown file that `/work` executes one task at a time. |
Write an implementation plan as a markdown file of checkbox tasks. The plan is executed by /work, one task at a time with user checkpoints.
Location: ai/tickets/YYYY-MM-DD-short-name.md
If the ticket already has upstream sections (e.g. # Requirements from a prior phase), leave them in place and append the plan as its own section. Reference upstream content by heading — don't duplicate it.
CLAUDE.md directly. For unfamiliar areas, spawn an Explore agent via the Agent tool:
Agent({
description: "Explore <area>",
subagent_type: "Explore",
prompt: "Find <what you need>. Focus: <files or patterns>. Report under 200 words."
})
# Plan: [Name]
## Overview
[2–4 sentences: what and why]
## Validation
- `bun test:local`
- `bun run typecheck`
## Task 1: [Name]
- [ ] Specific action with file/function reference
- [ ] ...
- [ ] Write/update tests
- [ ] Run validation — must pass
- [ ] Stop for user review before next task
## Task 2: ...
## Task N: Cleanup
- [ ] Update docs (CLAUDE.md, inline comments) if patterns changed
- [ ] Final `bun test:all`
src/foo/bar.ts:42), not "the bar module."OPEN: inline in the plan rather than leaving implicit ambiguity.