devague 0.10.0__tar.gz → 0.11.1__tar.gz

{devague-0.10.0 → devague-0.11.1}/.claude/skills/assign-to-workforce/scripts/assign-to-workforce.sh

@@ -90,8 +90,17 @@ cmd_split_plan() {
         shift
     done
 
-    local waves_json tmp_err waves_rc
+    local waves_json tmp_err waves_rc old_exit_trap
+    # Clean up the temp file on any exit path — including a signal after its
+    # creation — WITHOUT permanently changing the script's process-global EXIT
+    # handling. Capture any prior EXIT trap BEFORE mktemp (that capture forks a
+    # subshell, so doing it first keeps it out of the untracked-file window),
+    # then install our cleanup trap on the line immediately after mktemp, and
+    # restore the prior trap once the file is safely gone (#30; PR #31 review;
+    # devague#32).
+    old_exit_trap="$(trap -p EXIT)"
     tmp_err="$(mktemp)"
+    trap 'rm -f "$tmp_err"' EXIT
     set +e
     waves_json="$("${DEVAGUE[@]}" plan waves --json "${extra_args[@]}" 2>"$tmp_err")"
     waves_rc=$?
@@ -99,6 +108,8 @@ cmd_split_plan() {
     local waves_err
     waves_err="$(cat "$tmp_err")"
     rm -f "$tmp_err"
+    trap - EXIT
+    eval "${old_exit_trap}"  # empty string is a no-op; re-installs a prior trap if any
 
     if [ "$waves_rc" -ne 0 ]; then
         printf '%s\n' "$waves_err" >&2

{devague-0.10.0 → devague-0.11.1}/.claude/skills/spec-to-plan/SKILL.md

@@ -41,8 +41,9 @@ bash .claude/skills/spec-to-plan/scripts/spec-to-plan.sh status
 
 It resolves the CLI portably — an installed `devague` on `PATH` (the normal
 case), falling back to `uv run devague` inside the devague checkout, else an
-install hint. Every move except `status` is forwarded verbatim as `devague plan
-<move>`, so you can equally call the CLI directly (`devague plan <move> …`).
+install hint. Every move — including `status` — is forwarded verbatim as
+`devague plan <move>`, so you can equally call the CLI directly
+(`devague plan <move> …`).
 
 ### Moves
 
@@ -58,17 +59,24 @@ install hint. Every move except `status` is forwarded verbatim as `devague plan
 | `converge` | Evaluate the gate against the **live** source frame; list remaining gaps. |
 | `export` | Write the buildable plan to `docs/plans/` — only after `converge` passes. |
 | `waves` | Emit deterministic dependency waves (`{plan, waves}`) — scheduling metadata only, *not* orchestration. Read-only, works on an in-progress plan; refuses a cyclic/dangling graph. Devague describes the graph; an operator decides how to run it (#20). |
+| `status` | Read-only: where the plan stands + the recommended next move, re-checked against the live frame (`--json` too). |
 | `show` / `list` | Render a plan / list plans (`--json` for raw state). |
 | `learn` / `explain <move>` | Teach the method / explain one move. |
 
 Risk kinds (shared with the frame engine): `unknown_nonblocking`,
 `unknown_blocking`, `out_of_scope`, `follow_up`.
 
-### `status` — the next-move helper
-
-`status` is a wrapper-only verb. It reads `devague plan converge --json` +
-`devague plan list --json` and prints where the current plan stands, the
-remaining gaps, and the recommended next move derived from the first gap.
+### `status` — the next-move verb
+
+`status` is a first-class, **read-only** CLI verb (`devague plan status`,
+internalised from this wrapper in 0.11.0 — issue
+[#30](https://github.com/agentculture/devague/issues/30)). It composes
+`devague plan list` + `devague plan converge` and prints where the current plan
+stands, the remaining gaps, and the recommended next move derived from the first
+gap. Like `converge`/`export` it re-checks the **live** source frame (so frame
+drift surfaces as an error), but it never mutates state. Pass `--json` for the
+structured payload (`{plan, total, ready_for_plan, blockers, warnings,
+parked_items, required_next_moves}`).
 
 ```text
 plan: my-feature    (1 plan total)

devague-0.11.1/.claude/skills/spec-to-plan/scripts/spec-to-plan.sh

@@ -0,0 +1,102 @@
+#!/usr/bin/env bash
+# spec-to-plan.sh — drive devague's spec→plan engine (the /spec-to-plan skill).
+#
+# The skill is named `spec-to-plan`; the product/CLI it drives is `devague` (the
+# idea→spec half lives in the sibling /think skill). This wrapper forwards every
+# move to `devague plan <move>` verbatim — including the `status` verb the CLI
+# internalised in 0.11.0 (devague#30/#31), which reads the plan convergence gate
+# and names the recommended next move. It is the forward leg: seed a plan from a
+# *converged* frame, then work it into a buildable plan.
+#
+# Origin: authored and maintained in agentculture/devague. steward pulls this
+# skill from here and broadcasts it to the rest of the AgentCulture mesh, so it
+# is written to run anywhere — portable bash, no devague-checkout assumptions.
+#
+# Plans persist under .devague/ in the current directory (alongside frames), so
+# run from the repo you are speccing.
+
+set -euo pipefail
+
+# ── resolve the devague CLI (mesh-first, then local-dev fallback) ───────────
+DEVAGUE=()
+resolve_devague() {
+    if command -v devague >/dev/null 2>&1; then
+        DEVAGUE=(devague)            # installed tool — the normal mesh case
+        return 0
+    fi
+    # Local-dev fallback: inside the devague checkout, run via uv.
+    local dir="$PWD"
+    while [ -n "$dir" ] && [ "$dir" != "/" ]; do
+        if [ -f "$dir/pyproject.toml" ] \
+            && grep -q '^name = "devague"' "$dir/pyproject.toml" 2>/dev/null; then
+            if command -v uv >/dev/null 2>&1; then
+                DEVAGUE=(uv run devague)
+                return 0
+            fi
+            break
+        fi
+        dir=$(dirname "$dir")
+    done
+    cat >&2 <<'EOF'
+error: devague CLI not found.
+hint: install it with `uv tool install devague` (or `pipx install devague`),
+      or run from inside the devague checkout with `uv` available.
+      https://github.com/agentculture/devague
+EOF
+    return 1
+}
+
+usage() {
+    cat <<'EOF'
+spec-to-plan.sh — drive devague's spec→plan engine (the /spec-to-plan skill).
+
+Usage:
+  spec-to-plan.sh <move> [args...]   forward a `devague plan` move
+  spec-to-plan.sh status [--plan S]  where the plan stands + the next move
+  spec-to-plan.sh help               this help
+
+Moves (forwarded to `devague plan`; run `devague plan learn` for the method):
+  new          start a plan from a CONVERGED frame (--frame <slug>)
+  task         add a task (--accept / --dep / --covers, --origin user|llm)
+  accept       add an acceptance criterion to a task
+  depend       record that a task depends on another (--on)
+  cover        mark a task as covering a coverage target (c*/h*)
+  confirm      confirm a task                          (USER-only decision)
+  reject       reject a task
+  risk         record a first-class plan risk
+  converge     check whether the plan can export
+  export       write the buildable plan (only after converge passes)
+  waves        emit deterministic dependency waves (scheduling metadata, not orchestration)
+  status       where the plan stands + the recommended next move
+  show / list  render a plan / list plans
+  learn        teach the method   |   explain <move>  explain one move
+
+Plans persist under .devague/ in the current directory — run from the repo you
+are speccing. Results go to stdout, diagnostics to stderr; pass --json to any
+move for structured output.
+
+Note: every move — including `status` — is forwarded verbatim as `devague plan
+<move>`, so new plan moves work without editing this script. (`status` was
+internalised into the CLI in devague 0.11.0; it is no longer wrapper-only.)
+
+Prior leg: a plan is seeded from a converged frame produced by the /think skill.
+EOF
+}
+
+main() {
+    case "${1:-help}" in
+        help | -h | --help)
+            usage
+            return 0
+            ;;
+        *)
+            # Forward every move to `devague plan <move>` verbatim — including the
+            # internalised `status` verb (`devague plan status`) — so the CLI's own
+            # parser owns the plan surface.
+            resolve_devague
+            exec "${DEVAGUE[@]}" plan "$@"
+            ;;
+    esac
+}
+
+main "$@"

