菜单
Run a research-first, multi-perspective debate to explore complex technical decisions (trade-offs, architecture choices, integration strategies) using concrete codebase evidence. Use when the user asks to "debate" approaches, compare options, or needs a structured exploration before deciding.
Keep a tiny-step implementation diary during coding sessions (what changed, why, commands run, failures, and what was learned), with docmgr integration (doc add/relate/changelog). Use when the user asks to "keep a diary", "write a dev log", or document work step-by-step.
Use the docmgr CLI to manage ticketed docs (create tickets, add docs, relate code files with file-note, update changelog, and search). Use when the user asks how to use docmgr, wants a docmgr command sequence, or needs docmgr best practices (file-note, quoting, doctor).
Provide a pre-commit checklist and staging hygiene (review diffs, stage specific files, avoid common noise like dist/ or .env, and fix mistakes with reset/rm --cached/amend). Use when the user is about to commit, asks for a commit workflow, or needs help cleaning up staged files.
Upload markdown (including docmgr ticket docs) to a reMarkable device as PDF via a local uploader script, with a safe dry-run and optional mirroring of ticket structure. Use when the user asks to send docs to reMarkable, export markdown to PDF for reMarkable, or troubleshoot rmapi/pandoc/xelatex.
| name | cursor-debate |
| description | Run a research-first, multi-perspective debate to explore complex technical decisions (trade-offs, architecture choices, integration strategies) using concrete codebase evidence. Use when the user asks to "debate" approaches, compare options, or needs a structured exploration before deciding. |
Structure an evidence-based “debate round” to surface ideas and trade-offs; the debate does not decide, it informs the human decision-maker.
rg -n "...", git grep, git log -p -- <path>, go test ./..., etc.Use the canonical outline in references/debate.md.