--- name: status description: Display current FIRE project status and validate integrity of intents, work items, and runs. version: 2.0.0 --- Display current FIRE project status and validate integrity across state.yaml and file system. Detect inconsistencies and offer interactive resolution. - User runs `/specsmd-fire status` - User asks "what's the status?" - User asks to "check" or "validate" the project state **LOW** — Report facts accurately. Never auto-fix without user confirmation. NEVER auto-fix inconsistencies — ALWAYS ask user first ALWAYS scan file system — state.yaml may be incomplete Report ALL findings before offering fixes state.yaml is source of truth for status — frontmatter may be stale Read .specs-fire/state.yaml No FIRE project found. Run `/specsmd-fire` to initialize. # 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} | {title} | {status} | {complexity} | {mode} | {/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 File system may have artifacts not tracked in state.yaml. state.yaml may reference artifacts that no longer exist on disk. Glob: .specs-fire/intents/*/brief.md Extract intent IDs from directory names Store as: intents_on_disk[] Glob: .specs-fire/intents/*/work-items/*.md Exclude design docs (*-design.md) Extract work item IDs and parent intents Store as: work_items_on_disk[] Glob: .specs-fire/runs/run-*/run.md Extract run IDs from directory names For each run, check which artifacts exist: plan.md, test-report.md, review-report.md, walkthrough.md Store as: runs_on_disk[] with artifact_flags Compare intents_on_disk with state.intents Compare work_items_on_disk with state work_items Compare runs_on_disk with state.runs.completed + state.runs.active Intent '{id}' exists on disk but not tracked in state.yaml Work item '{id}' exists on disk but not tracked in state.yaml Run '{id}' exists on disk but not tracked in state.yaml Intent '{id}' tracked but brief.md not found on disk Work item '{id}' tracked but file not found on disk Run '{id}' marked complete but folder not found on disk 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" For each work item in state: Work item '{id}' was completed in run '{run_id}' but status is '{current_status}' Expected: completed Work item '{id}' is currently executing in run '{run_id}' but status is '{current_status}' Expected: in_progress Work item '{id}' marked as completed but no completed run found May have been done outside FIRE or run data is missing For each intent in state: 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" Intent '{title}' has status '{current}' but should be '{expected}' Based on work item statuses: {breakdown} For each run in runs.completed (or runs_on_disk marked complete): - run.md (mandatory) - plan.md (mandatory for all modes) - test-report.md (mandatory after tests) - walkthrough.md (mandatory after completion) - review-report.md (created by code-review skill) Run '{id}' is marked complete but missing: {missing_artifacts} For each run in runs.active: Active run '{id}' has no folder on disk Run may have been deleted or never initialized properly Active run '{id}' folder exists but run.md is missing Run initialization may have failed For each run in runs.active[]: Calculate age: now - run.started Active run '{id}' was started {age} ago Current item: {current_item} Artifacts present: {artifact_list} May be abandoned or work was done outside FIRE Run '{id}' appears interrupted mid-execution Has: plan.md Missing: test-report.md, walkthrough.md Execution may have been stopped before completion state.yaml is source of truth. Frontmatter may drift. For each work item with status in state.yaml: Read work item file, parse frontmatter Work item '{id}' frontmatter says '{frontmatter_status}' but state.yaml says '{state_status}' state.yaml is authoritative ## ✅ 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 ## ⚠️ Integrity Issues Detected Found {issue_count} issue(s) requiring attention: | # | Type | Location | Issue | Suggested Fix | |---|------|----------|-------|---------------| {for each issue, numbered} | {n} | {severity_icon} | {location} | {description} | {fix_suggestion} | {/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}]: Skipping integrity fixes. Issues may cause unexpected behavior. For each issue with a fix: Read brief.md frontmatter, add intent to state.yaml with status: pending Read work item frontmatter, add to parent intent in state.yaml Parse run.md, determine if complete or incomplete If complete: add to runs.completed If incomplete: offer to add to runs.active or delete Remove intent from state.yaml (data loss warning) Or: Create placeholder brief.md from state data Update state.yaml status to expected value Update intent status in state.yaml Update work item frontmatter to match state.yaml Mark run as incomplete in state, or generate missing artifacts User must decide: resume, abandon, or check code ## Fixes Applied {for each fix applied} ✓ {description} {/for} {if any fixes skipped} ⏭️ Skipped (requires user decision): {for each skipped} - {description} {/for} {/if} For each issue: ## Issue {n} of {total} **Type**: {type} **Severity**: {severity} **Location**: {location} ### Details {full_description} ### Suggested Fix {fix_suggestion} --- **[y]** Apply fix **[n]** Skip this issue **[c]** Check codebase for this item **[q]** Quit review (remaining issues skipped) Choice [y/n/c/q]: Apply fix for this issue ✓ Fixed: {description} Invoke code check for this specific item code-check for {item} Review ended. {remaining} issues skipped. Continue to next issue This is a BEST EFFORT verification. AI will look for evidence but may not catch everything. User should confirm findings. I'll check the codebase for evidence that work items were completed. This involves reading work item acceptance criteria and looking for matching implementations. Which items should I check? {for each item with needs_code_check} **[{n}]** {work_item_title} {/for} **[a]** All items **[b]** Back to actions Choice: Read work item file: .specs-fire/intents/{intent}/work-items/{id}.md Extract acceptance criteria Extract expected files/endpoints/components mentioned Look for files mentioned in the work item description Example: "Create src/auth/login.ts" → check if file exists Look for test files for the component Pattern: {filename}.test.ts, {filename}.spec.ts, __tests__/{filename}.ts If file exists, do a quick scan for expected functions/classes Example: Work item mentions "login endpoint" → look for login handler ## Code Verification: {work_item_title} ### Expected (from acceptance criteria) {list acceptance criteria} ### Found in Codebase {for each check} {check_result_icon} {check_description} {/for} ### Assessment {if all checks pass} ✅ **Likely Complete** — Implementation evidence found Recommend: Mark as completed in state.yaml {else if some checks pass} 🟡 **Partially Complete** — Some evidence found Missing: {missing_items} Recommend: Review manually or continue implementation {else} ❌ **Not Found** — No implementation evidence Recommend: Keep as pending, implementation needed {/if} --- Apply this assessment? [y/n]: Update state.yaml based on assessment Append to .specs-fire/maintenance-log.md (create if needed): ## {ISO-8601-timestamp} - Integrity Check **Triggered by**: status skill validation | Issue | Fix Applied | Details | |-------|-------------|---------| {for each fix} | {type} | {fix_description} | {location} | {/for} --- Changes logged to: .specs-fire/maintenance-log.md ## Status Check Complete {if fixes applied} **Fixes Applied**: {fix_count} **Issues Remaining**: {remaining_count} {/if} {if all clean} ✅ Project state is consistent and ready for work. {else} ⚠️ Some issues remain unresolved. Run `/specsmd-fire status` again to review. {/if} --- **Next**: {suggest next action based on current state} | Type | Severity | Auto-fixable | Description | |------|----------|--------------|-------------| | orphaned_intent | warning | yes | Intent on disk but not in state.yaml | | orphaned_work_item | warning | yes | Work item on disk but not in state.yaml | | orphaned_run | warning | partial | Run folder on disk but not tracked | | missing_intent_file | error | partial | Intent in state but file missing | | missing_work_item_file | error | partial | Work item in state but file missing | | missing_run_folder | error | no | Completed run in state but folder missing | | status_mismatch | error | yes | Work item status doesn't match run history | | status_unverifiable | warning | no | Status can't be verified from run data | | intent_status_mismatch | error | yes | Intent status inconsistent with work items | | incomplete_run_artifacts | warning | partial | Run missing required artifacts | | active_run_missing | error | no | Active run folder doesn't exist | | active_run_corrupted | error | no | Active run folder missing run.md | | stale_run | info | no | Active run is old, may be abandoned | | interrupted_run | warning | no | Run appears stopped mid-execution | | frontmatter_drift | info | yes | Frontmatter status differs from state | ``` # FIRE Status **Project**: my-saas-app **Workspace**: brownfield / monolith **Autonomy**: balanced **Version**: 0.1.8 ## Intents ### User Authentication [in_progress] | Work Item | Status | Complexity | Mode | |-----------|--------|------------|------| | login-endpoint | completed | medium | confirm | | session-management | in_progress | medium | confirm | | password-reset | pending | high | validate | ## Active Runs - **Run**: run-fabriqa-2026-002 | **Scope**: single - **Current Item**: session-management - **Started**: 2026-01-19T10:30:00Z ## Quick Stats - Intents: 1 (0 completed) - Work Items: 3 (1 completed) - Runs: 1 completed --- ## ⚠️ Integrity Issues Detected Found 3 issue(s) requiring attention: | # | Type | Location | Issue | Suggested Fix | |---|------|----------|-------|---------------| | 1 | 🟡 | run-fabriqa-2026-002 | Run started 3 days ago, may be stale | Resume or abandon | | 2 | 🔵 | login-endpoint | Frontmatter says 'pending' but state says 'completed' | Sync frontmatter | | 3 | 🟡 | analytics-dashboard.md | Work item on disk but not tracked | Add to state.yaml | **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 **[4] check-code** — Verify by inspecting the codebase Choose an action [1/2/3/4]: ``` State file read successfully All intents and work items displayed Active run status shown Quick stats accurate File system scanned for all artifacts Orphaned artifacts detected (disk → state) Missing files detected (state → disk) Status cascade validated (work items → intents) Run artifact completeness checked Stale/interrupted runs detected Frontmatter sync checked Issues reported in clear table format User given choice: fix-all, review, skip, check-code Fixes logged to maintenance-log.md Code verification available for ambiguous cases

status

Install this skill

Comments