daily-todos

To convert rough tasks into a codebase-referenced TODO plan, you record incoming work requests so the system can cross-reference repository documentation like module docs and architecture indexes. This process clarifies abstract tasks by suggesting specific entry points, related files, and implementation approaches.

Codebase-aware task concretization works by validating incoming work against existing repository artifacts such as onboarding indexes, module documentation, and business rules. Instead of guessing, it enforces clarification for abstract requests and maps tasks to specific codebase modules and architectural references.

Yes, you can track daily development tasks in a single markdown journaling file created at a deterministic path. The file organizes entries into morning plans, midday additions, and notes, applying auto-priority tagging with P1, P2, or P3 levels and task-type labels like development or analysis.

The best way to manage an overwhelming TODO backlog is using a daily tracker that applies priority tagging and flags backlog overflow situations. By assigning deterministic priority levels and reordering urgent items, the system ensures critical codebase tasks surface above less pressing daily additions.

Yes, you need repository documentation such as architecture indexes, module docs, and business rules to decompose abstract work requests. The system refuses to guess when input is too vague, enforcing clarification and requiring validated concretization using allowed file reading and searching tools.

Task tracking refuses to process vague incoming work requests to enforce safety guardrails and deterministic workflow constraints. Without sufficient context from codebase documentation, the system cannot accurately suggest module-specific entry points or approaches, so it requests clarification instead of generating generic suggestions.