status

Generates a tactical briefing of the latest VibeOS work session from status files.

2|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/chieflatif/vibeos-plugin --skill status-chieflatif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/skills/status
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill status-chieflatif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a concise, actionable briefing of the current or most recent VibeOS work session, helping users quickly understand progress, remaining work, and blockers without digging through logs.

Core Features & Use Cases

  • Read and synthesize the latest session state from files such as .vibeos/session-state.json, .vibeos/build-log.md, and .vibeos/checkpoints/*.json to present a clear status.
  • Present a structured report with sections like Done In This Session, Still In Motion, Issues Or Blockers, Next Tactical Move, and Decision Needed From You.
  • Respect governance signals like active overrides, checkpoints, and recent audits to reflect true autonomy status.
  • Support planning and daily standups by turning verbose logs into a compact update for teammates and stakeholders.

Quick Start

Ask for the Session Status to receive a tactical briefing of the current or most recent VibeOS session.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a concise summary of my current VibeOS work session progress?

To get a concise summary of your VibeOS work session progress, request a session status briefing. It reads session-state.json, build logs, and checkpoints to generate a tactical report covering completed work, in-motion items, and blockers.

What is the best way to track blockers and next moves across active work orders?

Tracking blockers and next moves across active work orders is done by reading WO indexes and audit signals. The system synthesizes this data into a structured briefing highlighting current issues and the next tactical move required.

Can I use session checkpoints and audit signals to prepare for a daily standup?

You can use session checkpoints and audit signals to prepare for a daily standup. The system transforms verbose build logs and governance overrides into a compact, actionable status update for teammates and stakeholders.

Does generating a tactical status report require active session-state.json configuration?

Generating a tactical status report relies on reading existing session-state.json configuration. It processes current files to reflect true autonomy status, meaning no special configuration is needed beyond standard VibeOS session logging.

Why does my session status briefing show governance overrides and audit warnings?

Your session status briefing shows governance overrides and audit warnings because it respects active governance signals. It reads recent audits and checkpoints to ensure the status report reflects the true autonomy status of the work session.

How do I check what decisions are needed from me in the latest VibeOS work session?

To check what decisions are needed from you in the latest VibeOS work session, review the 'Decision Needed From You' section of the status report. It analyzes session state and active blockers to surface required human input.