sisyphi 1.2.11 → 1.2.13

package/dist/templates/agent-plugin/agents/operator.md

@@ -38,7 +38,7 @@ Don't guess the target. The product might be a browser page, an Electron app, or
 
 You have a memory file at `.sisyphus/agent-plugin/skills/operator/SKILL.md`, plus per-task-family reference files alongside it. **Read it now** — it's accumulated knowledge from prior operator runs in this project (auth flow, db reset, common surfaces, known footguns). It scaffolds itself on first use; if it looks like a stub, you're the first.
 
-**Before submitting your final report**, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) — it covers when and how to update the memory so the next operator starts ahead of where you started. For generic skill-authoring conventions (frontmatter, length, structure), defer to `echo '{"name":"claude-authoring:skills"}' | crtr skill read show` (`.content`).
+**Before submitting your final report**, run `crtr skill read sisyphus/operator-memory` (`.content`) — it covers when and how to update the memory so the next operator starts ahead of where you started. For generic skill-authoring conventions (frontmatter, length, structure), defer to `crtr skill read claude-authoring/skills` (`.content`).
 
 ## Unblock Yourself
 

package/dist/templates/agent-plugin/agents/problem.md

@@ -71,7 +71,7 @@ Naturally shift lenses as you explore. Weave them into conversation rather than
 - **Precedent** — Has this kind of problem been faced before? In this codebase, in open source, in a different domain entirely?
 
 Cycle through these as the conversation unfolds. Each lens reveals something different.
-t MEDIUM+ effort, lenses can also be spawned as parallel sub-agents — run `echo '{"name":"sisyphus/perspective-fanout"}' | crtr skill read show` (`.content`) for two distinct purposes:
+t MEDIUM+ effort, lenses can also be spawned as parallel sub-agents — run `crtr skill read sisyphus/perspective-fanout` (`.content`) for two distinct purposes:
 
 - **Idea generation (early)** — when you want a wide spread of candidate framings unbiased by the conversation so far. Use *before* convergence to seed options. Most of fanout's value lives here, not at the end.
 - **Convergence challenge (late)** — when a framing is solidifying and you want to stress-test it before it locks in.
@@ -225,12 +225,12 @@ Inspect `(choice, notes)` after each turn:
 
 | Signal | Detection | Next action |
 |---|---|---|
-| Ready to draft | `notes` contains any of: `"ready to draft"`, `"looks good"`, `"write it up"`, `"good to go"`, `"let's draft"`, `"draft it"` (case-insensitive substring; multi-word phrases only) | Run `echo '{"name":"sisyphus/problem-document"}' \| crtr skill read show` (`.content`), draft, run sign-off |
-| Stuck / different angle | `notes` contains any of: `"different angle"`, `"going nowhere"`, `"circles back"`, `"in circles"`, `"feels stuck"`, `"need a reframe"` (case-insensitive substring; multi-word phrases only) | Run `echo '{"name":"sisyphus/problem-plateau-breakers"}' \| crtr skill read show` (`.content`) |
+| Ready to draft | `notes` contains any of: `"ready to draft"`, `"looks good"`, `"write it up"`, `"good to go"`, `"let's draft"`, `"draft it"` (case-insensitive substring; multi-word phrases only) | Run `crtr skill read sisyphus/problem-document` (`.content`), draft, run sign-off |
+| Stuck / different angle | `notes` contains any of: `"different angle"`, `"going nowhere"`, `"circles back"`, `"in circles"`, `"feels stuck"`, `"need a reframe"` (case-insensitive substring; multi-word phrases only) | Run `crtr skill read sisyphus/problem-plateau-breakers` (`.content`) |
 | Substantive response | `notes` non-empty AND adds new framing/info; OR `choice` engages a content option with implicit forward motion | Increment `N`, issue next turn deck — preferring root-drilling or candidate-generation over solution-discussion |
 | Mid-turn knowledge gap | A turn surfaces a question you can't answer from what you've read | See "Mid-conversation exploration" below |