{devague-0.10.0 → devague-0.11.1}/.claude/skills/think/SKILL.md

@@ -31,8 +31,9 @@ fixed sequence of prompts. **You (the agent) choose the next move; the CLI just
 tracks state and tells you what's still missing.** Run `devague learn` for the
 canonical ten-stage arc and `devague explain <move>` for any single move.
 
-This skill is the operator: a portable wrapper plus one helper (`status`) that
-reads the convergence gate and tells you the recommended next move.
+This skill is the operator: a portable wrapper that resolves the CLI and
+forwards every move verbatim — including `status`, the read-only verb that reads
+the convergence gate and tells you the recommended next move.
 
 ## How to run
 
@@ -47,9 +48,9 @@ bash .claude/skills/think/scripts/think.sh status
 It resolves the CLI portably — an installed `devague` on `PATH` (the normal
 case), falling back to `uv run devague` when you are inside the devague checkout.
 If neither resolves it prints an install hint (`uv tool install devague`). Every
-move except `status` is forwarded verbatim, so you can equally call the CLI
-directly (`devague <move> …`) when it is installed; the wrapper exists for
-portable resolution and the `status` helper.
+move — including `status` — is forwarded verbatim, so you can equally call the
+CLI directly (`devague <move> …`) when it is installed; the wrapper exists only
+for portable resolution.
 
 ### Moves
 
