wiki / segments / cli / workflowedited 2026-07-19
CLI — workflow

The daily loop Segments is built around: capture everything, then always know what to pick up next.

sg init          # once, in the project directory
sg add           # capture work as it appears
sg next          # what should I do now?
sg done <id>     # ship it

The ready queue

A task is ready when it is a todo with no outstanding blockers. sg next ranks the ready queue — highest priority first, oldest wins ties — and prints the best pick followed by the rest. Dependency chains (task B blocked by task A) keep downstream work out of the queue until its blockers land.

Priorities

0Incident — drop everything.1Ship-critical — required for the project's v1 thesis.2Standard — planned work, the default.3Extra — nice-to-have.

Projects

sg list scopes to the project matching the working-directory name, so a plain sg list inside a repo shows that repo’s tasks. The web UI’s All tasks scope aggregates across every project when you want the portfolio view.

Snapshots and migration

sg export streams task state as JSONL — one event per line — suitable for git-tracked snapshots or downstream pipelines. Configure a path in config.yaml to have every CLI / MCP mutation append automatically. Coming from Beads, sg beads imports an existing backlog wholesale.