kmmwren

action-task

Use when the user wants Claude to actually DO / execute / action / run / work on / pick up / start / tackle a SPECIFIC task that already lives in the claude-tasks queue — e.g. "action the staging task", "do the onboarding brief", "work on the billing one", "pick up X from the queue", "start the migration task". Resolves the phrase to a single brief, moves it to in-progress, executes it end-to-end against its success criteria, and marks it done (or escalates if it hits something only the user can decide). NOT for adding a task (use queue-task / raw-capture) or offloading the current session's loose ends (use handoff).

enrich

Process the queue's inbox/ items into full ready/ briefs. Human-initiated (never automatic). For each item — dedup check, gather context, fill all frontmatter fields, write goal + criteria + context, commit to ready/, and archive the raw file to inbox/.processed/ (never delete — audit trail). Flag if the inbox grows past 20 items.

handoff

Use when the user wants to STOP a Claude Code session and hand its still-open work to the task queue — "handoff", "I'm done with this session", "stop and queue what's left", "offload this session", "park this and pick it up later", "hand off everything to parked". Captures the session's open work items into the queue (inbox/ by default, or a directed target like parked/ or ready/) AND adds a judgement layer of things discussed-but-never-tracked, so nothing is stranded when the session ends.

prioritise

Use when the user asks what to do next or how the queue is prioritised — "what's next", "what should I work on", "what's the priority", "what's blocked", "what's the most important thing", "what can you pick up". Ranks the ready/ briefs (dependency-aware: a brief stays blocked until its dependencies are done; briefs that unblock others rank higher) and shows the top of the queue with blocked / needs-you / unlock flags.

queue-task

Use whenever a task should be added to the claude-tasks queue — either because the user said "add a task / track this / remember to do X / put this on the list", OR because you (Claude), in the middle of other work, discovered something that should become a tracked task: a follow-up, a deferred fix, a TODO you left, a security issue, an improvement, a "we should also…". This is how Claude self-captures work into the queue from any session. Fill the brief out as meaningfully as you can from what you already know.

raw-capture

Zero-friction capture of a raw idea into the queue's inbox/. Use when the user dumps a thought mid-flow and you want to capture it without structural overhead — no domain, no importance, no enrichment needed. Just get it in the queue. For a fully-structured ready-to-execute brief, use queue-task instead.

recap

Use when the user asks what has been discussed, wants a quick status check, says "recap", "remind me what we've done", "what's outstanding", "where are we", or any variation of wanting a mid-session or end-of-session summary in the chat. Trigger immediately — do not ask clarifying questions first. This is a quick in-chat summary, NOT a file write.