Skip to content
Back to skills

List

ASecurity

Use when listing all specs under the specs root — the /specode:list entry that shows every spec slug with its inferred phase, for looking up slugs or an overview; it does not resume. Trigger /specode:list.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
developmentgobash

Works with

  • cli

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add qxbyte/specode --skill list --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of List?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for List
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/qxbyte-list/badge)](https://www.skillsdirectory.com/skills/qxbyte-list)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: list
description: Use when listing all specs under the specs root — the /specode:list entry that shows every spec slug with its inferred phase, for looking up slugs or an overview; it does not resume. Trigger /specode:list.
---

# /specode:list — list all specs

Lists every spec under `<specsRoot>` with each one's inferred phase (for looking up slugs / overview). **Does not resume.**

## Resolver

specode CLIs go through the `run.sh` wrapper in the plugin's `scripts/` directory — relative to this skill that is `../../scripts/`; use this skill's base directory to turn the relative path into an absolute one (do **not** resolve env vars, do **not** `find` the cache):

```bash
sh ../../scripts/run.sh ../../scripts/resolve_root.py list-specs
```

## Flow

1. `resolve_root.py get-root`: exit 3 (not configured) → first-time setup (see `../spec/SKILL.md` §specsRoot resolution), then continue; **exit 4** (configured but **unreachable** — external drive not mounted / path gone) → surface the cause and re-prompt for a path, don't present an empty list as if there were no specs; exit 0 → `<specsRoot>`.
2. `resolve_root.py list-specs` to list slugs; for each slug, read its spec directory documents and infer the current phase per the documents-as-state table in `../continue/SKILL.md`, then display slug + phase.
3. No specs found → prompt the user with `/specode:spec <request>`. **Do not resume.**

## Output Language

User-facing output must be in **Chinese (中文)**.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.