Renew

Load focused context for a project or area to continue work. If the user omits the slug, infer the most likely target from conversation and workspace context.

Named /renew instead of /resume because /resume is a built-in command in Claude Code (and other tools) for resuming previous conversations.

Steps

1. Resolve the journal path:

   JORNAL="${JORNAL:-$HOME/para/areas/dev/gh/ak/journal}"

2. Identify the target.

   If the user provided a slug or name (/renew <slug>, pick up <project>, etc.), match it against:

   • $JORNAL/projects/<slug>.md
   • $JORNAL/areas/<slug>.md
   • If no exact match, try partial match or list available projects/areas and ask.

   If the user omitted the target (/renew, continue, pick this back up), infer it from context using these signals, in order:

   1. Current conversation: the project/area name or slug the user just mentioned.
   2. Current working directory: repo/path components matching a project or area slug/name.
   3. Git context: current branch name, remote URL/repo name, or recent commit messages matching a project or area slug/name.
   4. $JORNAL/workqueue.md: the most recent queued /next entry if it is unambiguous.
   5. Today's log: Focus section or most recent Log entry naming a project/area.
   6. Recent logs (last 3 days): most recently active project/area.

   Treat exact slug/name matches as strong evidence. Treat multiple plausible matches as ambiguous.

   If exactly one strong candidate is found, proceed and mention the inference source in the output (for example: Inferred from current directory). If no candidate or multiple candidates are plausible, list the top candidates with their evidence and ask the user to choose instead of guessing.

3. Read the matched project or area file.

4. Read today's log ($JORNAL/areas/log/YYYY/YYYY-MM/YYYY-MM-DD.md). If it doesn't exist, create it with the daily log template. Scan for any earlier session entries related to this project/area today.

4a. Check $JORNAL/workqueue.md for any queued /next entries matching this slug (any date). Match lines of the form ^## \d{4}-\d{2}-\d{2} \d{2}:\d{2} — <slug>$ (line-end anchor). If entries exist, display them in the output under a Queued sessions section so the user has the full prior context before continuing.

5. Search recent logs for context (last 3 days):

   grep -rl "<slug>" "$JORNAL/areas/log/" 2>/dev/null | sort -r | head -3

   Read any matches to understand recent session history.

6. Search inbox for related items:

   grep -i "<slug>" "$JORNAL/inbox.md"

7. If in a git repo, gather workspace context:

   • git branch --show-current
   • git log --oneline -5
   • git status --short

Output format

Resuming: Project/Area Name

Target inference: explicit <slug>, or inferred from cwd/git/workqueue/logs

Status: one-line summary of where things stand

Queued sessions (from workqueue.md — unprocessed /next entries for this slug)

• bullet entries from each queued session, in chronological order
• (none) if no queued entries

Last session (from most recent log entry)

• what was done last time

Open tasks

• task list from the project/area file

Waiting

• [~] any blocked items

Related inbox items (if any)

• items that mention this project

Workspace (if in a relevant git repo)

• Branch, status, recent commits

Suggested next step

• what makes sense based on task list and last session

Then ask: "Ready to continue, or want to adjust the plan?"