drift

Bind markdown specs to code and detect stale anchors.

78|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/fiberplane/otter --skill drift-fiberplane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift
Source: https://github.com/fiberplane/otter/tree/main/.agents/skills/drift
Command: npx skills add https://github.com/fiberplane/otter --skill drift-fiberplane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift binds markdown specs to code and lints for staleness. When specs describe bound code, anchors can drift, leading to misleading context in future sessions.

Core Features & Use Cases

  • Anchor binding and provenance checks to ensure specs reference the correct code.
  • Staleness detection across drift-bound files to surface outdated prose.
  • Use in workflows after code changes: refresh provenance with drift link and re-check anchors.

Quick Start

Run drift check to identify stale anchors and refresh provenance.

Frequently Asked Questions about drift

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

FAQPage Schema
How do I keep markdown specs synchronized with code after refactoring?

To keep specs synchronized with code, bind markdown specs to code using frontmatter-driven linking and enforce provenance. This prevents stale anchors from providing misleading context in future sessions after code changes.

What is anchor provenance and how does it detect spec staleness?

Anchor provenance verifies that markdown specs reference the correct code. Staleness detection runs across drift-bound files to surface outdated prose when anchors drift from the bound code they describe.

How do I check for stale anchors and refresh provenance after code changes?

Run drift check to identify stale anchors and refresh provenance. Use this in workflows after editing bound code or updating drift frontmatter to re-check anchors and keep specs synchronized.

Do I need frontmatter in my markdown files to enable drift binding?

Yes, drift binding relies on frontmatter-driven linking to connect markdown specs to code. The frontmatter establishes the links required to enforce anchor provenance and perform automated staleness checks.

Why do my spec anchors provide misleading context in future sessions?

Spec anchors provide misleading context when they drift from the bound code they describe. Without provenance enforcement, editing bound code causes staleness, making the prose outdated and inaccurate.