orientlisted

# Orient **One job: tell the user where the project stands and what to do next, in a shape they can actually read.** The user runs `/jig:orient` (or asks to be oriented) — the calm manager's question, *"where do things stand, and what should I pick up?"* Orient answers it by reading the project's own truth (not guessing), and presenting it in **one fixed, scannable layout**: a headline that tells the honest state, then a short stack of **titled sections**, each a list of **titled bullets** — never a wall of inline prose with items buried mid-sentence. The substance is grounded; the **format is the point**. If the answer reads like a paragraph with five things crammed into it, the skill has failed even if every fact is right. This is a **project-level rescan**, not a mid-flow nudge. A bare conversational *"what's next?"* while actively implementing a slice is asking to continue that slice — not to re-survey the whole project. Orient is for the deliberate "step back and take stock" moment (an explicit `/jig:orient`, a session pickup, a "where are we overall"). --- ## Start from the deterministic headline Do not re-derive the project's lifecycle state by hand — jig already computes it. Run the read-only command spec 088 added and use its line as your factual base: ```bash python3 "${PLUGIN_ROOT}/skills/spec-workflow/workflow.py" orient --project-dir . # → jig hint: <scaffold state> · active specs: <rollup> · focus: <slice needing attention> ``` That single `jig hint:` l