Feature List JSON

What it does

When your agent uses it

• Tasks that involve End-to-end testing

Example prompts

• “s done, what”
• “/feature-list-json”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Enumerate every user-observable behavior the spec implies. Login, list rendering, empty states, error states, keyboard shortcuts, mobile…
2. 2Write each as one entry. description is one sentence, steps is a user's actual action sequence (not implementation notes).
3. 3Order the array so an agent walking top-to-bottom builds prerequisites before dependents.
4. 4Every passes starts false. No exceptions, not even for the smoke test.
5. 5Validate: jq '. | length' returns your count; jq '[.[] | select(.passes==true)] | length' returns 0.

What it can do on your machine

Read from SKILL.md and the folder at commit 5ae033e. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • jq
  • git

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature List JSON loads about 1.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~64

When it runs · the whole SKILL.md, loaded when a task matches

~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Archive228/loopkit at commit 5ae033e, republished under its MIT licence (© Archive228). 564 words, ~1,241 tokens.

name

feature-list-json

description

Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.

when_to_use

initializer agent building the master feature list at scaffold time, coding agent flipping a single passes field after E2E verification, auditing that…

{
  "category": "functional",
  "description": "New chat button creates a fresh conversation",
  "steps": [
    "Navigate to main interface",
    "Click the 'New Chat' button",
    "Verify a new conversation is created",
    "Check that chat area shows welcome state",
    "Verify conversation appears in sidebar"
  ],
  "passes": false
}

git diff feature_list.json | grep -E '^[-+]' | grep -v 'passes'

© Archive228, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/feature-list-json of Archive228/loopkit.

Open the folder on GitHubat commit 5ae033e