-| Idea generation desired | Agent assessment: option space feels narrow, or framings are converging too early — want fresh framings unbiased by the conversation | (medium+ only) run `echo '{"name":"sisyphus/perspective-fanout"}' \| crtr skill read show` (`.content`) for early idea generation |
-| Convergence forming | Agent assessment: `N >= 4`, framing solidifying, want to stress-test before locking in | (medium+ only) run `echo '{"name":"sisyphus/perspective-fanout"}' \| crtr skill read show` (`.content`) for convergence challenge |
+| Idea generation desired | Agent assessment: option space feels narrow, or framings are converging too early — want fresh framings unbiased by the conversation | (medium+ only) run `crtr skill read sisyphus/perspective-fanout` (`.content`) for early idea generation |
+| Convergence forming | Agent assessment: `N >= 4`, framing solidifying, want to stress-test before locking in | (medium+ only) run `crtr skill read sisyphus/perspective-fanout` (`.content`) for convergence challenge |
 | Drifting into HOW | Three or more consecutive turns spent on implementation/approach rather than problem definition | Self-correct: next turn returns to "what's the actual problem we're addressing, and is it the right one?" |
 | Bifurcation recognized | The conversation has revealed independent sub-problems, not sub-parts of one problem | Use the bifurcation exit (see `<bifurcation>` below) |
 
@@ -258,7 +258,7 @@ This pattern is what keeps the conversation grounded as it deepens. Without it,
 
 ### 5. Drafting
 
-When the routing matrix signals "ready to draft", run `echo '{"name":"sisyphus/problem-document"}' | crtr skill read show` (`.content`) for design principles and the anchor example. Write `$SISYPHUS_SESSION_DIR/context/problem.draft.md`, render it for review, and issue the sign-off deck.
+When the routing matrix signals "ready to draft", run `crtr skill read sisyphus/problem-document` (`.content`) for design principles and the anchor example. Write `$SISYPHUS_SESSION_DIR/context/problem.draft.md`, render it for review, and issue the sign-off deck.
 
 ```bash
 printf '{"path":"%s"}' "$SISYPHUS_SESSION_DIR/context/problem.draft.md" | crtr human show >/dev/null

package/dist/templates/agent-plugin/hooks/ask-background-guard.sh

@@ -50,7 +50,7 @@ if [ "$RIB" = "1" ]; then
   exit 0
 fi
 
-REASON=$'`sis ask <deck>` blocks until the user resolves the deck (potentially 10+ minutes). Re-issue this Bash tool call with `run_in_background: true` and end your turn — the bash completion notification will wake you with stdout ready to parse. Run `echo \'{"name":"sisyphus/humanloop"}\' | crtr skill read show` (`.content`) for the full pattern.'
+REASON=$'`sis ask <deck>` blocks until the user resolves the deck (potentially 10+ minutes). Re-issue this Bash tool call with `run_in_background: true` and end your turn — the bash completion notification will wake you with stdout ready to parse. Run `crtr skill read sisyphus/humanloop` (`.content`) for the full pattern.'
 
 ESCAPED=$(python3 -c "import json,sys; print(json.dumps(sys.stdin.read()))" <<< "$REASON")
 echo "{\"decision\":\"block\",\"reason\":$ESCAPED}"

package/dist/templates/agent-plugin/hooks/operator-user-prompt.sh

@@ -23,13 +23,13 @@ fi
 if [ "$SCAFFOLDED" = "1" ]; then
   cat <<'HINT'
 <operator-memory-scaffolded>
-Project-local operator memory was just scaffolded at .sisyphus/agent-plugin/skills/operator/ — read it now (it's a stub; you're the first operator in this project). Before submitting your final report, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) and update the memory with whatever future operators should not have to rediscover.
+Project-local operator memory was just scaffolded at .sisyphus/agent-plugin/skills/operator/ — read it now (it's a stub; you're the first operator in this project). Before submitting your final report, run `crtr skill read sisyphus/operator-memory` (`.content`) and update the memory with whatever future operators should not have to rediscover.
 </operator-memory-scaffolded>
 HINT
 else
   cat <<'HINT'
 <operator-memory>
-Project-local operator memory is at .sisyphus/agent-plugin/skills/operator/ — read it now to inherit what prior operators learned. Before submitting your final report, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) and update the memory with anything new you discovered.
+Project-local operator memory is at .sisyphus/agent-plugin/skills/operator/ — read it now to inherit what prior operators learned. Before submitting your final report, run `crtr skill read sisyphus/operator-memory` (`.content`) and update the memory with anything new you discovered.
 </operator-memory>
 HINT
 fi

