Menu
/next — park a discovered bug or TODO for later without stopping current work. NOT for filing bugs found during a code audit (use /bugs for that).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Development wisdom and workflow rules. NOT for project-specific conventions (those live in CLAUDE.md, edit via wisdom).
The `BUGS.md` open-issues queue — entry format, lifecycle, pruning to diary. NOT for the record-don't-fix policy (that's CLAUDE.md Bug Triage Protocol), NOT for resolved-bug history (use /diary), NOT for feature backlog (use TODO.md/specs).
Terminal demo GIF + MP4 recordings for READMEs and social (asciinema + agg + ffmpeg). NOT for general Makefile targets (use software) or GUI screenshots (use visual).
Go development. NOT for non-Go code (use rs, py, ts, tsx, or sh).
Humanize text: strip AI-isms and add real voice. NOT for drafting new copy (use writing).
Python development. NOT for shell scripting (use sh) or non-Python code.
| name | next |
| description | /next — park a discovered bug or TODO for later without stopping current work. NOT for filing bugs found during a code audit (use /bugs for that). |
| when_to_use | park this, log this for later, don't fix now, note this and continue, do this next |
| user-invocable | true |
Record a discovered issue or idea without switching context. Log it and immediately resume whatever was in progress.
/bugs for that.If it looks like a bug: append a one-liner to BUGS.md at project root.
Format: - [ ] <description> (create the file if missing).
If it looks like a feature or general TODO: append to TODO.md at project root.
Format: - [ ] <description> (create the file if missing).
When in doubt: TODO.md.
Say one line: what was logged and where. Then continue immediately — no summary, no context switch, no explanation of what was parked.