status

To validate state.yaml consistency, this skill reads the file and cross-references it against on-disk artifacts. It checks the status cascade from work items to intents and runs, surfacing any orphaned or missing items for remediation.

Checking FIRE project status involves reading state.yaml to display project details like workspace and autonomy version. The skill then scans the filesystem to surface integrity issues, providing interactive remediation paths and an audit trail.

Finding orphaned artifacts requires scanning the filesystem for existing work items, intents, and runs, then comparing them against state.yaml. The skill surfaces these mismatches and presents actionable remediation options to resolve the orphaned files.

Yes, the FIRE status validation skill operates without external dependencies. It functions independently by reading state.yaml and scanning the local filesystem to report project status, validate integrity, and present remediation paths.

State.yaml may show missing work items during validation when on-disk artifacts do not match the recorded state. The skill detects these inconsistencies by applying the status cascade across disk and state representations, then offers remediation options.

Yes, you can use this skill to monitor workflows with intents and runs across disk. It enforces authoritative status by reading state.yaml, scanning for artifacts, and presenting findings with interactive remediation paths suitable for automation.