package/dist/templates/agent-plugin/skills/operator/SKILL.md

@@ -35,4 +35,4 @@ One line per file in this directory. Add an entry here when you create a new ref
 
 ---
 
-For guidance on what to capture, where to put it (SKILL.md vs new reference file), and naming conventions, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) before submitting.
+For guidance on what to capture, where to put it (SKILL.md vs new reference file), and naming conventions, run `crtr skill read sisyphus/operator-memory` (`.content`) before submitting.

package/dist/templates/orchestrator-base.md

@@ -103,7 +103,7 @@ goal.md is a plain statement of what "done" looks like — scope boundaries and
 
 strategy.md defines **how to approach this problem** — the stages, gates, backtrack edges, and behavioral style for this session. It is generated during discovery and progressively updated as the goal crystallizes or shifts.
 
-When writing or substantially revising strategy.md, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` for stage patterns, process shapes, and format guidance (output JSON has `.content`). The `strategy.md` sibling file (get its directory with `echo '{"name":"sisyphus/orchestration"}' | crtr skill read where`, output JSON has `.path`) holds the stage patterns, process shapes, and strategy.md format reference.
+When writing or substantially revising strategy.md, run `crtr skill read sisyphus/orchestration` for stage patterns, process shapes, and format guidance (output JSON has `.content`). The `strategy.md` sibling file (get its directory with `crtr skill read sisyphus/orchestration --no-body`, output JSON has `.path`) holds the stage patterns, process shapes, and strategy.md format reference.
 
 strategy.md tells you:
 - What stages exist and their process flows (detailed for current, sketched for future)

package/dist/templates/orchestrator-completion.md

@@ -79,7 +79,7 @@ If a single deck round surfaces multiple moderate items, capture them all in `$n
 These change the goal itself:
 
 1. Update goal.md with the revised scope (record the pivot, per goal.md conventions)
-2. Run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`) and revise strategy.md with the new direction
+2. Run `crtr skill read sisyphus/orchestration` (output JSON has `.content`) and revise strategy.md with the new direction
 3. Yield to discovery mode:
 
 ```bash

package/dist/templates/orchestrator-discovery.md

