Help us improve
Share bugs, ideas, or general feedback.
From jd
Generate a prioritized "what do I need to do next?" report by aggregating tasks, inbox items, and review items across Johnny.Decimal systems. Use this skill when the user wants a daily overview, needs to decide what to work on next, or says things like "what do I need to do next," "what's on my plate," "show my priorities," "what needs attention," "daily overview," "action dashboard," "what should I focus on," "what's urgent," "where should I start," "what's most important right now," or "give me a status report." Also trigger when the user asks "what's coming up," "what's ahead this week," or "anything I'm forgetting."
npx claudepluginhub ngerakines/jd --plugin jdHow this skill is triggered — by the user, by Claude, or both
Slash command
/jd:jd-next-actionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill creates a unified, prioritized view of everything requiring attention
Conducts a structured weekly review to clear inboxes, review projects, capture next actions, and set priorities for the coming week.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
This skill creates a unified, prioritized view of everything requiring attention
across all Johnny.Decimal systems. It combines active tasks (from todo.txt),
unprocessed inbox items, and items needing review into a single report ordered
from most urgent to least urgent, followed by a "coming up" section for items
approaching actionability.
This skill is read-only — it never modifies any files. It reads and reports.
For task parsing rules, read ../jd-task-manager/references/jdtodo-spec.md
(the jdtodo.txt format specification).
Before generating the report, build a mental map of the user's JD setup.
The JD root folder is wherever the user's systems live. Common locations:
~/Library/Mobile Documents/com~apple~CloudDocs/JD/ (iCloud Drive)~/Documents/JD/~/JD/If you don't know the root, ask the user. If the user says "what should I do next" without further context, check the most common locations above. If you find exactly one, use it. If you find multiple or none, ask.
List the top-level folders under the JD root. Each folder whose name matches
the pattern [A-Z][0-9][0-9] * is a JD system (e.g., P10 Personal,
W20 Work).
If the user has a single system (no SYS prefix), treat the entire JD root as one system.
If the user specified a system code as an argument (e.g., "next actions for P10"), limit scanning to that system only.
For every system you'll scan, read the JDex file at:
SYS/00-09 */00 */00.00 *JDex*
The JDex is needed to enrich task displays with human-readable descriptions
for +AC.ID references. If the JDex is missing, you can still generate the
report but cannot enrich JD codes — note this in the summary.
For each system, locate and read these data sources. If a source doesn't exist, skip it and note the absence.
00.02 Tasks/todo.txtRead and parse todo.txt using jdtodo.txt format rules (see the jdtodo-spec
reference). For each task, extract:
(A) through (Z), or none)@context)+project, +AC.ID)due:, before:, t:, after:, id:, dep:, rec:, h:)---)Filter for actionable tasks. A task is actionable if ALL of these are true:
x or ~)h:1 absent)t: date <= today, or no t:)after: date has passed or is absent (after: date <= today, or no after:)@someday contextdue:somedaydep: references point to completed tasks (or the referenced id: does
not exist in the active task list)Track separately:
dep: points to an incomplete task.
Count these for the summary but do not include in the main report.@waiting context that are otherwise actionable.
Include them in their normal bucket but count them separately for the summary.00.01 Inbox/List the contents of the inbox folder. Do NOT read or classify individual items — that is the inbox processor's job. Collect:
.md, .pdf, .jpg, etc.)If the inbox is empty, skip this data source entirely.
00.04 Needs review/List items in the needs-review folder. For each item, collect:
If the folder doesn't exist or is empty, skip this data source.
00.02 Tasks/someday.txtCount the number of tasks in someday.txt (if it exists). This is for the
summary statistics only — do not include someday tasks in the report body.
Also count tasks with @someday or due:someday in todo.txt that were
excluded by the actionability filter.
Identify tasks that are NOT yet actionable but will become actionable within the next 14 days:
t:YYYY-MM-DD where the date is > today AND <= today + 14 daysafter:YYYY-MM-DD where the date is > today AND <= today + 14 daysThese are not blocked or someday — they're simply waiting for their visibility window to open.
Place each item into exactly one bucket — the highest-priority bucket it qualifies for. A task that qualifies for multiple buckets appears only in the first matching one.
Process in this order (first match wins):
Bucket 1 — Overdue
Actionable tasks where due: or before: date is before today.
Show how many days overdue each task is.
Bucket 2 — Due Today
Actionable tasks where due: or before: date equals today.
Bucket 3 — Inbox
Unprocessed items in 00.01 Inbox/ folders.
Shown as a count per system, not individual items.
Bucket 4 — Needs Review
Items in 00.04 Needs review/ folders.
Shown as individual items with filenames.
Bucket 5 — High Priority
Actionable tasks with (A) priority that did not land in Overdue or Due Today.
Bucket 6 — Due This Week
Actionable tasks where due: or before: is within the next 7 days (after
today, up to and including today + 7 days). Excludes tasks already placed in
a higher bucket.
Bucket 7 — Other Actionable
All remaining actionable tasks — (B) through (Z) priority and unprioritized
tasks that did not land in any bucket above.
Bucket 8 — Coming Up
Tasks with t: or after: dates within the next 14 days that are not yet
actionable. These are shown to help the user prepare.
Within each bucket, sort tasks by:
(A) first, then (B), then (C), ..., then unprioritized lastIf a bucket has zero items, omit that section entirely from the report. Only show sections that have content.
## Next Actions
**Date:** YYYY-MM-DD
**Systems:** [comma-separated system names, e.g., P10 Personal, W20 Work]
If scanning a single system, omit the "Systems" line and use the system name in the header:
## Next Actions — P10 Personal
**Date:** YYYY-MM-DD
### Overdue (N)
| Pri | Task | Due | Overdue |
|-----|------|-----|---------|
| (A) | [P10] Submit quarterly tax estimate +N42.13.02 @laptop | 2026-02-05 | 5 days |
| (B) | [P10] Review tuition bill +V06.31.02 @laptop | 2026-02-08 | 2 days |
Show the [SYS] prefix only when displaying multiple systems.
### Due Today (N)
| Pri | Task |
|-----|------|
| (A) | [W20] Respond to P0 incident follow-up +G24.21.05 @work |
### Inbox (N items)
| System | Items | Newest |
|--------|-------|--------|
| P10 Personal | 8 items (.md, .pdf, .jpg) | 2026-02-09 |
| W20 Work | 3 items (.md, .txt) | 2026-02-08 |
Run `/jd:process-inbox` to classify and file these items.
For single-system reports, simplify:
### Inbox (8 items)
8 unprocessed items (.md, .pdf, .jpg). Newest: 2026-02-09.
Run `/jd:process-inbox P10` to classify and file these items.
### Needs Review (N items)
| System | Item | Date |
|--------|------|------|
| P10 | 2026-01-28 Meeting notes.md | Jan 28 |
| W20 | 2026-02-03 Budget spreadsheet.xlsx | Feb 3 |
### High Priority (N)
| Task | Due |
|------|-----|
| [P10] Clean out garage +GarageSale +N42.12.05 | 2026-05-01 |
| [W20] Review contract terms +G24.31.05 @laptop | 2026-02-15 |
### Due This Week (N)
| Pri | Task | Due |
|-----|------|-----|
| (B) | [P10] Schedule dentist for Hannah @phone | Feb 12 |
| (B) | [P10] Water all houseplants @home | Feb 11 |
### Other Actionable (N)
| Pri | Task | Due |
|-----|------|-----|
| (B) | [P10] Sort items for garage sale +GarageSale | Feb 20 |
| (C) | [W20] Update project documentation @laptop | — |
| — | [P10] Update emergency contacts | — |
Show — for tasks with no due date.
### Coming Up (next 14 days)
| Task | Actionable | Due |
|------|------------|-----|
| [P10] Renew car registration +N42.12.01 | Jun 1 (in 5 days) | Jun 30 |
| [W20] Start Q2 planning +G24.21.02 | Feb 20 (in 10 days) | Mar 1 |
These tasks are not yet actionable but will become visible soon.
Show both the date the task becomes actionable (t: or after: date) and its
due date (if any). Include the "in N days" relative label.
When displaying tasks with +AC.ID or +SYS.AC.ID project tags, look up the
code in the relevant system's JDex. If found, you may append the description
after the task or use it in the table.
For example, if N42.13.02 maps to "Tax returns & estimates" in the JDex:
| (A) | Submit quarterly tax estimate +N42.13.02 @laptop | 2026-04-15 |
The JD code itself is usually enough context. Only add the description if the task text alone doesn't make the purpose clear.
When showing tasks from multiple systems:
[SYS] (e.g., [P10], [W20])When showing a single system:
[SYS] prefixAlways end the report with a summary section:
### Summary
| | Count |
|--|-------|
| Overdue | 2 |
| Due today | 1 |
| Inbox items | 11 |
| Needs review | 2 |
| High priority | 2 |
| Due this week | 3 |
| Other actionable | 8 |
| **Total actionable** | **16** |
| | |
| Blocked | 3 |
| Waiting (@waiting) | 2 |
| Someday | 5 |
| Coming up (14 days) | 2 |
**Recommended focus:** [one sentence suggesting where to start]
The "Recommended focus" line should follow this logic:
The user may request a filtered view. Apply the filter AFTER scanning all data sources but BEFORE bucketing.
"next actions for P10" — Only scan the specified system.
"what can I do @phone" — Only include tasks with the specified context. Inbox and needs-review items are still shown (they may contain relevant work).
"what's next for +GarageSale" — Only include tasks with the specified project tag. Inbox and needs-review items are omitted (they haven't been classified).
"what's due this week" — Only include tasks in the Overdue, Due Today, and Due This Week buckets. Omit inbox, needs review, and lower-priority buckets.
This skill never modifies files. It reads task files, inbox contents, and needs-review items, then generates a report. No writes, no moves, no edits.
Do not read inbox item contents or classify them — that's the inbox processor's job. Only count items and note their presence.
Do not modify task priorities or due dates — that's the task manager's job.
After the report, suggest relevant next steps using other skills:
/jd:process-inbox to classify inbox items."/jd:manage-tasks to reschedule or complete overdue tasks."/jd:manage-tasks review to review someday items."If the user asks for the report again during the same session, regenerate it fresh — task states may have changed.
If 00.02 Tasks/todo.txt doesn't exist for a system:
00.02 Tasks.md exists (legacy format). If so, note it and
suggest migration via /jd:manage-tasks.If 00.01 Inbox/ or 00.04 Needs review/ doesn't exist, simply omit that
data source. Do not warn about structural absence — not all systems use all
standard zeros.
If a task line cannot be parsed:
[parse error] flagIf a system's JDex is missing:
If all data sources are empty across all systems:
| Order | Bucket | Source | Criteria |
|---|---|---|---|
| 1 | Overdue | todo.txt | due: or before: < today |
| 2 | Due Today | todo.txt | due: or before: = today |
| 3 | Inbox | 00.01 Inbox/ | Any items present |
| 4 | Needs Review | 00.04 Needs review/ | Any items present |
| 5 | High Priority | todo.txt | (A) tasks not in above |
| 6 | Due This Week | todo.txt | due: or before: within 7 days |
| 7 | Other Actionable | todo.txt | All remaining actionable |
| 8 | Coming Up | todo.txt | t: or after: within 14 days |
A task is actionable if ALL true:
x) or cancelled (~)h:1 absent)t: <= today, or no t:)after: <= today, or no after:)@someday contextdue:somedaydep: resolved (blocking tasks completed or absent)