skills.rest
chieflatif
chieflatifCOMMUNITY
Explore all skills by this author →
GitHub

vibeos-status

Your session summary is ready.

2|1|Updated Mar 9, 2026
Search Tags:#tactical#work-orders#session-status#status-update#build-log#vibeos
One-click install
npx skills add https://github.com/chieflatif/vibeos-plugin --skill vibeos-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibeos-status
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/reference/codex/skills/vibeos-status
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill vibeos-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tactical, session-level status reporting for active VibeOS Codex sessions, enabling quick situational awareness without exposing broader program details.

Core Features & Use Cases

  • Read session-state.json, build-log.md, checkpoints, config, WO index, and active work orders
  • Summarize current focus, completed work, in-progress items, blockers, and decisions
  • Keep updates tactical and hand off to vibeos-project-status for big-picture views when needed

Quick Start

Ask VibeOS for a tactical session status update

Frequently Asked Questions about vibeos-status

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

FAQPage Schema
How do I get a tactical session status update for my active build?▼

You can generate a tactical session status update by applying the Skill during a live VibeOS Codex session. It reads internal state files like session-state.json and build-log.md to summarize focus, blockers, and decisions.

What is the difference between tactical session status and broader program views?▼

Tactical session status reports scoped, session-level updates for active Codex sessions, while broader program views are delegated to vibeos-project-status to expose big-picture project details without cluttering the tactical report.

How do I summarize current focus and blockers from work orders?▼

The Skill summarizes current focus and blockers by reading active work orders, WO-INDEX.md, and checkpoints. It enforces plain-English reporting to deliver a concise tactical update of completed work and in-motion items.

Do I need specific state files to generate a VibeOS session status report?▼

Yes, the Skill requires specific files like .vibeos/session-state.json, .vibeos/config.json, and .vibeos/build-log.md to exist in your project. It reads these internal state files to generate the tactical update.

Can I view project-level status instead of session-level tactical updates?▼

You can view project-level status by delegating to vibeos-project-status. The current Skill strictly enforces tactical, session-level reporting and hands off to the broader program view tool when needed.

Related Skills

Explore More Software Engineering Skills→
chieflatifchieflatif
2

vibeos-autonomous

Enable a temporary autonomous session override for VibeOS in Codex.

Community
Intermediate
chieflatifchieflatif
2

status

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

Community
Intermediate
chieflatifchieflatif
2

autonomous

Enable continuous autonomous VibeOS sessions by updating configuration and session state files.

Community
Advanced
chieflatifchieflatif
2

vibeos-session-audit

Audit VibeOS build sessions and save structured reports to .vibeos/session-audits/.

Community
Advanced