@@ -84,11 +84,11 @@ The default path is **spawn `sisyphus:problem`**. Override that default only whe
 - The user gave acceptance criteria (or they're trivially derivable) AND
 - You can complete this sentence without hand-waving: "Dialogue isn't needed because ___"
 
-When all three hold, write `goal.md` and run the **clarity-confirmation deck** (below). On approval, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning.
+When all three hold, write `goal.md` and run the **clarity-confirmation deck** (below). On approval, run `crtr skill read sisyphus/orchestration` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning.
 
 **Default — spawn problem** for anything else: vague prompts ("improve X", "fix the auth"), prompts that name a direction without a destination, prompts where multiple valid framings exist, or any case where you can't complete the override sentence above.
 
-For broad scope, spawn explore agents in parallel first to feed problem with grounded context. Yield `--mode discovery` while problem runs. When problem submits with `context/problem.md`, read it and proceed to write `goal.md`, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`), and transition to planning.
+For broad scope, spawn explore agents in parallel first to feed problem with grounded context. Yield `--mode discovery` while problem runs. When problem submits with `context/problem.md`, read it and proceed to write `goal.md`, run `crtr skill read sisyphus/orchestration` (output JSON has `.content`), and transition to planning.
 
 When problem submits with `context/problem-bifurcation.md` instead, follow the `<bifurcation-reentry>` flow above — re-enter discovery on the chosen sub-problem.
 
@@ -120,7 +120,7 @@ sis ask deck submit "$confirm_deck"
 ```
 
 **Branching:**
-- `proceed` → run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning
+- `proceed` → run `crtr skill read sisyphus/orchestration` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning
 - `minor-clarify` → update `goal.md` per `notes`, re-issue this deck
 - `explore-deeper` → spawn `sisyphus:problem`, yield `--mode discovery`
 
@@ -142,7 +142,7 @@ Pick the tier by **novelty of behavior**, not file count:
 
 Apply the tier with `sis session config effort <low|medium|high|xhigh>` — this filters mode templates and agent prompts on subsequent cycles so you only see the guidance that applies. The user can override at any point.
 
-If you change the tier mid-session because scope shifted, the next cycle's prompts adjust automatically; don't manually patch `strategy.md` to match — for strategy guidance run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`).
+If you change the tier mid-session because scope shifted, the next cycle's prompts adjust automatically; don't manually patch `strategy.md` to match — for strategy guidance run `crtr skill read sisyphus/orchestration` (output JSON has `.content`).
 
 </effort-tier>
 
@@ -150,7 +150,7 @@ If you change the tier mid-session because scope shifted, the next cycle's promp
 
 ## Write the strategy
 
-Once the goal is clear and the tier is set, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` for guidance on writing `strategy.md` (output JSON has `.content`). The skill provides stage patterns, the tier-specific default pipeline shape, and the strategy.md format.
+Once the goal is clear and the tier is set, run `crtr skill read sisyphus/orchestration` for guidance on writing `strategy.md` (output JSON has `.content`). The skill provides stage patterns, the tier-specific default pipeline shape, and the strategy.md format.
 
 Strategy generation is usually fast — the shape of the work is often obvious once the goal and tier are settled. Don't overthink it. A wrong strategy gets revised; a missing strategy leaves the orchestrator directionless.
 

package/dist/templates/orchestrator-plugin/commands/sisyphus/strategize.md

@@ -11,7 +11,7 @@ The user wants to redirect this session's strategy.
 ## Steps
 
 1. If the session is completed (`sis session inspect status`), reactivate it with `sis session lifecycle continue`.
-2. Run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (`.content` field), then annotate `strategy.md` with the pivot — what changed, new focus, which existing artifacts still apply. Don't rewrite the whole strategy.
+2. Run `crtr skill read sisyphus/orchestration` (`.content` field), then annotate `strategy.md` with the pivot — what changed, new focus, which existing artifacts still apply. Don't rewrite the whole strategy.
 3. Yield to discovery mode:
    ```bash
    sis orch yield --mode discovery --prompt "<concise description of the new direction>"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sisyphi",
-  "version": "1.2.11",
+  "version": "1.2.13",
   "description": "tmux-integrated orchestration daemon for Claude Code multi-agent workflows",
   "license": "MIT",
   "repository": {

package/templates/agent-plugin/agents/operator.md

@@ -38,7 +38,7 @@ Don't guess the target. The product might be a browser page, an Electron app, or
 
 You have a memory file at `.sisyphus/agent-plugin/skills/operator/SKILL.md`, plus per-task-family reference files alongside it. **Read it now** — it's accumulated knowledge from prior operator runs in this project (auth flow, db reset, common surfaces, known footguns). It scaffolds itself on first use; if it looks like a stub, you're the first.
 
-**Before submitting your final report**, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) — it covers when and how to update the memory so the next operator starts ahead of where you started. For generic skill-authoring conventions (frontmatter, length, structure), defer to `echo '{"name":"claude-authoring:skills"}' | crtr skill read show` (`.content`).
+**Before submitting your final report**, run `crtr skill read sisyphus/operator-memory` (`.content`) — it covers when and how to update the memory so the next operator starts ahead of where you started. For generic skill-authoring conventions (frontmatter, length, structure), defer to `crtr skill read claude-authoring/skills` (`.content`).
 
 ## Unblock Yourself
 

package/templates/agent-plugin/agents/problem.md

@@ -71,7 +71,7 @@ Naturally shift lenses as you explore. Weave them into conversation rather than
 - **Precedent** — Has this kind of problem been faced before? In this codebase, in open source, in a different domain entirely?
 
 Cycle through these as the conversation unfolds. Each lens reveals something different.
-t MEDIUM+ effort, lenses can also be spawned as parallel sub-agents — run `echo '{"name":"sisyphus/perspective-fanout"}' | crtr skill read show` (`.content`) for two distinct purposes:
+t MEDIUM+ effort, lenses can also be spawned as parallel sub-agents — run `crtr skill read sisyphus/perspective-fanout` (`.content`) for two distinct purposes:
 
 - **Idea generation (early)** — when you want a wide spread of candidate framings unbiased by the conversation so far. Use *before* convergence to seed options. Most of fanout's value lives here, not at the end.
 - **Convergence challenge (late)** — when a framing is solidifying and you want to stress-test it before it locks in.
@@ -225,12 +225,12 @@ Inspect `(choice, notes)` after each turn:
 
 | Signal | Detection | Next action |
 |---|---|---|
-| Ready to draft | `notes` contains any of: `"ready to draft"`, `"looks good"`, `"write it up"`, `"good to go"`, `"let's draft"`, `"draft it"` (case-insensitive substring; multi-word phrases only) | Run `echo '{"name":"sisyphus/problem-document"}' \| crtr skill read show` (`.content`), draft, run sign-off |
-| Stuck / different angle | `notes` contains any of: `"different angle"`, `"going nowhere"`, `"circles back"`, `"in circles"`, `"feels stuck"`, `"need a reframe"` (case-insensitive substring; multi-word phrases only) | Run `echo '{"name":"sisyphus/problem-plateau-breakers"}' \| crtr skill read show` (`.content`) |
+| Ready to draft | `notes` contains any of: `"ready to draft"`, `"looks good"`, `"write it up"`, `"good to go"`, `"let's draft"`, `"draft it"` (case-insensitive substring; multi-word phrases only) | Run `crtr skill read sisyphus/problem-document` (`.content`), draft, run sign-off |
+| Stuck / different angle | `notes` contains any of: `"different angle"`, `"going nowhere"`, `"circles back"`, `"in circles"`, `"feels stuck"`, `"need a reframe"` (case-insensitive substring; multi-word phrases only) | Run `crtr skill read sisyphus/problem-plateau-breakers` (`.content`) |
 | Substantive response | `notes` non-empty AND adds new framing/info; OR `choice` engages a content option with implicit forward motion | Increment `N`, issue next turn deck — preferring root-drilling or candidate-generation over solution-discussion |
 | Mid-turn knowledge gap | A turn surfaces a question you can't answer from what you've read | See "Mid-conversation exploration" below |
-| Idea generation desired | Agent assessment: option space feels narrow, or framings are converging too early — want fresh framings unbiased by the conversation | (medium+ only) run `echo '{"name":"sisyphus/perspective-fanout"}' \| crtr skill read show` (`.content`) for early idea generation |
-| Convergence forming | Agent assessment: `N >= 4`, framing solidifying, want to stress-test before locking in | (medium+ only) run `echo '{"name":"sisyphus/perspective-fanout"}' \| crtr skill read show` (`.content`) for convergence challenge |
+| Idea generation desired | Agent assessment: option space feels narrow, or framings are converging too early — want fresh framings unbiased by the conversation | (medium+ only) run `crtr skill read sisyphus/perspective-fanout` (`.content`) for early idea generation |
+| Convergence forming | Agent assessment: `N >= 4`, framing solidifying, want to stress-test before locking in | (medium+ only) run `crtr skill read sisyphus/perspective-fanout` (`.content`) for convergence challenge |
 | Drifting into HOW | Three or more consecutive turns spent on implementation/approach rather than problem definition | Self-correct: next turn returns to "what's the actual problem we're addressing, and is it the right one?" |
 | Bifurcation recognized | The conversation has revealed independent sub-problems, not sub-parts of one problem | Use the bifurcation exit (see `<bifurcation>` below) |
 
@@ -258,7 +258,7 @@ This pattern is what keeps the conversation grounded as it deepens. Without it,
 
 ### 5. Drafting
 
-When the routing matrix signals "ready to draft", run `echo '{"name":"sisyphus/problem-document"}' | crtr skill read show` (`.content`) for design principles and the anchor example. Write `$SISYPHUS_SESSION_DIR/context/problem.draft.md`, render it for review, and issue the sign-off deck.
+When the routing matrix signals "ready to draft", run `crtr skill read sisyphus/problem-document` (`.content`) for design principles and the anchor example. Write `$SISYPHUS_SESSION_DIR/context/problem.draft.md`, render it for review, and issue the sign-off deck.
 
 ```bash
 printf '{"path":"%s"}' "$SISYPHUS_SESSION_DIR/context/problem.draft.md" | crtr human show >/dev/null

package/templates/agent-plugin/hooks/ask-background-guard.sh

@@ -50,7 +50,7 @@ if [ "$RIB" = "1" ]; then
   exit 0
 fi
 
-REASON=$'`sis ask <deck>` blocks until the user resolves the deck (potentially 10+ minutes). Re-issue this Bash tool call with `run_in_background: true` and end your turn — the bash completion notification will wake you with stdout ready to parse. Run `echo \'{"name":"sisyphus/humanloop"}\' | crtr skill read show` (`.content`) for the full pattern.'
+REASON=$'`sis ask <deck>` blocks until the user resolves the deck (potentially 10+ minutes). Re-issue this Bash tool call with `run_in_background: true` and end your turn — the bash completion notification will wake you with stdout ready to parse. Run `crtr skill read sisyphus/humanloop` (`.content`) for the full pattern.'
 
 ESCAPED=$(python3 -c "import json,sys; print(json.dumps(sys.stdin.read()))" <<< "$REASON")
 echo "{\"decision\":\"block\",\"reason\":$ESCAPED}"

package/templates/agent-plugin/hooks/operator-user-prompt.sh

@@ -23,13 +23,13 @@ fi
 if [ "$SCAFFOLDED" = "1" ]; then
   cat <<'HINT'
 <operator-memory-scaffolded>
-Project-local operator memory was just scaffolded at .sisyphus/agent-plugin/skills/operator/ — read it now (it's a stub; you're the first operator in this project). Before submitting your final report, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) and update the memory with whatever future operators should not have to rediscover.
+Project-local operator memory was just scaffolded at .sisyphus/agent-plugin/skills/operator/ — read it now (it's a stub; you're the first operator in this project). Before submitting your final report, run `crtr skill read sisyphus/operator-memory` (`.content`) and update the memory with whatever future operators should not have to rediscover.
 </operator-memory-scaffolded>
 HINT
 else
   cat <<'HINT'
 <operator-memory>
