elentok

Author a teach workspace's lessons/reference/index in markdown and build both the browsable HTML site and a phone-friendly EPUB from that one source.

A relentless interview that asks every frontier question at once, round by round.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Print the relevant text as raw copy-able markdown and copy it to the clipboard. Run `/markdown file` to copy it as a file reference instead, for pasting into Slack.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Implement a piece of work based on a spec or set of tickets.

Commit staged git changes, or include current changes only when the user explicitly says /commit all or $commit all. Use when asked to commit, create a commit, or finalize changes.

Author and edit qmkmd keyboard-layout files — QMK keymaps written in Markdown. Use when editing a *.layout.md file, or any Markdown file that contains qmkmd code blocks (```structure, ```layer:NAME, ```aliases, ```combos, ```options). Covers the block structure, the shorthand mapping syntax (simple keys, mod-tap, layer-tap, one-shot mods, chords, layer commands, aliases, raw), and the build/ format/copy CLI workflow. Do NOT use merely because a doc quotes qmkmd syntax; use it when actually creating or modifying a layout.