status

Validate FIRE project integrity by comparing state.yaml against the file system.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/AzrinPutra/schedulerv2 --skill status-azrinputra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/AzrinPutra/schedulerv2/tree/main/.specsmd/fire/agents/orchestrator/skills/status
Command: npx skills add https://github.com/AzrinPutra/schedulerv2 --skill status-azrinputra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the consistency and integrity of your FIRE project's state by comparing tracked information in state.yaml against the actual files and artifacts present on your file system. It detects and helps resolve inconsistencies, preventing potential errors and data loss.

Core Features & Use Cases

  • Project Status Overview: Provides a clear, consolidated view of your project's intents, work items, and active runs.
  • Integrity Validation: Scans the file system to identify orphaned files, missing artifacts, and status mismatches between state.yaml and disk.
  • Status Cascade Check: Verifies that work item statuses correctly roll up to intent statuses.
  • Run Artifact Verification: Ensures that completed runs have all necessary associated files.
  • Interactive Resolution: Offers options to automatically fix detected issues, review them one by one, or skip them.

Quick Start

Run /specsmd-fire status to check the current FIRE project status and validate its integrity.

Frequently Asked Questions about status

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

FAQPage Schema
How do I validate FIRE project integrity against the file system?

Run a status check to compare state.yaml against your file system, detecting orphaned artifacts, missing files, and status mismatches across intents, work items, and runs. It offers interactive resolution options to fix the detected inconsistencies.

What causes orphaned artifacts and missing files in state management?

Orphaned artifacts and missing files occur when state.yaml tracking falls out of sync with the actual file system. Integrity validation scans for these mismatches, preventing potential errors and data loss by identifying incomplete run artifacts and incorrect status cascades.

How do I fix status mismatches between state.yaml and disk?

Fix status mismatches by running an interactive resolution process that compares state.yaml to the file system. You can automatically fix detected issues, review and resolve them one by one, or skip them entirely based on your project needs.

Does the status check verify work item statuses roll up to intent statuses?

Yes, the status check performs a status cascade check to verify that work item statuses correctly roll up to intent statuses. This ensures your FIRE project maintains accurate hierarchical state tracking across all levels.

What is the best way to ensure completed runs have all necessary associated files?

Run artifact verification scans completed runs to ensure all necessary associated files are present on the file system. This validation step prevents incomplete run artifacts from causing data inconsistencies or errors in your FIRE project.

What are the limitations of automated integrity validation for FIRE projects?

Integrity validation relies on comparing state.yaml to the file system, so it cannot detect issues within untracked files or resolve semantic errors in project logic. Users must interactively choose to apply automatic fixes or manually review detected mismatches.