task-manager

To triage tasks from a brain dump file, this Skill maps chaotic inputs from BRAIN_DUMP.md to a prioritized TASK_MASTER.md ledger. It uses deterministic routing rules to categorize tasks, clear the inbox, and generate structured rows.

The best way to prioritize bugs and features in parallel is using a structured P0, P1, and P2 priority scheme. This Skill routes items into a TASK_MASTER ledger, tagging each with owner, date, and dependency data for clear ownership.

You can maintain Inbox Zero by applying automated guardrails that clear BRAIN_DUMP.md after populating TASK_MASTER.md. The Skill recovers gracefully from missing or ambiguous inputs to ensure your task ledger remains organized without manual cleanup.

Yes, this task triage approach works without external dependencies. It relies entirely on explicit input mappings and file I/O tooling to read BRAIN_DUMP.md and write prioritized tasks directly to TASK_MASTER.md.

In a deterministic task-management workflow, completed tasks are archived by moving their rows to a bottom 'Completed' section in the TASK_MASTER ledger. This is governed by explicit completion rules within the file structure.

When automated task triage encounters ambiguous inputs, built-in guardrails trigger a graceful recovery. Instead of failing, the Skill attempts to resolve the ambiguity or safely skips the entry while continuing to populate the ledger.