Suggest Next Features

What it does

When your agent uses it

• Development work in your project

Example prompts

• “/suggest-next-features”

Workflow steps

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

1. 1git log --pretty=format:'%h %s' "$(git log --grep='chore: initial scaffold' --format=%H | tail -1)"..HEAD — every commit since the…
2. 2Read the last 3 "What's done" / "Notes for the next session" entries from claude-progress.txt. This is where recent scope creep leaks.
3. 3Read feature_list.json in full. You need to know what is already enumerated so you do not propose duplicates.
4. 4Compare (1)+(2) against (3). Look for
5. 5Draft 5–10 candidate entries in the same shape as feature_list.json. Every one starts passes: false. Order them roughly by priority.
6. 6Write the array to feature_list.suggestions.json at the project root. Overwrite any prior draft — this file is regenerable, not append-only.
7. 7Print a one-line summary per suggestion so the operator can scan without opening the file.
8. 8Stop. Do not touch feature_list.json. Do not commit feature_list.suggestions.json (it is a proposal, not project state).

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:

  • git
  • jq

  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

Suggest Next Features loads about 1.1k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 521 words of instructions outside code blocks.

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

~44

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

~1.1k

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). 521 words, ~1,148 tokens.

name

suggest-next-features

description

Read git log since initial scaffold + last 3 progress notes, draft feature additions to a SEPARATE suggestions file so feature_list.json stays immutable

when_to_use

feature_list.json has zero passes:false entries left OR the last 3 sessions added no new work and the spec has quietly expanded (user asked for something the…

[
  {
    "category": "ux",
    "description": "Empty conversation list shows an onboarding CTA",
    "steps": [
      "Load app as a user with zero conversations",
      "Verify the sidebar shows a 'Start your first chat' CTA",
      "Click the CTA and land in a fresh conversation"
    ],
    "passes": false,
    "rationale": "Sessions 41/43 both hit the empty-list path and rendered a blank sidebar; no entry covers it."
  }
]

© 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/suggest-next-features of Archive228/loopkit.

Open the folder on GitHubat commit 5ae033e