exigere

To remove deferred-work language from code comments, scan your codebase for deferral phrases and replace them with concrete present-work statements. You must also attach named arc-tracking references to any remaining future-work items for traceability.

Deferred-work language in documentation consists of vague deferral phrases that signal future intent without accountability. It causes misalignment between stated intent and present work, making it difficult to track what actually needs to be done.

Enforce completion-honesty in READMEs and design notes by detecting deferral phrases and requiring explicit arc-tracking references. This surfaces present-work versus future-work, guiding teams toward concrete statements over vague commitments.

Yes, you can use code-quality checks to flag TODO comments and deferral phrases across software codebases, inline comments, READMEs, and design notes. This enforces a consistent review workflow by surfacing these patterns for immediate correction.

The best way to track future work without vague deferral phrases is to replace them with explicit arc-tracking references. This ensures traceability and accountability by attaching a named arc to any remaining future-work items in your comments.

You should not use arc-tracking for deferred work when the comment represents a present-work statement rather than future-work. The goal is to drive out deferral language entirely, so only attach named arcs to genuinely pending tasks that cannot be completed now.