status

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

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/phra/Antigravity-Discord-Bridge --skill status-phra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/phra/Antigravity-Discord-Bridge/tree/main/.specsmd/fire/agents/orchestrator/skills/status
Command: npx skills add https://github.com/phra/Antigravity-Discord-Bridge --skill status-phra

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 with the actual file system, detecting and helping to resolve inconsistencies.

Core Features & Use Cases

  • Comprehensive Status Reporting: Displays current project, workspace, and autonomy settings.
  • Integrity Validation: Scans for orphaned files, missing artifacts, and status mismatches between state.yaml and the file system.
  • Interactive Resolution: Offers automated fixes, guided review, or code verification for detected issues.
  • Use Case: Before starting a new development cycle, run /specsmd-fire status to ensure all previous work items are correctly marked as complete, all necessary files exist, and no stray files are cluttering the project directory.

Quick Start

Run the command /specsmd-fire status to check the current project's integrity.

Frequently Asked Questions about status

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

FAQPage Schema
How do I validate project integrity and check for orphaned files?

To validate project integrity, run a status check to compare the state.yaml file against the file system, detecting orphaned artifacts, missing files, and status mismatches while offering interactive resolution options.

Why does my state.yaml file have status mismatches with the file system?

Status mismatches between state.yaml and the file system occur when tracked work items are not correctly marked as complete or when files are manually moved or deleted outside of the automated workflow.

How do I fix stale runs and missing artifacts in my project state?

Fix stale runs and missing artifacts by running an integrity validation scan, which identifies inconsistencies and provides interactive options for automated fixing, manual review, or code verification.

What's the best way to scan a file system for project inconsistencies?

The best way to scan for project inconsistencies is to validate the state.yaml file against the actual file system, detecting orphaned files, missing artifacts, and status mismatches before starting a new development cycle.

Can I automate fixing orphaned artifacts detected during a state check?

Yes, you can automate fixing orphaned artifacts by using the interactive resolution options provided after the integrity validation scan detects inconsistencies between your state file and file system.

When should I run a state management check on my project?

You should run a state management check before starting a new development cycle to ensure all previous work items are correctly marked as complete, necessary files exist, and no stray files clutter the directory.