agentleFS
NitinJNitinJ/specforge/skills/list-specs/SKILL.md

list-specs

Skill4 starsChanged 2 months agoMITView on GitHub

List SpecForge specs — either every spec in the store (mode "all") or just the specs attached to this session (mode "mine"). Use when the user asks to "list specs", "show all specs", "what specs do I have open", or wants to open/detach a spec. Starts or reuses the daemon, prints a table, and offers to open/detach.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If at least one row is actionable, call AskUserQuestion ("Open or detach a spec?").

    line 51
  2. Distinctive:

    always include "Just viewing" (does nothing)

    line 57
  3. Distinctive:

    If more than 3 rows are actionable, show the 3 most useful (free specs first) and note that "Other" accepts any id.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

list-specs

${CLAUDE_PLUGIN_ROOT} below denotes the installed plugin directory. Claude and Pi export it; Codex provides the exact value in SpecForge SessionStart context. Substitute that value in every path and shell command.

Run the CLI

  • All specs (mode "all"): node "${CLAUDE_PLUGIN_ROOT}/lib/specforge-cli.mjs" listall
  • This session's specs (mode "mine"): node "${CLAUDE_PLUGIN_ROOT}/lib/specforge-cli.mjs" list

The default output is compact: one line per spec — id status type attached title — where attached reads mine when it names the calling session (so the picker can classify rows from the lines alone), a session id when another session holds it, or free. listall adds index: <url> (and ensures the daemon is up). Pass --json for the machine shape: session plus rows ({ id, title, type, status, attached }, where attached is a session id or free). list reads straight from the store (no daemon needed). The picker's actions handle the daemon themselves: open starts it when needed and returns a URL, while detach is store-only — so both work whether or not the daemon was already running.

Present the result

Render rows as a compact, numbered table — # · id · title · type · status · attached — showing attached as free, mine (this session), or held: <first 8 of the id>. For "all", also print indexUrl (the browser index links each row to /spec/<id>).

Then offer to open / detach (the picker)

Classify each row (the compact output renders mine for the calling session; --json output carries the raw session id instead):

attachedmeaningaction
freeunattachedopen (attach to this session)
mine (compact), or equals session (--json)attached heredetach
any other idheld by another live sessionnone (show it greyed)

If at least one row is actionable, call AskUserQuestion ("Open or detach a spec?"). AskUserQuestion allows 4 options max, so offer up to 3 actionable specs plus a "Just viewing" option (4 total):

  • free specs → label Open · <title> (use <id8> if untitled)
  • this session's specs → label Detach · <title>
  • always include "Just viewing" (does nothing)

The user can also pick "Other" (always available) and type any id from the table. If more than 3 rows are actionable, show the 3 most useful (free specs first) and note that "Other" accepts any id.

Act on the choice:

  • Open <id> → node "${CLAUDE_PLUGIN_ROOT}/lib/specforge-cli.mjs" open <id> (attaches it to this session; fails if another live session holds it). Print the returned url. In Codex, finish the turn; the host-owned watcher delivers browser comments automatically. Do not start a watcher. In Claude Code, arm one background review-wait if none is running; Pi delivery is extension-managed.
  • Detach <id> → node "${CLAUDE_PLUGIN_ROOT}/lib/specforge-cli.mjs" detach <id>. Confirm it's freed.
  • Other <id> → open it if free, detach it if it's attached here, else say it's held by another session.
  • Just viewing → stop, no action.

Skip the picker when nothing is actionable. In "mine" mode with no rows, say no spec is attached to this session and point to the list-all command to open one — that is /specforge:listall under Claude Code and /spec-listall under Pi. Name the one your harness registers; the other does not exist there.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.