@mindrian_os/install 1.13.0-beta.13 → 1.13.0-beta.14

package/commands/act.md

@@ -4,6 +4,7 @@ description: Run Larry's best-pick methodology for your room state
 argument-hint: '[--chain] [--swarm] [--dry-run]'
 body_shape: E (Action Report)
 serves_jtbd: ["plan-execution"]
+teaching: "When you have analyses on the table but no clear next step, /mos:act picks the best-fit methodology for your current room state and runs it. Saves you from analysis paralysis."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: meta
 frameworks: []

package/commands/admin.md

@@ -4,6 +4,7 @@ description: Manage Brain API keys from the admin panel
 argument-hint: [subcommand]
 body_shape: A (Mondrian Board)
 serves_jtbd: ["audit-room"]
+teaching: "When you need to inspect or rotate Brain API keys, /mos:admin opens the admin panel. Read-only by default; rotation is gated behind a confirm prompt."
 ui_reference: skills/ui-system/SKILL.md
 visibility: admin
 allowed-tools:

package/commands/analyze-needs.md

@@ -2,6 +2,7 @@
 name: analyze-needs
 description: Score customer jobs with importance and satisfaction
 serves_jtbd: ["find-problem"]
+teaching: "When you need to know which customer jobs matter most, /mos:analyze-needs scores them by importance versus satisfaction. Best after you have a customer segment defined."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Jobs to Be Done (JTBD)"]

package/commands/analyze-systems.md

@@ -2,6 +2,7 @@
 name: analyze-systems
 description: Decompose a system into layers and leverage points
 serves_jtbd: ["find-bottleneck"]
+teaching: "When you need to find where leverage lives in a complex system, /mos:analyze-systems decomposes it into layers and surfaces the leverage points. Best when symptoms keep recurring."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Systems Thinking"]

package/commands/analyze-timing.md

@@ -2,6 +2,7 @@
 name: analyze-timing
 description: Place a technology on the S-Curve timing clock
 serves_jtbd: ["understand-market"]
+teaching: "When you need to know if your technology is too early, too late, or right on time, /mos:analyze-timing places it on the S-Curve. Best before you commit to a launch window."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["S-Curve Analysis"]

package/commands/auto-explore.md

@@ -2,6 +2,7 @@
 description: "Manually trigger auto-explore on a specific file (Desktop fallback when PostToolUse hook does not fire per RESEARCH 4.8)"
 argument-hint: "<file_path>"
 serves_jtbd: ["find-problem", "understand-market", "explore"]
+teaching: "In the moment a new artifact lands, /mos:auto-explore kicks off the same domain decomposition the PostToolUse hook would run. Use it on Desktop when the hook does not fire."
 allowed-tools:
   - "Bash"
   - "Read"

package/commands/beautiful-question.md

@@ -2,6 +2,7 @@
 name: beautiful-question
 description: Reframe a challenge as Why / What-if / How
 serves_jtbd: ["find-problem", "explore"]
+teaching: "When the framing feels stuck, /mos:beautiful-question reshapes the challenge as Why / What-if / How. The right question unlocks more progress than a better answer."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Beautiful Question Framework"]

package/commands/brain-derive.md

@@ -2,6 +2,7 @@
 description: Derive BRAIN.md for section(s) now
 argument-hint: "[section] [--all] [--cross-room] [--dry-run]"
 serves_jtbd: ["audit-room"]
+teaching: "When a room section drifts from its BRAIN.md derivation, /mos:brain-derive rebuilds the per-section Brain context now. Run after large filings or before a decision gate."
 disable-model-invocation: false
 allowed-tools: Bash(node *)
 ---

package/commands/build-knowledge.md

@@ -2,6 +2,7 @@
 name: build-knowledge
 description: Climb Ackoff's DIKW pyramid across the room
 serves_jtbd: ["explore"]
+teaching: "When you have data but not yet wisdom, /mos:build-knowledge climbs Ackoff's DIKW pyramid across the room. Surfaces what you know, what you can decide, and what is still raw."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Ackoff Pyramid"]

package/commands/build-thesis.md

@@ -2,6 +2,7 @@
 name: build-thesis
 description: Run the Ten-Questions investment thesis gate
 serves_jtbd: ["decide-pursue", "prepare-pitch"]
