suggest-next-features

The ledger runs dry. Either every feature_list.json entry has passes: true, or the last few sessions have been shuffling half-features and adding no new work because the spec grew and the list did not.

This skill drafts candidate additions — but to a separate file, feature_list.suggestions.json. feature_list.json is immutable except for the single passes: false → true flip that [[feature-list-json]] permits. Silently appending entries would break that contract and let a runaway session invent its own scope.

The suggestions file is a proposal. A human hand-merges chosen entries into feature_list.json; the rest are ignored or deleted. No agent, ever, edits feature_list.json directly from this skill.

Trigger

Apply when either condition holds:

• jq '[.[] | select(.passes==false)] | length' feature_list.json returns 0.
• The last 3 progress entries in claude-progress.txt show no new passes: true flips AND the user has referenced behavior not present in feature_list.json.

Do not apply just because the list looks short. 30 unfinished entries is not a trigger; 0 is.

Procedure