flagslisted

# flags — blockers & follow-ups flag = open question / blocker. `--feature <id>` set -> the flag is that feature's blocker (joined on the roadmap; shown on the Roadmap card + Flags tab). `<self>` = your shell_id. All reads/writes go through `sc mem` (the engine API) — there is no `sqlite3` path. ## Surface ``` sc mem get flags # open flags as five-line evidence blocks (identity/status + four detail lines) sc mem get flags --json # same, as JSON sc mem get flags <id> # exact non-deleted row, open or resolved sc mem get flags --feature <id> --resolved # resolved non-deleted rows for one feature ``` Each flag carries its `feature_id`; cross-reference `sc mem get roadmap` for the blocked feature's title. The default list forms are **open-only**. Exact and feature-scoped resolved reads include numeric id, display name, owner, feature, priority, description, opened date, resolved date, and closure notes in human and JSON output. Resolved history without `--feature` is refused; there is no fleet-wide history read. The exact CLI form reuses the authenticated single-row endpoint that protects `flag close`: ``` GET /_sc/mem/flags/{id} ``` ## Open ``` sc mem flag open "[Area] what's blocked | Blocker for: X" --name SC-001 --priority Medium [--feature <id>] ``` - `--name` = short id, format `SC-###`. - description format = `[Area] {what} | Blocker for: {what it blocks}`. - `--priority` = High / Medium / Low. `--feature` = the feature it