aming-claw-drift-demo

Name: aming-claw-drift-demo
Availability: InStock
Author: Aming

Detect and demonstrate documentation drift during observer sessions.

26|5|Updated Feb 28, 2026

Search Tags:#documentation #ai #dashboard #evidence #docs-drift #drift-demo #observer-session

Ready to run

npx skills add https://github.com/amingclawdev/aming-claw --skill aming-claw-drift-demo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aming-claw-drift-demo
Source: https://github.com/amingclawdev/aming-claw/tree/main/skills/aming-claw-drift-demo
Command: npx skills add https://github.com/amingclawdev/aming-claw --skill aming-claw-drift-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Public demo to illustrate how feature changes can outpace documentation, surfacing drift state so teams can address docs quickly during an observer session.

Core Features & Use Cases

Drift visualization: shows where docs are stale relative to features.
Evidence collection: gathers dashboard evidence and backlog references.
Observer-guided testing: supports running, previewing, or collecting drift evidence with Claude Codex sessions.

Quick Start

Run the drift demo fixture to initialize a test project and simulate docs drift with an active observer session.

Frequently Asked Questions about aming-claw-drift-demo

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

FAQPage Schema

How do I detect documentation drift between feature changes and stale docs?▼

Documentation drift is detected by comparing current feature states against existing docs to surface staleness. This skill visualizes where documentation has fallen behind feature updates, generating a drift state for review during an observer session.

What is docs drift detection and when do I need to run it?▼

Docs drift detection identifies mismatches between updated features and outdated documentation. You need to run it when features change rapidly and reviewers require visual evidence and backlog references to prioritize documentation updates.

How do I collect evidence of documentation drift using an observer session?▼

To collect drift evidence, run the drift demo fixture to initialize a test project and simulate docs drift. This gathers dashboard evidence and backlog references within an active observer session for reviewer analysis.

Can I preview documentation drift state without setting up a full production environment?▼

Yes, you can preview documentation drift state without a full production environment. The skill provides a live demo fixture that initializes a test project to simulate and visualize drift locally during an observer session.

Does this docs drift detection demo require any external dependencies or components?▼

This docs drift detection demo requires no external dependencies or components to run. It operates independently by initializing its own test project fixtures to simulate feature changes and documentation staleness.