Theoretical background for veb-in-c's design choices — memeff root, bitwise leaves, the O(u)-bits derivation from issue
Turn a GitHub issue into a concrete implementation plan for the veb-in-c codebase. Given an issue number, fetch the issue, map it onto the current code, and produce a step-by-step plan with affected files, invariants to preserve, and tests to add. Use when the user wants to start work on a tracked item from ROADMAP.md or the issue tracker.
Pick up a refined GitHub issue and implement it end-to-end using strict red-green-refactor TDD. Creates a branch, cycles through Red/Green/Refactor with one commit per phase, and stops at a green local build. Use when the user hands you a ticket number that has already been through /refine.
Run the SortingBenchmark and report the vEB-sort vs qsort timing comparison. Use when the user wants a perf number after changes to vebtrees.h.
Clean-build the veb-in-c library and run all CTest suites (UnitTests + SortingBenchmark). Use after edits to vebtrees.h or anything under test/, or when the user wants to verify the build is green.
Generate the Doxygen documentation website for veb-in-c and report where the output zip landed. Use when the user wants to refresh docs after public-API or comment changes.
Generate a self-contained handoff prompt for the next Claude session to continue this session's work. Captures issue context, branch state, what's done, what's left, and gotchas. The user copies the output and pastes it as the opening prompt of the next session. Use at the end of a work session — especially when stopping mid-task.