skills.rest
autopus-ai
autopus-aiOFFICIAL
Explore all skills by this author →
GitHub

auto-status

Displays SPEC lifecycle and module status dashboard for the current project and submodules.

111|73|Updated Mar 20, 2026
Search Tags:#monitoring#cli#dashboard#pipeline#spec#status#omp
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-status-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-status
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/auto-status
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-status-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with SPEC-driven development across a project and its submodules, it is hard to know which SPECs are in progress, who owns each execution, and what command to run next. This Skill aggregates that scattered state into a single dashboard. ## Core Features & Use Cases - SPEC Status Dashboard: Runs auto status to collect SPEC lifecycle and module state for the current workspace. - Ownership Verification: Reads .autopus/pipeline-state/<SPEC-ID>.execution-owner.json receipts and combines them with OMP-native hub job state to detect single-DAG-owner violations. - Next-Action Guidance: Reports per-SPEC status along with the next executable command. - Use Case: After running parallel implementation tasks across submodules, invoke /auto status to confirm which SPECs completed, which are blocked, and what to execute next. ## Quick Start Ask the agent to run /auto status to show the current SPEC dashboard for this project and its submodules.

Frequently Asked Questions about auto-status

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

FAQPage Schema
How do I check SPEC status across project submodules?▼

Invoke /auto status or /auto-status in the OMP session. The skill runs the auto status CLI to collect SPEC lifecycle and module state for the current workspace and its submodules, then reports per-SPEC status.

What is a single DAG owner violation in SPEC pipelines?▼

It occurs when execution ownership receipts and OMP-native hub job states disagree about which session owns a SPEC's execution DAG. The skill combines execution-owner.json receipts with hub state to detect and report such violations.

Can auto status inspect other OMP user sessions?▼

No. The skill explicitly does not assume the external CLI can inspect OMP user-session roots. It only reads the current workspace's pipeline-state receipts and the current OMP session's native hub job state.

Where are SPEC execution owner receipts stored?▼

Receipts are stored in the workspace at .autopus/pipeline-state/<SPEC-ID>.execution-owner.json. The skill reads these files and combines their owner, source, and verification fields with hub state.

What should I do after viewing the SPEC dashboard?▼

The dashboard reports the next executable command for each SPEC based on its current lifecycle state. Follow that guidance to continue implementation, testing, or synchronization steps in the pipeline.

Related Skills

Explore More Software Engineering Skills→
b12consultingb12consulting
2

specs-tickets

Create and manage spec-driven tickets through six lifecycle phases.

Official
Advanced
CvNoobLrxCvNoobLrx

auto-coder

Automate spec-driven implementation, testing, and progress tracking for modular tasks.

Community
Advanced
jeremyaryjeremyary
7

status

Run linting, type checks, tests, and dependency audits with pass/fail reporting.

Community
Intermediate
led8led8

jq

Parse and transform JSON data from command-line inputs using jq filters.

Community
Intermediate