plan-drift

Traces requirements to stories bidirectionally and reports coverage gaps and drift.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill plan-drift-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-drift
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/plan-drift
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill plan-drift-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In a markdown-based project pipeline, requirements in PRDs, epics, and features can silently lose coverage or diverge from the stories that implement them, and nobody notices until late. This Skill audits both directions of the traceability chain and surfaces gaps and drift as an advisory report. ## Core Features & Use Cases - Requirement-to-story coverage mapping: Inventories every PRD key requirement, epic In-scope bullet, and feature acceptance criterion, then checks each has at least one covering story. - Story-to-requirement fidelity check: Compares each story's acceptance criteria against its linked source requirement and flags scope-adds, scope-drops, reinterpretations, and stale requirement sources. - Dated advisory report: Writes a single PLAN-DRIFT-<date>.md report under 41-Reports/audits/ without ever editing stories, requirements, or status fields. - Use Case: Before closing a PRD-backed epic, run a plan-drift pass over the whole repo to confirm every requirement is traced to a story and no story has drifted from its source. ## Quick Start Ask the assistant to run a plan-drift check over the whole repo to audit requirement coverage and story fidelity.

Frequently Asked Questions about plan-drift

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

FAQPage Schema
How do I check requirement coverage across PRDs and stories?

Run a plan-drift pass over the whole repo or a named epic. It inventories every PRD key requirement, epic In-scope bullet, and feature acceptance criterion, then traces each through the existing linkage chain to find stories that cover it, reporting any gaps.

How to detect scope creep in user stories against requirements?

The fidelity check compares each story's acceptance criteria against the requirement its PRD reference resolves to. It flags scope-adds, scope-drops, reinterpretations, and stale source requirements as advisory findings for human review.

Does plan-drift modify stories or requirement documents?

No, it is strictly read-only. The only file it writes is a dated report under 41-Reports/audits/, and it never edits stories, PRDs, epics, features, or any status field.

Can I run plan-drift on a single epic instead of the whole repo?

Yes, you can scope the run to a named epic, which restricts the requirement inventory to that epic's PRD, its In-scope bullets, and the features and stories under it. The whole-repo run is the thorough default.

What happens if a requirement folder is empty during the audit?

The report explicitly states in its Scope section that the resolved requirement folder was empty rather than silently reporting a clean pass. An empty inventory is treated as a failure mode because it looks identical to full coverage.