GLOSSARY
These are the failure modes Motionode detects—spec drift, requirements drift, missing requirements, scope impact, and more. Each term links to resource pages and tools so you can diagnose problems and fix them with the same vocabulary your team uses.
Jump to a term by letter.
When the agreed spec, requirements, or context and the actual plan or code fall out of sync.
When the written spec and the planned or built implementation diverge.
Where comments, versions, or decisions change the requirements but not the plan.
Context (PRD, tickets, decisions) evolves and the execution context doesn’t.
The slice of spec and code context that belongs to a single ticket or task.
Checks that keep specs, requirements, and code aligned and complete before and during build.
Verifying that implementation matches the spec and flagging gaps.
Scoring whether a PRD or SOW is build-ready and what’s missing.
Gaps in roles, flows, or constraints that cause rework and misalignment.
From PRD to execution plan, scope change impact, and dependency-based forecasting.