# Tasks

View and manage the task stack and processing queue.

- Repository: https://github.com/agenticnotetaking/arscontexta (3518 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-02-24
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add agenticnotetaking/arscontexta --skill tasks -g -a claude-code -y`
Codex: `npx skills add agenticnotetaking/arscontexta --skill tasks -g -a codex -y`
Cursor: `npx skills add agenticnotetaking/arscontexta --skill tasks -g -a cursor -y`
Gemini CLI: `npx skills add agenticnotetaking/arscontexta --skill tasks -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add agenticnotetaking/arscontexta`

## Description

View and manage the task stack and processing queue. Shows pending work, active tasks, completed items, and queue state. Triggers on "/tasks", "show tasks", "what's pending", "task list", "queue status".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Runtime Configuration (Step 0, before any processing)

Read these files to configure domain-specific behavior:

1. **`ops/derivation-manifest.md`**, vocabulary mapping
   - Use `vocabulary.notes` for the notes folder name
   - Use `vocabulary.note` / `vocabulary.note_plural` for note type references
   - Use `vocabulary.topic_map` for MOC references
   - Use `vocabulary.cmd_reflect` / `vocabulary.cmd_reweave` / `vocabulary.cmd_verify` for phase command names

2. **`ops/config.yaml`**, pipeline chaining mode, automation settings

If no derivation file exists, use universal terms.

---

## EXECUTE NOW

**Target: $ARGUMENTS**

Parse the operation:
- No arguments or `status`: show task stack + queue state (combined view)
- `add [description]`: add a task to the stack
- `done [task-number]`: mark a task as completed
- `drop [task-number]`: remove a task without completing
- `reorder [number] [position]`: move a task to a different position in the stack
- `discoveries`: show only the Discoveries section

**START NOW.** Execute the requested operation.

---

## Philosophy

**Two systems, one view.**

The task stack (`ops/tasks.md`) and the pipeline queue (`ops/queue/queue.yaml` or `ops/queue/queue.json`) serve different purposes:

| System | Purpose | Managed By | Updated By |
|--------|---------|-----------|------------|
| Task stack | Human priorities, what YOU want to work on | You (via /tasks) | Manual: /tasks add, /tasks done |
| Pipeline queue | Automated processing state, what the SYSTEM needs to process | Pipeline skills | Automatic: /reduce, /ralph, /reflect |

/tasks shows BOTH so you always have a unified view of all pending work. The task stack is your working memory. The pipeline queue is the system's working memory. Together they answer: "What should I do next?"

---

## Operations

### /tasks (or /tasks status)

Show both the human task stack and the automated queue.

**Step 1: Read task stack**

The rest: https://github.com/agenticnotetaking/arscontexta/blob/HEAD/skill-sources/tasks/SKILL.md