template-drift

Detect drift across vendored project files against canonical ai-factory toolkit definitions.

4|Updated Jul 20, 2026

Search Tags:#workflow #templates #compliance #configuration #sync #drift

Ready to run

npx skills add https://github.com/highflame-ai/ai-factory --skill template-drift-highflame-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: template-drift
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/template-drift
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill template-drift-highflame-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of configuration drift where local project files like templates, partials, and workflow runtimes diverge from the canonical toolkit versions, leading to inconsistent development practices and outdated constitutions.

Core Features & Use Cases

Multi-Surface Drift Detection: Monitors five distinct sync surfaces including templates, partials, ETHOS, workflow runtimes, and legacy test files.
Intentional vs. Accidental Classification: Distinguishes between project-specific customizations that should be preserved and accidental staleness that requires reconciliation.
Use Case: Use this when you suspect your project's local workflow or ETHOS constitution has fallen behind the latest ai-factory standards or when you need to verify if your local templates are still aligned with the toolkit.

Quick Start

Run the template drift skill to check if your project templates and workflow runtime are out of sync with the toolkit.

Frequently Asked Questions about template-drift

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

FAQPage Schema

What is configuration drift in project templates and how does it happen?▼

Configuration drift happens when local project templates, partials, and workflow runtimes diverge from canonical toolkit versions, leading to inconsistent development practices and outdated ETHOS constitutions across projects.

How do I check if my local workflow runtime is out of sync with the toolkit?▼

Run a diff-based validation against the local ai-factory symlink to detect and report drift across vendored project files, checking if templates and workflow runtimes are out of sync with toolkit standards.

How can I distinguish intentional customizations from accidental template staleness?▼

Use drift classification to distinguish between project-specific customizations that should be preserved and accidental staleness that requires reconciliation against the canonical toolkit definitions.

Does template drift detection require specific shell environments or dependencies?▼

Yes, it requires POSIX-compliant shell utilities and access to the local ai-factory symlink to perform diff-based validation and reconciliation across software engineering projects using the ai-factory framework.

What project surfaces are monitored for template and configuration drift?▼

Multi-surface drift detection monitors five distinct sync surfaces including templates, partials, ETHOS constitutions, workflow runtimes, and legacy test files to ensure consistency with canonical toolkit definitions.

When should I run template drift detection on my project configurations?▼

Run drift detection when you suspect local workflow or ETHOS constitutions have fallen behind latest ai-factory standards, or when you need to verify if local templates remain aligned with the toolkit.