asap-process

name	asap-process
description	ASAP process skill — interactive ASAP list triage

ASAP Process

Interactive triage of the ASAP list.

Arguments

$ARGUMENTS — Optional: an integer index to start from (resumes triage from that item). Omit to start from the first pending item.

Behavior

Step 1 — Load the ASAP list

Run via Bash:

rubber-ducky asap list --json

This returns an array of items from wiki/asap.md. Each item has index (integer), message (string), createdAt (ISO timestamp), and resolved (boolean). Filter to only pending items (resolved: false).

Present a numbered summary:

ASAP items (N pending):
1. message (added: date)
2. message (added: date)
...

If $ARGUMENTS specifies an index, skip items with an index less than that value (they were already processed in a previous run).

If there are no pending items, report "No pending ASAP items." and stop.

Step 2 — Walk through items one at a time

For each pending ASAP item, present it with four options:

[N/total] #index — message
Added: date

What would you like to do?
  (a) Act on it now — drop into this item immediately
  (c) Convert to task — create a wiki task page and resolve this item
  (d) Defer — skip for now, keep on ASAP list
  (x) Dismiss — resolve and remove from ASAP list

Wait for the user's choice before proceeding.

Step 3 — Execute the chosen action

Act (a): Report "Switching to this item. Run /asap-process <next-index> to resume triage." and stop processing. The user will handle the item and can resume later.

Convert (c): Create a task page from the ASAP item. Run via Bash:

rubber-ducky page create task "<message>"

Then resolve the ASAP item so it no longer appears as pending:

rubber-ducky asap resolve <index>

Confirm: "Converted to task and resolved from ASAP list."

Defer (d): No action needed — the item stays pending on the ASAP list. Confirm: "Deferred." Move to the next item.

Dismiss (x): Resolve the item without creating a task. Run via Bash:

rubber-ducky asap resolve <index>

Confirm: "Dismissed." Move to the next item.

Step 4 — Progress tracking

After each item, show progress: "Processed N of M items."

Resolved items (converted or dismissed) are removed from the pending list immediately. If the user runs the skill again, only unprocessed pending items remain. If the user stops partway through (chooses "act" or interrupts), already-resolved items stay resolved. No progress is lost.

Step 5 — Completion

When all pending items are processed, summarize:

ASAP triage complete:
- Acted on: N
- Converted to tasks: N
- Deferred: N
- Dismissed: N

Output

Interactive, one-at-a-time triage flow. Keep each item presentation concise. Progress is saved as items are processed — stopping partway through is safe.