status

Reports pipeline progress for a work item and names the next command to run.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/AiFirstDevelopment/quorum --skill status-aifirstdevelopment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/AiFirstDevelopment/quorum/tree/main/plugins/quorum/skills/status
Command: npx skills add https://github.com/AiFirstDevelopment/quorum --skill status-aifirstdevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a multi-stage plan-build-review-adjudicate pipeline, it is hard to know what has already run, what it concluded, and what changed since. This Skill reads the recorded state and on-disk artifacts to give a straight, read-only answer about where a work item stands. ## Core Features & Use Cases - Pipeline state detection: Reads state.json, plan.md, reviews, and verdict files to identify which stage a work item is in, from planned through published. - Delta analysis: Uses recorded git head SHAs to compute exactly which commits landed after review or adjudication, with commit subjects and diffstats. - Contradiction reporting: Cross-checks the recorded state against the disk and flags disagreements, missing lenses, guard violations, and suspicious verdicts. - Use Case: After returning to a branch mid-week, ask where things stand and get a terse report showing the pipeline completed, one small commit landed after the verdict, and the single next command to run. ## Quick Start Ask the AI to run the status skill to report where the current work item stands in the quorum pipeline and what command to run next.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check the status of an AI pipeline work item?▼

Run the status command with the work item's slug. It reads state.json and the artifacts under docs/work, then reports what has run, what it concluded, and the one next command to run.

How to tell if code changed after a review completed?▼

The skill compares the recorded review and verdict head SHAs against HEAD using git log and diffstat. It reports the exact commit subjects and sizes that no lens has seen, rather than just calling the reviews stale.

Does the status command modify files or run pipeline steps?▼

No, it is strictly read-only. It never edits files, commits, writes state.json, or runs another pipeline step, so its reports can be trusted as honest observations.

What happens when state.json is missing or malformed?▼

The skill falls back to inferring the state from the artifacts on disk, such as plan.md, reviews, and verdict files. It explicitly says the answer is inferred rather than recorded.

Why does status report commits after review on every finished run?▼

The adjudication step commits its own accepted fixes after the lenses read the tree, so review.head always lags HEAD on completed runs. Only commits after verdict.head indicate genuinely unreviewed work.