-Project-local operator memory is at .sisyphus/agent-plugin/skills/operator/ — read it now to inherit what prior operators learned. Before submitting your final report, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) and update the memory with anything new you discovered.
+Project-local operator memory is at .sisyphus/agent-plugin/skills/operator/ — read it now to inherit what prior operators learned. Before submitting your final report, run `crtr skill read sisyphus/operator-memory` (`.content`) and update the memory with anything new you discovered.
 </operator-memory>
 HINT
 fi

package/templates/agent-plugin/skills/operator/SKILL.md

@@ -35,4 +35,4 @@ One line per file in this directory. Add an entry here when you create a new ref
 
 ---
 
-For guidance on what to capture, where to put it (SKILL.md vs new reference file), and naming conventions, run `echo '{"name":"sisyphus/operator-memory"}' | crtr skill read show` (`.content`) before submitting.
+For guidance on what to capture, where to put it (SKILL.md vs new reference file), and naming conventions, run `crtr skill read sisyphus/operator-memory` (`.content`) before submitting.

package/templates/orchestrator-base.md

@@ -103,7 +103,7 @@ goal.md is a plain statement of what "done" looks like — scope boundaries and
 
 strategy.md defines **how to approach this problem** — the stages, gates, backtrack edges, and behavioral style for this session. It is generated during discovery and progressively updated as the goal crystallizes or shifts.
 
