design-drift

Detect design documentation drift by extracting assertions and verifying codebase alignment.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill design-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-drift
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/design-drift
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill design-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and surfaces mismatches between a project's design documentation and its codebase to replace manual, ad-hoc checks with a structured audit that highlights aligned, drifted, partial, and unresolved assertions.

Core Features & Use Cases

  • Structured assertion extraction: mechanically extracts verification assertions from standardized project docs and maps them to code checks.
  • Agent-driven verification & flow tracing: dispatches a design-drift auditor and optional flow-tracer agents to validate call chains and produce hop-by-hop traces with file:line references.
  • Modes & remediation: supports full scans or focused audits by category or document, handles truncated agent runs, aggregates summary statistics, and provides repair recommendations or decision-point prompts for user approval.

Quick Start

Check for design drift across the repository and trace any flagged call flows to produce a consolidated drift report.

Frequently Asked Questions about design-drift

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

FAQPage Schema
How do I detect drift between design documentation and my codebase?

To detect design drift, you can extract assertions from standardized project docs and verify implementation alignment. This Skill dispatches auditor agents to check the code, categorizes findings as aligned, drifted, partial, or unresolved, and surfaces remediation recommendations.

How does assertion extraction work for code audits?

Assertion extraction mechanically parses standardized design documents to derive verification assertions and maps them to code checks. This replaces manual, ad-hoc reviews with a structured audit that dispatches agents to validate implementation alignment.

Can I run a focused code audit on a specific design document or category?

Yes, you can run focused code audits by category or specific document instead of a full scan. This allows targeted verification of implementation alignment and optional flow-trace follow-ups for specific call chains.

What is flow tracing and when do I need it for design drift detection?

Flow tracing validates call chains by producing hop-by-hop traces with file:line references. You need it as a follow-up when design drift detection flags mismatches, allowing you to pinpoint exactly where the code diverges from the design docs.

Do I need standardized design docs to check for design drift?

Yes, standardized design documents are required. The Skill mechanically extracts verification assertions from these docs and maps them to code checks, so projects without standardized documentation cannot be audited for implementation alignment.

How do I handle truncated agent runs during a design audit?

The Skill handles truncated agent runs by aggregating available summary statistics and surfacing partial results. It provides repair recommendations or decision-point prompts for user approval, ensuring you still get actionable drift status counts.