fabriqaai/specs.md/status
Claude Code and agent skill by fabriqaai/specs.md
- community
Checking that the SKILL.md file is still in the repository.
Display current FIRE project status and validate integrity of intents, work items, and runs.
Install
npx vskill@latest install fabriqaai/specs.md/statusSKILL.md
<objective> Display current FIRE project status and validate integrity across state.yaml and file system. Detect inconsistencies and offer interactive resolution. </objective>
<triggers>
- User runs
/specsmd-fire status - User asks "what's the status?"
- User asks to "check" or "validate" the project state
</triggers>
<degrees_of_freedom> LOW — Report facts accurately. Never auto-fix without user confirmation. </degrees_of_freedom>
<llm critical="true"> <mandate>NEVER auto-fix inconsistencies — ALWAYS ask user first</mandate> <mandate>ALWAYS scan file system — state.yaml may be incomplete</mandate> <mandate>Report ALL findings before offering fixes</mandate> <mandate>state.yaml is source of truth for status — frontmatter may be stale</mandate> </llm>
<flow> <step n="1" title="Read State"> <action>Read .specs-fire/state.yaml</action> <check if="state.yaml not found"> <output>No FIRE project found. Run /specsmd-fire to initialize.</output> <exit/> </check> </step>
<step n="2" title="Display Status"> <output> # FIRE Status
Project: {project.name} Workspace: {workspace.type} / {workspace.structure} Autonomy: {workspace.autonomy_bias} Version: {project.fire_version}
## Intents
{for each intent} ### {intent.title} [{intent.status}]
| Work Item | Status | Complexity | Mode |
|---|
{for each work_item}
{/for}
{/for}
## Active Runs
{if runs.active is array and has items} {for each active_run in runs.active}
- Run: {active_run.id} | Scope: {active_run.scope}
- Current Item: {active_run.current_item}
- Started: {active_run.started}
{/for} {else if active_run exists (legacy singular)}
- Run: {active_run.id}
- Work Item: {active_run.work_item}
- Started: {active_run.started}
{else} No active run. {/if}
## Quick Stats
- Intents: {total_intents} ({completed_intents} completed)
- Work Items: {total_work_items} ({completed_work_items} completed)
- Runs: {total_runs} completed
</output> </step>
<!-- ═══════════════════════════════════════════════════════════════════════════ --> <!-- INTEGRITY VALIDATION (NEW) --> <!-- ═══════════════════════════════════════════════════════════════════════════ -->
<step n="3" title="Scan File System"> <critical> File system may have artifacts not tracked in state.yaml. state.yaml may reference artifacts that no longer exist on disk. </critical>
<substep n="3a" title="Scan Intents"> <action>Glob: .specs-fire/intents/*/brief.md</action> <action>Extract intent IDs from directory names</action> <action>Store as: intents_on_disk[]</action> </substep>
<substep n="3b" title="Scan Work Items"> <action>Glob: .specs-fire/intents//work-items/.md</action> <action>Exclude design docs (*-design.md)</action> <action>Extract work item IDs and parent intents</action> <action>Store as: work_items_on_disk[]</action> </substep>
<substep n="3c" title="Scan Runs"> <action>Glob: .specs-fire/runs/run-*/run.md</action> <action>Extract run IDs from directory names</action> <action>For each run, check which artifacts exist:</action> <substep>plan.md, test-report.md, review-report.md, walkthrough.md</substep> <action>Store as: runs_on_disk[] with artifact_flags</action> </substep> </step>
<step n="4" title="Compare File System vs State"> <substep n="4a" title="Find Orphaned Artifacts (on disk but not in state)"> <action>Compare intents_on_disk with state.intents</action> <action>Compare work_items_on_disk with state work_items</action> <action>Compare runs_on_disk with state.runs.completed + state.runs.active</action>
<check if="intent on disk but not in state"> <add_issue type="orphaned_intent" severity="warning"> Intent '{id}' exists on disk but not tracked in state.yaml </add_issue> </check>
<check if="work item on disk but not in state"> <add_issue type="orphaned_work_item" severity="warning"> Work item '{id}' exists on disk but not tracked in state.yaml </add_issue> </check>
<check if="run folder on disk but not in state"> <add_issue type="orphaned_run" severity="warning"> Run '{id}' exists on disk but not tracked in state.yaml </add_issue> </check> </substep>
<substep n="4b" title="Find Missing Files (in state but not on disk)"> <check if="intent in state but no brief.md on disk"> <add_issue type="missing_intent_file" severity="error"> Intent '{id}' tracked but brief.md not found on disk </add_issue> </check>
<check if="work item in state but no .md file on disk"> <add_issue type="missing_work_item_file" severity="error"> Work item '{id}' tracked but file not found on disk </add_issue> </check>
<check if="completed run in state but no folder on disk"> <add_issue type="missing_run_folder" severity="error"> Run '{id}' marked complete but folder not found on disk </add_issue> </check> </substep> </step>
<step n="5" title="Validate Status Cascade"> <critical> Status must cascade correctly:
- Run completes work item → work item should be "completed"
- All work items completed → intent should be "completed"
- Any work item in_progress → intent should be "in_progress"
</critical>
<substep n="5a" title="Work Item Status Check"> <action>For each work item in state:</action>
<check if="work item in runs.completed but status != completed"> <add_issue type="status_mismatch" severity="error"> Work item '{id}' was completed in run '{run_id}' but status is '{current_status}' Expected: completed </add_issue> </check>
<check if="work item in runs.active as current_item but status != in_progress"> <add_issue type="status_mismatch" severity="warning"> Work item '{id}' is currently executing in run '{run_id}' but status is '{current_status}' Expected: in_progress </add_issue> </check>
<check if="work item status is completed but not found in any completed run"> <add_issue type="status_unverifiable" severity="warning" needs_code_check="true"> Work item '{id}' marked as completed but no completed run found May have been done outside FIRE or run data is missing </add_issue> </check> </substep>
<substep n="5b" title="Intent Status Check"> <action>For each intent in state:</action>
<derive_expected_status> IF any work_item.status == "in_progress": expected = "in_progress" ELSE IF all work_items.status == "completed": expected = "completed" ELSE IF all work_items.status == "pending": expected = "pending" ELSE: # mixed pending/completed expected = "in_progress" </derive_expected_status>
<check if="intent.status != expected_status"> <add_issue type="intent_status_mismatch" severity="error"> Intent '{title}' has status '{current}' but should be '{expected}' Based on work item statuses: {breakdown} </add_issue> </check> </substep> </step>
<step n="6" title="Validate Run Artifact Completeness"> <substep n="6a" title="Check Completed Runs"> <action>For each run in runs.completed (or runs_on_disk marked complete):</action>
<required_artifacts>
- run.md (mandatory)
- plan.md (mandatory for all modes)
- test-report.md (mandatory after tests)
- walkthrough.md (mandatory after completion)
</required_artifacts>
<optional_artifacts>
- review-report.md (created by code-review skill)
</optional_artifacts>
<check if="completed run missing required artifact"> <add_issue type="incomplete_run_artifacts" severity="warning"> Run '{id}' is marked complete but missing: {missing_artifacts} </add_issue> </check> </substep>
<substep n="6b" title="Check Active Runs"> <action>For each run in runs.active:</action>
<check if="active run folder does not exist"> <add_issue type="active_run_missing" severity="error"> Active run '{id}' has no folder on disk Run may have been deleted or never initialized properly </add_issue> </check>
<check if="active run has no run.md"> <add_issue type="active_run_corrupted" severity="error"> Active run '{id}' folder exists but run.md is missing Run initialization may have failed </add_issue> </check> </substep> </step>
<step n="7" title="Detect Stale Runs"> <action>For each run in runs.active[]:</action> <action>Calculate age: now - run.started</action>
<check if="active run started more than 24 hours ago"> <add_issue type="stale_run" severity="info" needs_user_decision="true"> Active run '{id}' was started {age} ago Current item: {current_item} Artifacts present: {artifact_list} May be abandoned or work was done outside FIRE </add_issue> </check>
<check if="active run has plan.md but no test-report.md and age > 1 hour"> <add_issue type="interrupted_run" severity="warning" needs_user_decision="true"> Run '{id}' appears interrupted mid-execution Has: plan.md Missing: test-report.md, walkthrough.md Execution may have been stopped before completion </add_issue> </check> </step>
<step n="8" title="Check Frontmatter Sync"> <note>state.yaml is source of truth. Frontmatter may drift.</note>
<action>For each work item with status in state.yaml:</action> <action>Read work item file, parse frontmatter</action>
<check if="frontmatter.status != state.yaml.status"> <add_issue type="frontmatter_drift" severity="info"> Work item '{id}' frontmatter says '{frontmatter_status}' but state.yaml says '{state_status}' state.yaml is authoritative </add_issue> </check> </step>
<step n="9" title="Report Findings"> <check if="no issues found"> <output> ## ✅ Integrity Check Passed
All artifacts are consistent:
- {intent_count} intents tracked and verified
- {work_item_count} work items with correct status
- {run_count} runs with complete artifacts
- No orphaned or missing files detected
</output> <exit/> </check>
<check if="issues found"> <output> ## ⚠️ Integrity Issues Detected
Found {issue_count} issue(s) requiring attention:
| # | Type | Location | Issue | Suggested Fix |
|---|
{for each issue, numbered}
{/for}
Severity: 🔴 Error | 🟡 Warning | 🔵 Info
### Actions
[1] fix-all — Apply all recommended fixes automatically [2] review — Go through each issue one by one [3] skip — Continue without fixing {if any issue has needs_code_check} [4] check-code — Verify by inspecting the codebase {/if}
Choose an action [1/2/3{if check-code available}/4{/if}]: </output> </check> </step>
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingsrc/flows/fire/agents/orchestrator/skills/status/SKILL.md
Popularity
- Repository stars
- 176
- Repository forks
- 19
- 7-day trend score
- 26
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 22 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/fabriqaai/specs.md/status)