@@ -64,6 +65,7 @@ portable resolution and the `status` helper.
 | `park "<text>" --kind <kind>` | Move uncertainty into first-class open vagueness instead of forcing an answer. |
 | `converge` | Evaluate the gate; list remaining gaps. |
 | `export` | Write the buildable spec to `docs/specs/` — only after `converge` passes. |
+| `status` | Read-only: where the frame stands + the recommended next move (`--json` too). |
 | `show` / `list` | Render a frame / list frames (`--json` for raw state). |
 | `learn` / `explain <move>` | Teach the method / explain one move. |
 
@@ -84,15 +86,18 @@ per-move input/output/transition/error contract are documented in
 live shape of any move, run it with `--json` (or `devague learn --json` /
 `devague explain <move>`).
 
-### `status` — the next-move helper
-
-`status` is a wrapper-only verb (the CLI has no `status`). It reads
-`converge --json` + `list --json` and prints where the current frame stands, the
-remaining gaps, and the recommended next move. `converge --json` emits the
-structured result `{ready_for_spec, blockers, warnings, parked_items,
-required_next_moves}` (issue [#5](https://github.com/agentculture/devague/issues/5));
-the helper reads `ready_for_spec`, lists the `blockers` and `warnings`, and shows
-`required_next_moves[0]` as the recommended move — no longer deriving it itself.
+### `status` — the next-move verb
+
+`status` is a first-class, **read-only** CLI verb (`devague status`, internalised
+from this wrapper in 0.11.0 — issue
+[#30](https://github.com/agentculture/devague/issues/30)). It composes
+`list` + `converge` and prints where the current frame stands, the remaining
+gaps, and the recommended next move; it never mutates state (the
+`drafting`↔`converged` transition stays in `converge`). It reports
+`ready_for_spec`, lists the `blockers` and `warnings`, and shows
+`required_next_moves[0]` as the recommended move. Pass `--json` for the same
+fields as a structured payload (`{frame, total, ready_for_spec, blockers,
+warnings, parked_items, required_next_moves}`).
 
 ```text
 frame: my-feature    (1 frame total)

devague-0.11.1/.claude/skills/think/scripts/think.sh

@@ -0,0 +1,101 @@
+#!/usr/bin/env bash
+# think.sh — drive devague's working-backwards idea→spec engine (the /think skill).
+#
+# The skill is named `think`; the product/CLI it drives is `devague` (the spec→plan
+# half lives in the sibling /spec-to-plan skill, which drives `devague plan`).
+# devague turns a vague feature idea into a buildable spec by working backwards.
+# This wrapper is the agent-facing operator for the deterministic devague CLI:
+# it resolves the CLI portably and forwards every move verbatim — including the
+# `status` verb the CLI internalised in 0.11.0 (devague#30/#31), which reads the
+# convergence gate and names the recommended next move.
+#
+# Origin: authored and maintained in agentculture/devague. steward pulls this
+# skill from here and broadcasts it to the rest of the AgentCulture mesh, so it
+# is written to run anywhere — portable bash, no devague-checkout assumptions.
+#
+# Frames persist under .devague/ in the current directory, so run from the repo
+# you are speccing.
+
+set -euo pipefail
+
+# ── resolve the devague CLI (mesh-first, then local-dev fallback) ───────────
+DEVAGUE=()
+resolve_devague() {
+    if command -v devague >/dev/null 2>&1; then
+        DEVAGUE=(devague)            # installed tool — the normal mesh case
+        return 0
+    fi
+    # Local-dev fallback: inside the devague checkout, run via uv.
+    local dir="$PWD"
+    while [ -n "$dir" ] && [ "$dir" != "/" ]; do
+        if [ -f "$dir/pyproject.toml" ] \
+            && grep -q '^name = "devague"' "$dir/pyproject.toml" 2>/dev/null; then
+            if command -v uv >/dev/null 2>&1; then
+                DEVAGUE=(uv run devague)
+                return 0
+            fi
+            break
+        fi
+        dir=$(dirname "$dir")
+    done
+    cat >&2 <<'EOF'
+error: devague CLI not found.
+hint: install it with `uv tool install devague` (or `pipx install devague`),
+      or run from inside the devague checkout with `uv` available.
+      https://github.com/agentculture/devague
+EOF
+    return 1
+}
+
+usage() {
+    cat <<'EOF'
+think.sh — drive devague's working-backwards idea→spec engine (the /think skill).
+
+Usage:
+  think.sh <move> [args...]    forward a devague move
+  think.sh status [--frame S]  where the frame stands + the next move
+  think.sh help                this help
+
+Moves (forwarded to the devague CLI; run `devague learn` for the full method):
+  new          start a frame from the announcement ("pretend it shipped")
+  capture      record + classify a claim (--kind audience|after_state|...)
+  interrogate  pressure-test a claim (--honesty / --hard-question / --risk)
+  confirm      confirm a claim or honesty condition  (USER-only decision)
+  reject       reject a claim or honesty condition
+  park         record open vagueness instead of forcing an answer
+  converge     check whether the frame can export a spec
+  export       write the buildable spec (only after converge passes)
+  status       where the frame stands + the recommended next move
+  show / list  render a frame / list frames
+  learn        teach the method   |   explain <move>  explain one move
+
+Frames persist under .devague/ in the current directory — run from the repo
+you are speccing. Results go to stdout, diagnostics to stderr; pass --json to
+any move for structured output.
+
+Note: every move — including `status` — is forwarded verbatim to the devague
+CLI, so new devague moves work without editing this script. (`status` was
+internalised into the CLI in devague 0.11.0; it is no longer wrapper-only.)
+
+Next leg: once a frame exports a spec, hand off to the /spec-to-plan skill
+(`devague plan ...`) to turn that spec into a buildable plan.
+EOF
+}
+
+main() {
+    case "${1:-help}" in
+        help | -h | --help)
+            usage
+            return 0
+            ;;
+        *)
+            # Forward every move to the CLI verbatim (including --version, the
+            # internalised `status` verb, and any future devague move), so its
+            # own parser owns the surface.
+            resolve_devague
+            exec "${DEVAGUE[@]}" "$@"
+            ;;
+    esac
+}
+
+main "$@"

{devague-0.10.0 → devague-0.11.1}/CHANGELOG.md

@@ -5,6 +5,30 @@ All notable changes to this project will be documented in this file.
 Format follows [Keep a Changelog](https://keepachangelog.com/). This project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.11.1] - 2026-05-24
+
+### Changed
+
+- Trio skill-script header comments (`think.sh`, `spec-to-plan.sh`) no longer claim the wrapper *adds* a `status` subcommand — since 0.11.0 it is forwarded verbatim like every other move (devague#32, steward PR #58 review).
+
+### Fixed
+
+- `assign-to-workforce.sh` now installs its `mktemp` cleanup `EXIT` trap on the line immediately after creating the temp file, capturing the prior trap beforehand so the subshell-forking capture no longer sits inside the untracked-file window (devague#32).
+
+## [0.11.0] - 2026-05-24
+
+### Added
+
+- `devague status` and `devague plan status` — first-class, read-only CLI verbs that compose `list` + `converge` and report the convergence verdict, remaining gaps, and the recommended next move (`--json` too). Internalised from the `think` / `spec-to-plan` skill wrappers (#30); they never mutate state and the plan verb re-checks the live source frame for drift. Shared renderer in `devague/cli/_status.py`.
+
+### Changed
+
+- The `think` / `spec-to-plan` skill wrappers are now thin: `status` is forwarded verbatim like every other move instead of being a wrapper-only verb implemented in embedded Python. This removed their `mktemp` temp-file and stdout-ordering hazards entirely (#30, Qodo via steward).
+
+### Fixed
+
+- `assign-to-workforce.sh` no longer leaks its `mktemp` temp file if interrupted by a signal — cleanup is now registered with an `EXIT` trap (#30). Its split-plan orchestration presentation deliberately stays out of the deterministic CLI (#20).
+
 ## [0.10.0] - 2026-05-24
 
 ### Added

{devague-0.10.0 → devague-0.11.1}/CLAUDE.md

@@ -4,6 +4,16 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Status
 
+**`status` internalised into the CLI (0.11.0, #30).** The next-move helper that
+used to live as embedded Python inside the `think` / `spec-to-plan` skill
+wrappers is now a first-class, read-only CLI verb — `devague status` and
+`devague plan status` (sharing `devague/cli/_status.py`). Both compose
+`list` + `converge` and report the verdict, gaps, and recommended next move
+(`--json` too); neither mutates state. This removed the wrappers' `mktemp` +
+embedded-stdout hazards (Qodo via steward); the trio's remaining `mktemp` (in
+`assign-to-workforce.sh`, whose orchestration presentation deliberately stays
+out of the deterministic CLI) gained a cleanup trap.
+
 **Human Review Loop landed (0.6.0, #17).** `devague review` (+ `--json`) lists
 every proposed claim + honesty condition with ids — un-gated by convergence,
 never mutating state — and writes a non-authoritative artifact to
@@ -26,12 +36,12 @@ required_next_moves}` (plans: `ready_for_plan`) — a hard break from the old
 The **frame engine** (idea→spec) — Frame domain model, JSON store, convergence
 gate, renderer registry, and the flat moves `new` / `capture` / `interrogate` /
 `confirm` / `reject` / `review` / `question` / `park` / `converge` / `export` /
-`show` / `list` / `learn` / `explain`. The **plan engine** (spec→plan) is its
-structural peer:
+`status` / `show` / `list` / `learn` / `explain`. The **plan engine** (spec→plan)
+is its structural peer:
 `devague/plan.py`, `plan_convergence.py`, `plan_store.py`, `render/plan_md.py`,
 and the nested group `devague plan <move>` (`new` / `task` / `accept` / `depend`
 / `cover` / `confirm` / `reject` / `risk` / `converge` / `export` / `waves` /
-`show` / `list` / `learn` / `explain`). The two operator skills are `/think` (idea→spec,
+`status` / `show` / `list` / `learn` / `explain`). The two operator skills are `/think` (idea→spec,
 renamed from `/devague`) and `/spec-to-plan` (spec→plan). Coverage ≥ 95 %; all
 linters pass. Run `git ls-files` to see the real surface.
 
@@ -202,8 +212,9 @@ that unless the user asks otherwise. The established sibling shape is:
   split, `--json` support).
 - `devague/cli/_commands/` — one module per verb, each exposing `register()`.
   Frame verbs: `new`, `capture`, `interrogate`, `confirm`, `reject`, `park`,
-  `converge`, `export`, `show`, `list`, `learn`, `explain`. The plan engine adds
-  one module, `_commands/plan.py`, registering the nested `plan` subcommand group.
+  `converge`, `export`, `status`, `show`, `list`, `learn`, `explain` (`status`
+  shares `cli/_status.py` with the plan engine). The plan engine adds one module,
+  `_commands/plan.py`, registering the nested `plan` subcommand group.
 - Frame engine: `devague/frame.py`, `convergence.py`, `store.py`,
   `render/{spec_md,frame_md}.py`. Plan engine (its peer): `devague/plan.py`,
   `plan_convergence.py`, `plan_store.py`, `render/plan_md.py`, `cli/_plans.py`.

{devague-0.10.0 → devague-0.11.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devague
-Version: 0.10.0
+Version: 0.11.1
 Summary: devague — turns a vague feature idea into a buildable spec, then a buildable plan.
 Project-URL: Homepage, https://github.com/agentculture/devague
 Project-URL: Issues, https://github.com/agentculture/devague/issues

{devague-0.10.0 → devague-0.11.1}/devague/cli/__init__.py

@@ -69,6 +69,7 @@ def _build_parser() -> argparse.ArgumentParser:
     from devague.cli._commands import reject as _reject_cmd
     from devague.cli._commands import review as _review_cmd
     from devague.cli._commands import show as _show_cmd
+    from devague.cli._commands import status as _status_cmd
 
     _learn_cmd.register(sub)
     _explain_cmd.register(sub)
@@ -83,6 +84,7 @@ def _build_parser() -> argparse.ArgumentParser:
     _converge_cmd.register(sub)
     _export_cmd.register(sub)
     _plan_cmd.register(sub)
+    _status_cmd.register(sub)
     _show_cmd.register(sub)
     _list_cmd.register(sub)
 

{devague-0.10.0 → devague-0.11.1}/devague/cli/_commands/learn.py

@@ -16,6 +16,7 @@ MOVES = {
     "park": "Move uncertainty into first-class open vagueness instead of forcing an answer.",
     "converge": "Check whether the frame is solid enough to export a spec.",
     "export": "Write the buildable spec — only once the frame converges.",
+    "status": "Report where the frame stands + the recommended next move (read-only).",
     "show": "Render the Announcement Frame.",
     "list": "List frames.",
 }

{devague-0.10.0 → devague-0.11.1}/devague/cli/_commands/plan.py

@@ -21,6 +21,7 @@ from devague.cli._frames import resolve as resolve_frame
 from devague.cli._output import emit_result
 from devague.cli._paths import dated_name
 from devague.cli._plans import resolve_plan
+from devague.cli._status import StatusLabels, emit_empty, emit_status
 from devague.convergence import evaluate as evaluate_frame
 from devague.frame import Frame
 from devague.plan import RISK_KINDS, Plan, dependency_waves, targets_from_frame, to_dict
@@ -46,10 +47,22 @@ PLAN_MOVES = {
     "converge": "Check whether the plan can export, against the live frame.",
     "export": "Write the buildable plan — only once the plan converges.",
     "waves": "Emit deterministic dependency waves (scheduling metadata, not orchestration).",
+    "status": "Report where the plan stands + the recommended next move (read-only).",
     "show": "Render the plan.",
     "list": "List plans.",
 }
 
+_STATUS_LABELS = StatusLabels(
+    noun="plan",
+    ready_key="ready_for_plan",
+    export_move="devague plan export   # write the buildable plan",
+    empty_text=(
+        "no plans yet — seed one from a converged frame:\n"
+        '  devague plan new --frame "<slug>"\n'
+        "  (the frame must have converged in the /think skill first)"
+    ),
+)
+
 
 # ── shared helpers ──────────────────────────────────────────────────────────
 def _load_source_frame(slug: str) -> Frame:
@@ -319,6 +332,31 @@ def cmd_plan_waves(args: argparse.Namespace) -> int:
     return 0
 
 
+def cmd_plan_status(args: argparse.Namespace) -> int:
+    """Where the plan stands + the recommended next move — read-only.
+
+    Re-evaluates against the **live** source frame (like ``converge``/``export``),
+    so frame drift surfaces as a real error on stderr before any stdout. Internalised
+    from the ``spec-to-plan`` skill wrapper (issue #30); unlike ``converge`` it never
+    persists the ``drafting``↔``converged`` transition.
+    """
+    json_mode = getattr(args, "json", False)
+    slugs = plan_store.list_slugs()
+    if not slugs:
+        emit_empty(_STATUS_LABELS, json_mode=json_mode)
+    else:
+        # resolve_plan + _live raise here (before any stdout) on a bad --plan or a
+        # source frame that regressed below convergence — routed to stderr.
+        plan = resolve_plan(args.plan)
+        _frame, targets = _live(plan)
+        plan.targets = targets  # in-memory refresh only; status does not save
+        result = evaluate_plan(plan, targets=targets)
+        emit_status(
+            _STATUS_LABELS, selected=plan.slug, total=len(slugs), result=result, json_mode=json_mode
+        )
+    return 0
+
+
 def cmd_plan_show(args: argparse.Namespace) -> int:
     plan = resolve_plan(args.plan)
     if getattr(args, "json", False):
@@ -465,6 +503,10 @@ def register(sub: argparse._SubParsersAction) -> None:
     _plan_opt(pwv)
     pwv.set_defaults(func=cmd_plan_waves)
 
+    pst = psub.add_parser("status", help="Where the plan stands + the recommended next move.")
+    _plan_opt(pst)
+    pst.set_defaults(func=cmd_plan_status)
+
     psh = psub.add_parser("show", help="Render the plan.")
     _plan_opt(psh)
     psh.set_defaults(func=cmd_plan_show)

devague-0.11.1/devague/cli/_commands/status.py

@@ -0,0 +1,53 @@
+"""``devague status`` — where the frame stands + the recommended next move.
+
+A read-only value-add verb that composes ``list`` and ``converge``: it reports
+the selected frame, the convergence verdict (blockers and warnings), and, when
+not converged, the next move for the first gap. This logic used to live in the
+``think`` skill wrapper's embedded Python (issue #30); internalising it makes it
+deterministic and unit-testable and removes the wrapper's temp-file +
+stdout-ordering hazards. ``status`` never mutates state — like ``review`` it only
+reports (the ``drafting``↔``converged`` transition stays in ``converge``).
+"""
+
+from __future__ import annotations
+
+import argparse
+
+from devague import store
+from devague.cli._frames import resolve
+from devague.cli._status import StatusLabels, emit_empty, emit_status
+from devague.convergence import evaluate
+
+_LABELS = StatusLabels(
+    noun="frame",
+    ready_key="ready_for_spec",
+    export_move="devague export   # write the buildable spec",
+    empty_text=(
+        "no frames yet — start one:\n"
+        '  devague new "<announcement>"\n'
+        "  first question: \"What's the announcement? Pretend this shipped"
+        ' successfully — what would you announce?"'
+    ),
+)
+
+
+def cmd_status(args: argparse.Namespace) -> int:
+    json_mode = getattr(args, "json", False)
+    slugs = store.list_slugs()
+    if not slugs:
+        emit_empty(_LABELS, json_mode=json_mode)
+    else:
+        # A bad --frame raises here (before any stdout) so the error reaches stderr.
+        frame = resolve(args.frame)
+        result = evaluate(frame)
+        emit_status(
+            _LABELS, selected=frame.slug, total=len(slugs), result=result, json_mode=json_mode
+        )
+    return 0
+
+
+def register(sub: argparse._SubParsersAction) -> None:
+    p = sub.add_parser("status", help="Where the frame stands + the recommended next move.")
+    p.add_argument("--frame", help="Frame slug (default: current).")
+    p.add_argument("--json", action="store_true", help="Emit structured JSON.")
+    p.set_defaults(func=cmd_status)