jd-next-action

What this skill does

# Johnny.Decimal Next Action Dashboard

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).

---

## 1. Orientation: Discover the JD Environment

Before generating the report, build a mental map of the user's JD setup.

### 1.1 Locate the JD Root

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/`
- A project-specific folder the user designates

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.

### 1.2 Identify Systems

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.

### 1.3 Load Each System's JDex

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.

---

## 2. Scan Data Sources

For each system, locate and read these data sources. If a source doesn't exist,
skip it and note the absence.

### 2.1 Active Tasks — `00.02 Tasks/todo.txt`

Read and parse `todo.txt` using jdtodo.txt format rules (see the jdtodo-spec
reference). For each task, extract:

- State (incomplete, complete, cancelled)
- Priority (`(A)` through `(Z)`, or none)
- Creation date
- Description
- Contexts (`@context`)
- Projects (`+project`, `+AC.ID`)
- Key:value pairs (`due:`, `before:`, `t:`, `after:`, `id:`, `dep:`, `rec:`, `h:`)
- Notes (after ` --- `)

**Filter for actionable tasks.** A task is actionable if ALL of these are true:

- It is incomplete (not `x` or `~`)
- It is not hidden (`h:1` absent)
- Its threshold date has passed or is absent (`t:` date <= today, or no `t:`)
- Its `after:` date has passed or is absent (`after:` date <= today, or no `after:`)
- It does not have `@someday` context
- It does not have `due:someday`
- All `dep:` references point to completed tasks (or the referenced `id:` does
  not exist in the active task list)

**Track separately:**

- **Blocked tasks**: Incomplete tasks whose `dep:` points to an incomplete task.
  Count these for the summary but do not include in the main report.
- **Waiting tasks**: Tasks with `@waiting` context that are otherwise actionable.
  Include them in their normal bucket but count them separately for the summary.

### 2.2 Inbox — `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:

- Total item count
- File types present (`.md`, `.pdf`, `.jpg`, etc.)
- Date of the most recently added item (from filesystem metadata or date-prefix
  in filename)

If the inbox is empty, skip this data source entirely.

### 2.3 Needs Review — `00.04 Needs review/`

List items in the needs-review folder. For each item, collect:

- Filename
- Date added (from date-prefix in filename, or filesystem metadata)

If the folder doesn't exist or is empty, skip this data source.

### 2.4 Someday — `00.02 Tasks/someday.txt`

Count 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.

### 2.5 Coming Up — Future Threshold Tasks

Identify tasks that are NOT yet actionable but will become actionable within the
next 14 days:

- Tasks with `t:YYYY-MM-DD` where the date is > today AND <= today + 14 days
- Tasks with `after:YYYY-MM-DD` where the date is > today AND <= today + 14 days

These are not blocked or someday — they're simply waiting for their visibility
window to open.

---

## 3. Categorize into Priority Buckets

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.

### 3.1 Bucket Definitions

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.

### 3.2 Sorting Within Buckets

Within each bucket, sort tasks by:

1. Priority — `(A)` first, then `(B)`, then `(C)`, ..., then unprioritized last
2. Due date — earliest first (tasks with no due date sort last)
3. Creation date — oldest first

### 3.3 Empty Buckets

If a bucket has zero items, omit that section entirely from the report. Only
show sections that have content.

---

## 4. Generate the Report

### 4.1 Report Header

```
## 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
```

### 4.2 Overdue Section

```
### 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.

### 4.3 Due Today Section

```
### Due Today (N)

| Pri | Task |
|-----|------|
| (A) | [W20] Respond to P0 incident follow-up +G24.21.05 @work |
```

### 4.4 Inbox Section

```
### 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.
```

### 4.5 Needs Review Section

```
### 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 |
```

### 4.6 High Priority Section

```
### High Priority (N)

| Task | Due |
|------|