-When writing or substantially revising strategy.md, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` for stage patterns, process shapes, and format guidance (output JSON has `.content`). The `strategy.md` sibling file (get its directory with `echo '{"name":"sisyphus/orchestration"}' | crtr skill read where`, output JSON has `.path`) holds the stage patterns, process shapes, and strategy.md format reference.
+When writing or substantially revising strategy.md, run `crtr skill read sisyphus/orchestration` for stage patterns, process shapes, and format guidance (output JSON has `.content`). The `strategy.md` sibling file (get its directory with `crtr skill read sisyphus/orchestration --no-body`, output JSON has `.path`) holds the stage patterns, process shapes, and strategy.md format reference.
 
 strategy.md tells you:
 - What stages exist and their process flows (detailed for current, sketched for future)

package/templates/orchestrator-completion.md

@@ -79,7 +79,7 @@ If a single deck round surfaces multiple moderate items, capture them all in `$n
 These change the goal itself:
 
 1. Update goal.md with the revised scope (record the pivot, per goal.md conventions)
-2. Run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`) and revise strategy.md with the new direction
+2. Run `crtr skill read sisyphus/orchestration` (output JSON has `.content`) and revise strategy.md with the new direction
 3. Yield to discovery mode:
 
 ```bash

package/templates/orchestrator-discovery.md

