Steward Status logo

Steward Status

Organization
vibevm
steward-status

Resolve and verify the current user-local stewardship context and report the campaign frontier. Use at central-session start, after interruption or compaction, or for a status request; continue execution only when the current owner request includes it.

Overview

Publishervibevm
Repositoryvibevm
Skill namesteward-status
Stars
285
Forks
83
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vibevm on GitHub. Read the source before you install it.

Installation

Install the Steward Status AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vibevm/vibevm/tree/main/vibevm/vibepacks/org.vibevm.world/multi-user-planning/v1.0.0/vibevm/vibespecs/skills/steward-status
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vibevm/vibevm.git /tmp/vibevm
mkdir -p .claude/skills
cp -r /tmp/vibevm/vibevm/vibepacks/org.vibevm.world/multi-user-planning/v1.0.0/vibevm/vibespecs/skills/steward-status .claude/skills/steward-status
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Steward Status in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Steward Status on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Steward Status is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Steward status {#root}

@fact:STATUS-CENTRAL-ONLY This skill is for an owner-facing central session. If the current task is a worker/reviewer packet, report that the packet—not central custody—governs and stop. @status:impl/done

Procedure {#procedure}

@fact:STATUS-VERSUS-CONTINUE Determine the current owner's requested scope first. A status, review or planning-only request ends with that deliverable; neither a stored next atom nor a generated goal starts implementation. If the request also authorizes continuation, report the verified state and continue within that scope. A stop or narrower instruction takes precedence over the standing campaign route. @status:impl/done

  1. @fact:STATUS-RESOLVE Resolve the exact repository/worktree/revision binding under ~/.vibe/steward/contexts/*/binding.toml. An explicit context named by the owner wins. Do not guess between duplicate exact matches. @status:impl/done
  2. @fact:STATUS-READ On cold start, resume, compaction, or model/account change, read global/context settings, advisory custody, the whole plan.toml, and the repository's actual branch, HEAD, ahead/behind and dirty state. Inspect relevant surviving worker jobs and candidate artifacts before restarting work. In an uninterrupted session, reuse the already-read complete plan when its revision and relevant input changes are accounted for; unknown changes require a fresh read. Read handoff material only when the owner explicitly requests formal handoff inspection or receipt. Session/handoff/takeover records are not prerequisites for ordinary status or continuation. @status:impl/done
  3. @fact:STATUS-VERIFY Compare stored claims with the tree. Separate project-accepted evidence from local claims and candidates; warn first when a valid explicit formal offer is active or an actual conflicting writer is observed. Recapture expected own writes and explained input changes; resolve unexplained semantic conflicts before writing. vacant, held, stale heartbeat and mismatched holder/session are advisory diagnostics, not authority or a write gate. Accepted evidence for an unchanged exact subject remains accepted; an interrupted thought or absent transcript does not prove acceptance or failure. Resolve uncertain tool outcomes before replay under spec://org.vibevm.world/multi-user-planning/flows/multi-user-planning/interruption-recovery#root. @status:impl/done
  4. @fact:STATUS-BACKSCAN Check every non-terminal mandate item has a plan node and every candidate artifact named by the plan still exists. Do not pay or repair the debt during a status-only request. @status:impl/done

Output {#output}

@fact:STATUS-OUTPUT Report: context and effective modes; custody holder/epoch; repository state; accepted boundary; candidate/unaccepted work and surviving jobs; full remaining epic route in compressed form; expanded current frontier; blockers and the candidate next atom. Status reporting does not change product work, plan nodes or acceptance, or claim custody. Ordinary context resolution may create missing documented defaults and refresh stale derived goals as the boot contract requires; an explicitly read-only request or valid formal-offer fence instead reports what is missing/stale without writing. Stop after a status-only report; when continuation is already authorized, proceed after the report without requesting that authority again or creating a handoff ritual. @status:impl/done

Frequently asked questions

What does the Steward Status AI skill do?

Resolve and verify the current user-local stewardship context and report the campaign frontier. Use at central-session start, after interruption or compaction, or for a status request; continue execution only when the current owner request includes it.

Why use Steward Status on TypingMind?

Because you install it once and use it with any model. Steward Status is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Steward Status in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vibevm/vibevm/tree/main/vibevm/vibepacks/org.vibevm.world/multi-user-planning/v1.0.0/vibevm/vibespecs/skills/steward-status. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Steward Status?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Steward Status?

As many as you like. As long as a model supports skills, you can use Steward Status with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Steward Status AI skill free?

It is published on GitHub by vibevm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