AgentStack
SKILL verified MIT Self-run

List Tasks

skill-avanrossum-claude-task-skills-list-tasks · by avanrossum

List tasks by status — shows open, completed, stalled, or all tasks from the project's task tracker

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-avanrossum-claude-task-skills-list-tasks

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of List Tasks? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

/list-tasks — List Tasks by Status

Show the user a summary of tasks, optionally filtered by status.

Arguments: $ARGUMENTS


Step 1 — Parse Filter

The user may have specified a filter:

  • /list-tasks — show all tasks, grouped by status
  • /list-tasks open or /list-tasks active — only in-progress tasks
  • /list-tasks completed or /list-tasks done or /list-tasks closed — only completed tasks
  • /list-tasks stalled or /list-tasks blocked — tasks that are blocked, stalled, or pending external input
  • /list-tasks all — everything, including completed

Default (no argument): show open/active tasks first, then a count of completed tasks (not the full list).


Step 2 — Find Task Data

Locate the project's task tracking system:

  1. Task tracker file — Look for TASKS.md, a task section in CHANGELOG.md, or whatever CLAUDE.md specifies
  2. Task folders — Look for a tasks/ directory and scan its subfolders
  3. Both — Cross-reference the tracker against actual folders to catch discrepancies

If the tracker and folders disagree (e.g., a folder exists but isn't in the tracker, or a tracker entry has no folder), flag the discrepancy to the user.


Step 3 — Classify Tasks

Group tasks into these categories:

| Status | Meaning | |--------|---------| | 🔵 In Progress | Active work happening | | ⏳ Pending Review | Built, awaiting feedback or sign-off | | ⏳ Sandbox Ready | Deployed to sandbox, awaiting prod | | 🔴 Blocked / Stalled | Cannot proceed — dependency, question, or external blocker | | 📋 Queued | Defined but not yet started | | ✅ Complete | Done and closed |

Map the project's status terms to these categories. Different projects use different labels — normalize for display but preserve the original status.


Step 4 — Display

Format the output as a clean table or grouped list. For each task show:

  • Title
  • Status (with icon)
  • Location (folder path or reference)
  • Brief note (one line — what's the current state or blocker)

Example output:

## Active Tasks (3)

| Task | Status | Notes |
|------|--------|-------|
| Regional Rep Goals Dashboard | ⏳ In Team Review | Full dashboard deployed to sandbox |
| C2L FA Link Signing | 🔵 In Progress | Discovery phase — open questions logged |
| FSA Cohort Swap | ⏳ Sandbox Ready | Awaiting team testing for prod |

## Queued (1)
| Flow Blast Radius Map | 📋 Queued | Not yet started |

## Completed: 8 tasks (use `/list-tasks completed` to see all)

Keep it scannable. This is a status check, not a deep dive.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.