+teaching: "When you need to know if this venture is worth pursuing, /mos:build-thesis runs the Ten-Questions investment thesis gate. The output is a defensible go / no-go with reasons."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["PWS Value Proposition"]

package/commands/causal.md

@@ -3,6 +3,7 @@ name: causal
 description: Trace causal edges in the room's graph
 argument-hint: [extract|trace|predict]
 serves_jtbd: ["find-problem", "find-bottleneck"]
+teaching: "When you suspect the visible problem is downstream of something else, /mos:causal traces causal edges in the room's graph. Surfaces the upstream causes worth fixing."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Root Cause Analysis"]

package/commands/challenge-assumptions.md

@@ -2,6 +2,7 @@
 name: challenge-assumptions
 description: Stress-test assumptions with Devil's Advocate
 serves_jtbd: ["validate-idea", "surface-contradiction"]
+teaching: "When an idea feels too clean, /mos:challenge-assumptions runs Devil's Advocate against the load-bearing claims. Catches the assumptions you stopped questioning."
 allowed-tools:
   - Read
   - Write

package/commands/compare-ventures.md

@@ -2,6 +2,7 @@
 name: compare-ventures
 description: Compare against ventures that tried this before
 serves_jtbd: ["compare-options"]
+teaching: "When you are weighing your approach against ventures that tried this before, /mos:compare-ventures lines them up on the dimensions that matter. Saves you from re-learning their lessons."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["PWS Triple Validation Compass"]

package/commands/dashboard.md

@@ -3,6 +3,7 @@ name: dashboard
 description: Open the Data Room dashboard (live or snapshot)
 body_shape: raw
 serves_jtbd: ["audit-room", "prepare-pitch"]
+teaching: "When you need to see the whole room at a glance, /mos:dashboard opens the live or snapshot view in De Stijl layout. The fastest way to read room health before a meeting."
 ui_reference: skills/ui-system/SKILL.md
 argument-hint: [live|stop|open]
 allowed-tools:

package/commands/deep-grade.md

@@ -2,6 +2,7 @@
 name: deep-grade
 description: Grade a venture against 100+ calibrated projects
 serves_jtbd: ["audit-room", "compare-options"]
+teaching: "When you need a calibrated grade on the room's quality, /mos:deep-grade scores it against 100+ real student projects. Best after at least three sections are populated."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["PWS Triple Validation Compass"]

package/commands/diagnose.md

@@ -2,6 +2,7 @@
 name: diagnose
 description: Classify problem type against the PWS matrix
 serves_jtbd: ["decide-pursue"]
+teaching: "When you cannot tell if this is an Ill-Defined or Well-Defined Problem, /mos:diagnose classifies it against the PWS matrix. Knowing the problem type picks the right methodology."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Problem Definition Transformation Framework"]

package/commands/diagnostics.md

@@ -3,6 +3,7 @@ name: diagnostics
 description: Run Wave-1 algorithmic fingerprint on the room
 body_shape: E
 serves_jtbd: ["audit-room"]
+teaching: "When you need a quantitative read on the room, /mos:diagnostics runs the Wave-1 fingerprint: disruption, blindspot, novelty, surprise. Surfaces algorithmic signals humans miss."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["HSI Semantic Surprise Analysis Assistant"]

package/commands/doctor.md

@@ -5,6 +5,7 @@ argument-hint: "[--fix] [--cascade-rooms] [--verify-surface] [--room-md] [--ui-c
 body_shape: E (Action Report)
 body_shape_detail: per-class status rows with [before → after] pattern, summary totals, F.1 Next Move selector when drift detected without --fix
 serves_jtbd: ["audit-room"]
+teaching: "When something feels off with the install, /mos:doctor diagnoses install-cache drift, ROOM.md gaps, statusline visibility, and UI compliance. Optionally repairs with --fix."
 allowed-tools:
   - Bash
   - Read

package/commands/dominant-designs.md

@@ -2,6 +2,7 @@
 name: dominant-designs
 description: Spot dominant designs with Utterback-Abernathy
 serves_jtbd: ["understand-market"]
+teaching: "When you are wondering if the market has settled on a winning design, /mos:dominant-designs runs Utterback-Abernathy to spot it. Tells you whether to ride the wave or break it."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Dominant Design"]

package/commands/explain-decision.md

@@ -2,6 +2,7 @@
 description: Show Navigation Engine decision trace for last turn
 argument-hint: "[--last N] [--session SESSIONID]"
 serves_jtbd: ["audit-room"]
