Run the two-axis code review through the Codex CLI (GPT) instead of Claude sub-agents.
Implement a piece of work based on a spec or set of tickets.
Implement the result of /to-spec and /to-tickets in code.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
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).
Service architecture for the Obsidian plugin: Effect services, the plugin runtime that composes them, and the plugin shell. Use when creating, modifying, or wiring services in apps/obsidian/src/services/ or editing zt-main.ts lifecycle code.
Commands and menus in the Obsidian plugin: registering a command, adding an entry to Obsidian's file menu or a view's "More options" menu, building a menu of ZotLit's own, and the `zotlit:*-menu` events other plugins render into. Use when adding or changing a…