@@ -84,11 +84,11 @@ The default path is **spawn `sisyphus:problem`**. Override that default only whe
 - The user gave acceptance criteria (or they're trivially derivable) AND
 - You can complete this sentence without hand-waving: "Dialogue isn't needed because ___"
 
-When all three hold, write `goal.md` and run the **clarity-confirmation deck** (below). On approval, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning.
+When all three hold, write `goal.md` and run the **clarity-confirmation deck** (below). On approval, run `crtr skill read sisyphus/orchestration` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning.
 
 **Default — spawn problem** for anything else: vague prompts ("improve X", "fix the auth"), prompts that name a direction without a destination, prompts where multiple valid framings exist, or any case where you can't complete the override sentence above.
 
-For broad scope, spawn explore agents in parallel first to feed problem with grounded context. Yield `--mode discovery` while problem runs. When problem submits with `context/problem.md`, read it and proceed to write `goal.md`, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`), and transition to planning.
+For broad scope, spawn explore agents in parallel first to feed problem with grounded context. Yield `--mode discovery` while problem runs. When problem submits with `context/problem.md`, read it and proceed to write `goal.md`, run `crtr skill read sisyphus/orchestration` (output JSON has `.content`), and transition to planning.
 
 When problem submits with `context/problem-bifurcation.md` instead, follow the `<bifurcation-reentry>` flow above — re-enter discovery on the chosen sub-problem.
 
@@ -120,7 +120,7 @@ sis ask deck submit "$confirm_deck"
 ```
 
 **Branching:**
-- `proceed` → run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning
+- `proceed` → run `crtr skill read sisyphus/orchestration` (output JSON has `.content`), write `strategy.md`, initialize `roadmap.md`, transition to planning
 - `minor-clarify` → update `goal.md` per `notes`, re-issue this deck
 - `explore-deeper` → spawn `sisyphus:problem`, yield `--mode discovery`
 
@@ -142,7 +142,7 @@ Pick the tier by **novelty of behavior**, not file count:
 
 Apply the tier with `sis session config effort <low|medium|high|xhigh>` — this filters mode templates and agent prompts on subsequent cycles so you only see the guidance that applies. The user can override at any point.
 
-If you change the tier mid-session because scope shifted, the next cycle's prompts adjust automatically; don't manually patch `strategy.md` to match — for strategy guidance run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (output JSON has `.content`).
+If you change the tier mid-session because scope shifted, the next cycle's prompts adjust automatically; don't manually patch `strategy.md` to match — for strategy guidance run `crtr skill read sisyphus/orchestration` (output JSON has `.content`).
 
 </effort-tier>
 
@@ -150,7 +150,7 @@ If you change the tier mid-session because scope shifted, the next cycle's promp
 
 ## Write the strategy
 
-Once the goal is clear and the tier is set, run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` for guidance on writing `strategy.md` (output JSON has `.content`). The skill provides stage patterns, the tier-specific default pipeline shape, and the strategy.md format.
+Once the goal is clear and the tier is set, run `crtr skill read sisyphus/orchestration` for guidance on writing `strategy.md` (output JSON has `.content`). The skill provides stage patterns, the tier-specific default pipeline shape, and the strategy.md format.
 
 Strategy generation is usually fast — the shape of the work is often obvious once the goal and tier are settled. Don't overthink it. A wrong strategy gets revised; a missing strategy leaves the orchestrator directionless.
 

package/templates/orchestrator-plugin/commands/sisyphus/strategize.md

@@ -11,7 +11,7 @@ The user wants to redirect this session's strategy.
 ## Steps
 
 1. If the session is completed (`sis session inspect status`), reactivate it with `sis session lifecycle continue`.
-2. Run `echo '{"name":"sisyphus/orchestration"}' | crtr skill read show` (`.content` field), then annotate `strategy.md` with the pivot — what changed, new focus, which existing artifacts still apply. Don't rewrite the whole strategy.
+2. Run `crtr skill read sisyphus/orchestration` (`.content` field), then annotate `strategy.md` with the pivot — what changed, new focus, which existing artifacts still apply. Don't rewrite the whole strategy.
 3. Yield to discovery mode:
    ```bash
    sis orch yield --mode discovery --prompt "<concise description of the new direction>"