+teaching: "When Larry made a recommendation and you want to know why, /mos:explain-decision shows the Navigation Engine trace for the last turn. Every recommendation has a graph path behind it."
 disable-model-invocation: true
 allowed-tools: Bash(node *)
 ---

package/commands/explore-domains.md

@@ -2,6 +2,7 @@
 name: explore-domains
 description: Map domains through IKA + Feynman decomposition
 serves_jtbd: ["find-problem", "understand-market", "explore"]
+teaching: "When the problem could live in any of several domains, /mos:explore-domains maps the territory through IKA and Feynman decomposition. Surfaces where to look before you commit."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Domain Selection"]

package/commands/explore-futures.md

@@ -2,6 +2,7 @@
 name: explore-futures
 description: Synthesize TTA + Scenario + S-Curve futures
 serves_jtbd: ["compare-options", "explore"]
+teaching: "When the path forward branches into multiple plausible futures, /mos:explore-futures synthesizes TTA, Scenario, and S-Curve views. Helps you choose without pretending you can predict."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Scenario Planning"]

package/commands/explore-trends.md

@@ -2,6 +2,7 @@
 name: explore-trends
 description: Push trends to extremes to surface future problems
 serves_jtbd: ["understand-market", "explore"]
+teaching: "When today's trends could become tomorrow's problems, /mos:explore-trends pushes them to extremes to surface the second-order effects. The future shows up at the edges first."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["S-Curve Analysis"]

package/commands/export.md

@@ -5,6 +5,7 @@ argument-hint: [hub|thesis|summary|report]
 disable-model-invocation: true
 body_shape: E (Action Report)
 serves_jtbd: ["prepare-pitch"]
+teaching: "When you need to share a Data Room view with someone outside the room, /mos:export packages it as a De Stijl HTML artifact. Investor-ready, no install required on their side."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash

package/commands/feynman-timeline-refresh.md

