state-check

Cross-reference workflow state files, directories, and run logs to report inconsistencies.

3|3|Updated Aug 19, 2024
One-click install
npx skills add https://github.com/AMDResearch/dh_comms --skill state-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-check
Source: https://github.com/AMDResearch/dh_comms/tree/main/.agents/skills/state-check
Command: npx skills add https://github.com/AMDResearch/dh_comms --skill state-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain integrity of workflow and project state by detecting orphan workflows, mismatched state entries, stale handoffs, and empty run-logs.

Core Features & Use Cases

  • Cross-reference active-workflows.md with lifecycle directories to identify mismatches.
  • Validate dossier lifecycle states against their directory locations and confirm current-focus references exist.
  • Detect stale handoffs and empty run-logs and generate a concise results summary.

Quick Start

Run the state-check skill after completing a workflow or at session start to validate all state documents and surface inconsistencies.

Frequently Asked Questions about state-check

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

FAQPage Schema
How do I verify workflow state consistency across lifecycle directories?

Workflow state consistency is verified by cross-referencing active-workflows.md with lifecycle directories and dossier metadata. This detects orphan workflows and mismatched entries to ensure project alignment.

What causes mismatched state entries in active-workflows.md?

Mismatched state entries occur when workflow files in lifecycle directories like active/ or done/ are moved without updating the active-workflows.md table, creating orphan workflows and stale handoff records.

How do I detect stale handoffs and empty run-logs in my project?

Detect stale handoffs and empty run-logs by running a state validation check that reads current-focus.md and dossier metadata. This surfaces inconsistencies and produces a structured summary of stale entries.

When should I run a state consistency check on my workflow directories?

Run a state consistency check after completing a workflow or at session start. This validates all state documents, confirms current-focus references exist, and surfaces any inconsistencies before starting new work.

Can I validate dossier lifecycle states against their directory locations?

Yes, you can validate dossier lifecycle states by cross-referencing their metadata against their actual directory locations across lifecycle folders. This confirms alignment and flags mismatches in the structured summary.