triage-inbox

Review captured inbox ideas and promote them into area-prefixed tasks or drop them.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill triage-inbox-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-inbox
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/triage-inbox
Command: npx skills add https://github.com/toderian/project_template --skill triage-inbox-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Captured ideas pile up in a raw inbox (docs/tasks_manager/_inbox/) with no type, priority, or area assigned, making it hard to turn quick notes into committed, trackable work without a deliberate review pass. ## Core Features & Use Cases - Discovery gate: Scans inbox, archived ideas, active and archived tasks, roadmaps, docs, and code to classify each idea as duplicate, already tracked, already implemented, obsolete, related, or genuinely new before any task is created. - Decide and promote: Presents each idea with evidence so the user can promote, drop, defer, or append it to existing work; promoted ideas become well-formed area-prefixed tasks with Source ref back to the original I-NNN inbox entry. - Inbox hygiene and ledger sync: Archives promoted or dropped ideas into _inbox_archived/, optionally defines new areas with user confirmation, and runs at ledger sync, at ledger check, and at repos-check to keep ledgers consistent. - Use Case: After a week of jotting down ideas, ask the agent to triage the inbox; it reviews each I-NNN note, flags two as duplicates of existing tasks, and converts the rest into prioritized AUTH and API tasks with acceptance criteria. ## Quick Start Ask the agent to triage the inbox and turn my captured ideas into actionable tasks.

Frequently Asked Questions about triage-inbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn captured inbox ideas into actionable tasks?

Run the triage inbox workflow, which reviews each new idea in docs/tasks_manager/_inbox/, checks it against existing tasks and code, and promotes worthwhile ideas into area-prefixed tasks with type, priority, and acceptance criteria. Duplicates and obsolete ideas are dropped with a recorded reason.

How does the triage process avoid creating duplicate tasks?

Before promoting anything, a discovery gate scans the inbox, archived ideas, active and archived tasks, roadmaps, area pages, docs, and likely code and tests. Each idea is classified as duplicate, already tracked, already implemented, obsolete, related, or genuinely new, and the evidence is shown to you first.

What happens to inbox ideas after they are triaged?

Promoted ideas become tasks with Source ref pointing back to their I-NNN entry, and the inbox file is marked promoted and moved to docs/tasks_manager/_inbox_archived/. Dropped ideas are archived with a one-line reason, and deferred ideas stay untouched as new.

What prerequisites are needed before triaging the inbox?

The docs/tasks_manager/ directory must already be initialized in the repository. If it is missing, run at init --with-tasks first so the inbox, ledgers, and area structure exist before triage begins.

Can triage create a new task area if none fits an idea?

Yes. When no existing area fits a promoted idea, the workflow proposes a slug, uppercase prefix, one-line description, and page path, asks for your confirmation, appends it to docs/tasks_manager/_areas.md, and then uses it for the new task.