@@ -0,0 +1,78 @@
+---
+description: Refresh FEYNMAN.md ## Timeline (auto) section for one or all room sections
+argument-hint: "[--all | --section <slug>]"
+serves_jtbd: ["validate-idea", "audit-room"]
+teaching: "When a section's FEYNMAN.md timeline feels stale, /mos:feynman-timeline-refresh rebuilds the auto-section from the memory event log. Human-authored prose stays byte-preserved."
+disable-model-invocation: false
+allowed-tools: Bash(node *)
+kind: utility
+frameworks: []
+produces: "room/*/FEYNMAN.md"
+inputs: []
+autonomous_safe: true
+---
+
+# /mos:feynman-timeline-refresh
+
+Force-refresh the `## Timeline (auto)` sentinel-bounded section in each section's `FEYNMAN.md`. The renderer reads from `room.db` via the Phase 109 `navigation.cjs` chokepoint; the runner writes back atomically with the human-authored body byte-preserved. This is the manual knob the user reaches for when the automatic session-start cascade is not enough -- explicit redraw, ignore the watermark.
+
+## Modes
+
+- `/mos:feynman-timeline-refresh` -- refresh every section in the active room (default; equivalent to `--all`).
+- `/mos:feynman-timeline-refresh --all` -- refresh every section in the active room.
+- `/mos:feynman-timeline-refresh --section <slug>` -- refresh one section.
+
+## Output
+
+F.0 Action Report (Canon Part 3 UI Ruling System; same shape as `/mos:brain-derive`'s Shape E). Three summary rows + a PER SECTION breakdown + a NEXT action footer:
+
+- Sections refreshed: N
+- Sections skipped (watermark fresh): S
+- Sections failed: F
+
+When more than 3 target sections, per-section progress streams to stderr as each completes: `[1/7] market-analysis: refreshed`. The final report renders to stdout at the end.
+
+## Graceful degradation
+
+- **No active room**: exit 1 with "Set one with /mos:rooms switch <slug>".
+- **Invalid section slug**: exit 1 with a pointer to the active room and a hint to list sections.
+- **room.db missing**: single-line "room.db not found for active room; the runner needs the Phase 109 SQL spine" message, exit 0 (soft-fail; the timeline section is enrichment, not a gate).
+- **Runner exception per section**: the failure is logged via `feynman_timeline_refresh_failed` memory_event; the per-section row in the report names the failure; other sections still process.
+
+## Canon references
+
+- **Canon Part 3 (Tri-Context Decision Gate)**: output uses the F.0 / Shape E Action Report so the user sees a LOCAL snapshot of what was refreshed.
+- **Canon Part 7 (Reuse Before Build)**: the command wraps `lib/core/feynman/timeline-runner.cjs` (Plan 124-02). No new render logic at the command layer.
+- **Canon Part 8 (Graph Boundary)**: zero net new Brain surface. The renderer reads ONLY `room.db` via `navigation.cjs`. The runner writes ONLY FEYNMAN.md inside the sentinels.
+- **Canon Part 9 (Memory Locality)**: this is the Larry-explains face of `memory_event` -- the rendered timeline section IS the human-readable view of the SQL log.
+
+## Invocation
+
+Run the dispatcher via Bash:
+
+```bash
+node ${CLAUDE_PLUGIN_ROOT}/scripts/feynman-timeline-refresh-command.cjs $ARGUMENTS
+```
+
+## Examples
+
+```
+/mos:feynman-timeline-refresh
+/mos:feynman-timeline-refresh --all
+/mos:feynman-timeline-refresh --section market-analysis
+```
+
+## Exit codes
+
+| Exit | Meaning |
+| --- | --- |
+| 0 | Success (including soft-fail paths: room.db missing, every section watermark-skipped) |
+| 1 | Invocation error: no active room, invalid section slug, malformed args |
+
+## Cross-surface adaptation
+
+- **CLI**: full power. Slash command resolves via Claude Code's plugin hook substrate and runs the dispatcher through the Bash tool. F.0 report renders in the terminal.
+- **Desktop**: the same slash command runs when the plugin is connected. Larry may narrate the result conversationally; the underlying dispatcher is identical.
+- **Cowork**: same as CLI. Team members see the regenerated FEYNMAN.md `## Timeline (auto)` block through the shared `00_Context/` snapshot on their next session-start.
+
+No surface-specific code exists anywhere in the dispatcher.

package/commands/file-meeting.md

@@ -3,6 +3,7 @@ name: file-meeting
 description: File a meeting transcript into the Data Room
 argument-hint: [--latest|--paste|<file>]
 serves_jtbd: ["file-meeting"]
+teaching: "When a meeting just happened, /mos:file-meeting captures the transcript and routes the intelligence into the right room sections. Meetings are where institutional knowledge actually lives."
 allowed-tools:
   - Read
   - Write

package/commands/find-analogies.md

@@ -3,6 +3,7 @@ name: find-analogies
 description: Find cross-domain analogies with SAPPhIRE + TRIZ
 body_shape: D (Comparison Matrix)
 serves_jtbd: ["connect-domains"]
+teaching: "When the answer might live in another field, /mos:find-analogies runs SAPPhIRE and TRIZ against your problem to surface cross-domain matches. Most breakthroughs are borrowed structure."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Four Lenses of Innovation"]

package/commands/find-bottlenecks.md

@@ -2,6 +2,7 @@
 name: find-bottlenecks
 description: Find lagging components via Reverse Salient
 serves_jtbd: ["find-bottleneck"]
+teaching: "When progress feels stuck and you cannot say where, /mos:find-bottlenecks runs Reverse Salient analysis to name the lagging component. Hughes 1983, but for your venture."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Reverse Salient Analysis"]

package/commands/find-connections.md

@@ -2,6 +2,7 @@
 name: find-connections
 description: Find cross-domain patterns that touch your work
 serves_jtbd: ["connect-domains"]
+teaching: "When you suspect your work touches a pattern in another field, /mos:find-connections traces cross-domain links through the graph. Surfaces the connections you did not know to look for."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Usher's Model of Cumulative Synthesis"]

package/commands/funding.md

@@ -4,6 +4,7 @@ description: Track grant opportunities through their lifecycle
 argument-hint: [list|add|update]
 body_shape: B (Semantic Tree)
 serves_jtbd: ["prepare-pitch", "decide-pursue"]
+teaching: "When you need to track grants and investors as a real pipeline, /mos:funding manages the lifecycle from spotted to applied to decided. Funding is a process, not a one-shot event."
 allowed-tools:
   - Read
   - Write

package/commands/grade.md

@@ -2,6 +2,7 @@
 name: grade
 description: Grade problem-discovery quality (6 components)
 serves_jtbd: ["audit-room"]
+teaching: "When you want a fast read on problem-discovery quality, /mos:grade scores the room on six components in under a minute. The lightweight cousin of /mos:deep-grade."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["PWS Triple Validation Compass"]

package/commands/graph.md

@@ -4,6 +4,7 @@ description: Explore the knowledge graph by asking questions
 body_shape: C (Room Card)
 body_shape_detail: Query results as cards, graph stats as header
 serves_jtbd: ["audit-room", "explore"]
+teaching: "When you want to ask the knowledge graph a question without writing Cypher, /mos:graph translates plain English into the right traversal. Larry walks the edges so you do not have to."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash

package/commands/hat-briefing.md

@@ -4,6 +4,7 @@ description: Consolidate Six Hats briefings from hat memory
 body_shape: C (Dashboard Grid)
 body_shape_detail: 6-panel hat grid + synthesis strip
 serves_jtbd: ["prepare-pitch"]
+teaching: "When you have run several Six Hats sessions and need them consolidated, /mos:hat-briefing pulls the hat memory into one briefing. Best right before a stakeholder review."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Six Thinking Hats"]

package/commands/heal.md

@@ -5,6 +5,7 @@ argument-hint: "[room-dir]"
 body_shape: E (Action Report)
 body_shape_detail: 10-step heal table mirrors recipe provenance section
 serves_jtbd: ["audit-room"]
+teaching: "When a plugin upgrade leaves the room with structural drift, /mos:heal repairs the missing ROOM.md, broken backlinks, and stale section state. Use after every major version bump."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash

package/commands/help.md

@@ -5,6 +5,7 @@ argument-hint: [command-name]
 body_shape: B (Semantic Tree)
 body_shape_detail: -- (inline, no zones)
 serves_jtbd: ["explore"]
+teaching: "When you forget which /mos: command does what, /mos:help groups them by flow in tldr style. Start here when the surface feels overwhelming."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Read

package/commands/hmi-status.md

@@ -5,6 +5,7 @@ argument-hint: "[--json]"
 body_shape: E (Action Report)
 body_shape_detail: 4-zone Shape E rendering of the side-channel at <roomDir>/.mindrian/last-hmi-poll.json (status + counts + top-5 priorities + operator-shape mismatches); --json emits raw envelope; graceful Shape E when poll absent or tier 0
 serves_jtbd: ["audit-room"]
+teaching: "When you need to know how well the UI is honoring the ruling system, /mos:hmi-status shows the latest compliance poll with operator-aware drift summaries. Read-only; fix via /mos:doctor."
 locks_operator: null
 min_tier: 0
 concurrency: sequential

package/commands/jtbd.md

@@ -5,6 +5,7 @@ argument-hint: "[set <jtbd> | clear | list | history] [--json]"
 body_shape: E (Action Report)
 body_shape_detail: current state + last 5 history (default), 13 entries (list), full history (history), Shape F.1 picker (set with no arg), Shape E confirmation (clear, set <jtbd>)
 serves_jtbd: ["audit-room"]
+teaching: "When you need to see or set the active job-to-be-done for this room, /mos:jtbd shows the per-room signal that tells Larry what kind of work you are doing right now."
 locks_operator: null
 min_tier: 0
 concurrency: sequential

package/commands/leadership.md

@@ -2,6 +2,7 @@
 name: leadership
 description: Diagnose the leadership shape your team needs
 serves_jtbd: ["explore"]
+teaching: "When the team feels wrong-shaped for the stage, /mos:leadership diagnoses which leadership pattern you actually need. Different stages of a venture need different leadership shapes."
 allowed-tools:
   - Read
   - Write

package/commands/lean-canvas.md

@@ -2,6 +2,7 @@
 name: lean-canvas
 description: Fill the Lean Canvas in one page (9 boxes)
 serves_jtbd: ["prepare-pitch", "validate-idea"]
+teaching: "When you need the whole business model on one page, /mos:lean-canvas fills the nine boxes from your room data. The fastest way to get a defensible canvas in front of someone."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Lean Canvas"]

package/commands/macro-trends.md

@@ -2,6 +2,7 @@
 name: macro-trends
 description: Map macro changes with PEST across a domain
 serves_jtbd: ["understand-market"]
+teaching: "When you need to map the forces shaping a domain, /mos:macro-trends runs PEST across Political, Economic, Social, and Technological dimensions. The wide-angle lens before you zoom in."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["PEST Analysis"]

package/commands/map-unknowns.md

@@ -2,6 +2,7 @@
 name: map-unknowns
 description: Map known, unknown, and unknowable (Rumsfeld)
 serves_jtbd: ["validate-idea"]
+teaching: "When you cannot tell what you do not know, /mos:map-unknowns plots known, unknown, and unknowable in a Rumsfeld matrix. The unknowable column is usually where the risk lives."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Knowns and Unknowns Matrix Framework"]

package/commands/memory.md

@@ -5,6 +5,7 @@ argument-hint: "[query <jtbd> | cross-room | resume | park <jtbd> | complete <jt
 body_shape: E (Action Report)
 body_shape_detail: 4-zone Shape E for default + park + complete + opt-out; Shape G (Comparison Matrix) for query when Phase 101 ships (Shape E fallback otherwise); Shape G Mode A or Shape E Mode B for cross-room depending on Brain availability; Shape F.6 (or F.1 fallback) for resume picker.
 serves_jtbd: ["audit-room"]
+teaching: "When you need to inspect what the room remembers, /mos:memory shows the three layers: within-session, across-session, and cross-room. Memory locality is a Canon Part 9 invariant."
 locks_operator: null
 min_tier: 0
 concurrency: sequential

package/commands/models.md

@@ -4,6 +4,7 @@ description: View or switch model-routing profiles
 argument-hint: [list|set|show]
 body_shape: C (Information Card)
 serves_jtbd: ["compare-options"]
+teaching: "When you want to see or switch which model routes which kind of work, /mos:models opens the routing profile. Different tasks deserve different models."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Read

package/commands/mos-reason.md

@@ -4,6 +4,7 @@ command: mos:reason
 description: Generate Feynman-MINTO reasoning for a section
 usage: /mos:reason [--section <name>] [--regenerate-all]
 serves_jtbd: ["explore"]
+teaching: "When a section needs Feynman-MINTO reasoning generated against its artifacts, /mos:mos-reason produces the pyramid: governing thought down to grounded support. Larry's structured thinking surface."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["The Pyramid Principle"]

package/commands/mullins.md

@@ -2,6 +2,7 @@
 name: mullins
 description: Run Mullins 7-Domains on a business opportunity
 serves_jtbd: ["understand-market"]
+teaching: "When you need the most rigorous opportunity screen ever published, /mos:mullins runs the 7-Domains Model from Mullins' New Business Road Test. Best before you commit real resources."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Mullins Model"]

package/commands/new-project.md

@@ -3,6 +3,7 @@ name: new-project
 description: Start a new venture project and create its room
 argument-hint: [name]
 serves_jtbd: ["explore"]
+teaching: "When you are starting a new venture, /mos:new-project creates the room scaffolding and registers it in the room registry. The first move of every Mindrian journey."
 allowed-tools:
   - Read
   - Write

package/commands/onboard.md

@@ -4,6 +4,7 @@ description: Walk through MindrianOS and build your first room
 body_shape: B (Semantic Tree)
 body_shape_detail: Steps as conversational flow, context building as nested nodes
 serves_jtbd: ["explore"]
+teaching: "When you just installed MindrianOS, /mos:onboard walks you through the system and builds your first room. Designed so a stranger can self-activate without Larry holding their hand."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Read

package/commands/operator.md

@@ -5,6 +5,7 @@ argument-hint: "[history] [set <op>] [reset] [--json]"
 body_shape: E (Action Report)
 body_shape_detail: current state + last 5 history (default), full history (history subcommand), Shape F.1 picker (set subcommand), Shape F.4 confirmation (reset subcommand)
 serves_jtbd: ["explore"]
+teaching: "When you want to see or set how Larry should render right now, /mos:operator shows the conversation state machine: JUST_TALK, EXPLORE_CAPTURE, BUILD_ROOM, METHODOLOGY, or DECISION_GATE."
 allowed-tools:
   - Bash
   - Read

package/commands/opportunities.md

@@ -4,6 +4,7 @@ description: Discover and manage grants in the Opportunity Bank
 argument-hint: [list|add|scan]
 body_shape: E (Action Report)
 serves_jtbd: ["explore"]
+teaching: "When you need to manage grants as a live pipeline rather than a list, /mos:opportunities surfaces the Opportunity Bank with HSI scores and decision states. Funding deserves the same rigor as product."
 allowed-tools:
   - Read
   - Write

package/commands/organize.md

@@ -4,6 +4,7 @@ description: Navigate room hierarchy with graph-aware tree
 argument-hint: [tree|propose|compound]
 body_shape: B (Semantic Tree)
 serves_jtbd: ["audit-room"]
+teaching: "When the room hierarchy has grown messy, /mos:organize navigates it with a graph-aware tree that respects sub-room boundaries. The structural overview, not the content view."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Read

package/commands/persona.md

@@ -3,6 +3,7 @@ name: persona
 description: Generate Six-Hats lenses from room data
 body_shape: C (Room Card)
 serves_jtbd: ["prepare-pitch"]
+teaching: "When you need fresh perspectives on the room, /mos:persona generates Six-Hats lenses from your room data. Each persona argues from a different stance; you decide what holds."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Six Thinking Hats"]

package/commands/pipeline.md

@@ -3,6 +3,7 @@ name: pipeline
 description: Chain a multi-step methodology pipeline
 argument-hint: '[pipeline-name] [--from-problem-type <x>] [--from-framework <x>]'
 serves_jtbd: ["plan-execution"]
+teaching: "When you want several methodologies chained instead of run one-by-one, /mos:pipeline executes a multi-step pipeline with the room as the connecting tissue. Week 7 pattern."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: meta
 frameworks: []

package/commands/present.md

@@ -4,6 +4,7 @@ description: Generate the 6-view presentation and open it
 body_shape: E (Action Report)
 body_shape_detail: Generation results as action items, 6 views listed as outputs
 serves_jtbd: ["prepare-pitch"]
+teaching: "When you need to walk someone through the room visually, /mos:present generates the 6-view presentation and opens it. Dashboard, Wiki, Deck, Insights, Diagrams, Graph in one artifact."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash

package/commands/publish.md

@@ -3,6 +3,7 @@ name: publish
 description: Publish the Data Room presentation to Vercel
 argument-hint: [--all|<view>]
 serves_jtbd: ["prepare-pitch"]
+teaching: "When the Data Room is ready to share publicly, /mos:publish deploys the presentation to Vercel with a one-click link. From local artifact to shareable URL in one move."
 disable-model-invocation: true
 allowed-tools:
   - Read

package/commands/query.md

@@ -3,6 +3,7 @@ name: query
 description: Query the knowledge graph in natural language
 argument-hint: [question]
 serves_jtbd: ["audit-room", "explore"]
+teaching: "When you need to ask the knowledge graph something specific, /mos:query translates natural language into the right traversal and returns the answer with its graph path."
 allowed-tools:
   - Read
   - Bash

package/commands/radar.md

@@ -2,6 +2,7 @@
 name: radar
 description: Track Claude capabilities that may help MindrianOS
 serves_jtbd: ["understand-market"]
+teaching: "When new Claude capabilities ship that might change what MindrianOS can do, /mos:radar tracks them so you do not have to. Capability awareness as a habit, not a one-time scan."
 allowed-tools:
   - Read
   - Write

package/commands/reanalyze.md

@@ -4,6 +4,7 @@ description: Re-analyze filed meetings for new patterns
 body_shape: E (Action Report)
 body_shape_detail: Before/after delta showing new insights discovered
 serves_jtbd: ["file-meeting"]
+teaching: "When a meeting was filed earlier and the room has since grown, /mos:reanalyze re-runs the cascade pattern detection. New context can change what an old meeting meant."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash

package/commands/research.md

@@ -3,6 +3,7 @@ name: research
 description: Research the web and cross-reference with Brain
 argument-hint: [topic]
 serves_jtbd: ["explore", "understand-market"]
+teaching: "When you need fresh evidence from the web cross-referenced with the Brain methodology graph, /mos:research runs the dual-source pull. Public signal plus calibrated framework."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["Hypothesis-Driven Problem Solving"]

package/commands/room.md

@@ -5,6 +5,7 @@ argument-hint: [overview|<section>]
 body_shape_overview: B (Semantic Tree)
 body_shape_section: C (Room Card)
 serves_jtbd: ["audit-room"]
+teaching: "When you need to view or launch the active Data Room, /mos:room opens the room view with its current state. The default entry point for room navigation."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Read