detect-structure-drift

Detect structural drift across agent frontmatter, artifact manifest, and orchestrator reference documentation.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill detect-structure-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-structure-drift
Source: https://github.com/dimagi-internal/ace/tree/main/skills/detect-structure-drift
Command: npx skills add https://github.com/dimagi-internal/ace --skill detect-structure-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ACE plugin relies on three separate sources of truth for its lifecycle structure: agent frontmatter, the artifact manifest, and the orchestrator reference state schema. These sources can drift apart over time due to manual edits, missed updates when adding skills or phases, or inconsistent naming, leading to broken skill references, missing artifacts, and misconfigured phase workflows that are difficult to debug manually.

Core Features & Use Cases

  • Cross-source drift detection: Validates alignment between agent frontmatter, artifact manifest, and orchestrator reference documentation across 5 key checks.
  • Pre-release validation: Catches orphaned skill references, missing SKILL.md files, and mismatched phase vocabularies before they reach production.
  • Post-change verification: Confirms new skills are properly claimed, renamed phases are aliased correctly, and state schema stays in sync with agent and manifest definitions.
  • Use Case: Before releasing an update to the ACE plugin, run this skill to ensure no structural drift exists that would break the /ace:run lifecycle orchestration or the /system page display.

Quick Start

Use the detect-structure-drift skill to audit your ACE plugin checkout for structural inconsistencies between its core configuration sources.

Frequently Asked Questions about detect-structure-drift

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

FAQPage Schema
How do I check for structural drift in an ACE plugin configuration?

To check for structural drift in an ACE plugin configuration, validate alignment across agent frontmatter, artifact manifest, and orchestrator reference state schema to detect orphaned references, missing SKILL.md files, or mismatched phase vocabularies.

Why does my ACE plugin lifecycle orchestration break after renaming phases?

ACE plugin lifecycle orchestration breaks after renaming phases when state schema parity drifts from the agent frontmatter and artifact manifest, requiring a phase consistency audit to ensure renamed phases are aliased correctly across all configuration sources.

What is the best way to validate reachability of newly added skills before an ACE plugin release?

The best way to validate reachability of newly added skills before an ACE plugin release is to run a pre-release audit that verifies SKILL.md file existence, manifest producer claims, and orchestrator reference documentation alignment to prevent broken lifecycle workflows.

Can I audit state schema parity across agent frontmatter and orchestrator documentation?

Yes, you can audit state schema parity by cross-referencing agent frontmatter definitions against the orchestrator reference documentation and artifact manifest to identify inconsistencies that cause misconfigured phase workflows and missing artifacts.

How do I debug missing or misclassified skills in the ACE plugin system display?

Debug missing or misclassified skills in the ACE plugin system display by performing a cross-source drift detection audit that checks skill file existence and validates that manifest producer claims accurately reflect the agent frontmatter definitions.