track-pending

What problem does it solve?

It prevents scope drift and lost context by giving deferred follow-ups a consistent, repository-root home instead of scattering them into TODO comments or ad-hoc notes.

Core Features & Use Cases

• Creates a bounded pending ledger: Writes structured entries into walter-pending.md at the repo root so future self can find what to do next.
• Standardizes entry metadata and triggers: Uses strict frontmatter fields (e.g., severity, area, created, defer-until, owner) to support predictable review and cleanup.
• Improves planning and review hygiene: Separates out-of-scope follow-ups from the current PR while keeping the why and the trigger phrase tied to the work context.

Quick Start

Use the instruction "Track this follow-up by writing a new TP entry in walter-pending.md with the correct type, severity, area, created date, and defer-until condition."