What problem does it solve? When decomposing accepted specifications into implementation plans, forward-looking obligations (deferred requirements, approval gates, retention or migration duties) often sit outside the primary interface sections and silently disappear from task breakdowns. This Skill ensures every such obligation is inventoried, traced to a plan task or an explicit justified deferral, and verified before the plan is treated as executable. ## Core Features & Use Cases - Forward-Obligation Scan: Searches full governing sources (specifications, amendments, decision records) for forward-looking language and records each hit in an obligation register with source, owner, trigger, and disposition. - Authority Boundary Check: Verifies that every gate ID and dispatchable stage in a plan resolves to an accepted decision-register entry, failing plans that mint authority from proposed or reviewer-only records. - Interface Verification: Requires every named seam (function, schema, runtime call) to be confirmed against the actual file with a path:line citation, or the plan is marked interface-unverified as a dispatch blocker. - Caller-Inventory Closure: Enforces registry-aware transitive closure for "no other caller" claims, with runtime negatives for protected entries. - Use Case: Before decomposing a multi-document ARS/TDL specification into work packages, run this scan to surface deferred obligations and unresolved approval gates so the master plan closes them explicitly. ## Quick Start Use the writing-plans-extras skill to scan my accepted specification documents and draft plan for deferred obligations, unverified interfaces, and unresolved approval gates before task decomposition.
