Investigate a beads issue in the current checkout, gather context from its dependency graph, and produce a plan-skeleton + triage verdict (ready / needs-info / blocked). Use when the user says "investigate bd-XXXX", "let's look at bd-XXXX", or pastes a beads issue ID and asks what's needed to work on it.
Improve prose clarity using the reader-expectations methodology of Gopen & Swan ("The Science of Scientific Writing", American Scientist, Nov-Dec 1990). Use when the user asks for writing improvement, prose review, revision suggestions, help making writing clearer or more readable, feedback on a draft, or mentions clarity, flow, emphasis, sentence structure, or "why this passage is hard to read". Works on any expository prose (papers, reports, memos, docs, essays), not only scientific writing.
Diagnose and fix DOM / style differences between `q2 preview` and `q2 render` so the two pipelines produce visually-equivalent output. Use when the user reports that the preview's appearance, spacing, classes, or DOM structure doesn't match the rendered site — phrases like "preview vs render differs", "preview shows X differently", "spacing/margin/padding off", "DOM doesn't match", "missing class in preview", or shows a specific computed-style mismatch (e.g. "17px in preview, 34px in render"). Also invoked explicitly via `/preview-parity`.
Set up an isolated worktree and triage a GitHub issue into a durable on-branch record. Use when the user says "triage issue