Appearance
Capture Workflows
Lightweight capture for ideas that surface mid-execution but don't yet belong to a plan. Capture is fast and cheap by design — np:triage decides later whether they become Tasks, Backlog items, or get dropped.
np:add-todo
Capture a pending todo. Writes a Markdown file under .nubos-pilot/todos/pending/ and bumps the count in STATE.md. The todo carries a one-line title plus a few lines of free-form context.
bash
np:add-todo "Investigate slow plan-checker pass on Phase 5"A todo lives under pending/ until np:triage promotes it to a Task or Backlog item, or moves it to a dropped/ archive.
np:note
Capture a free-form note. Project default writes under .nubos-pilot/notes/; --global writes to ~/.nubos-pilot/notes/ (cross-project). Notes never bind to a unit-type — they are pure "I want to remember this" capture.
np:add-backlog
Append a backlog item. Adds a 999.x entry to ROADMAP.md (the 999 block is the conventional backlog band) and scaffolds an empty phase directory at .nubos-pilot/phases/999.x-<slug>/. The next-decimal slot is computed via np-tools.cjs phase next-decimal 999.
Use this when an idea is bigger than a Todo (needs rationale + rough scoping) but you are not ready to plan or execute it.
np:thread
Cross-session thread CRUD. Threads live under .nubos-pilot/threads/<id>-<slug>/ and persist a conversation context that survives across host CLI sessions. Subcommands:
create <topic>— open a new thread, returns its slug.resume <slug>— re-attach to an existing thread.
Threads have an OPEN → IN_PROGRESS lifecycle; there is intentionally no close command — closure happens by promotion to a Phase or Task.