get-next-feature

Automate feature selection by parsing a JSON file to identify the next task based on status priority. The script checks for in-progress features to handle retries, then selects the first pending feature to maintain project momentum.

Task status priority works by first scanning for features marked in_progress to resume stalled work. If none are found, it selects the first task with a pending status, ensuring a continuous and efficient development workflow.

When all pending features are completed, the script handles completion detection by returning an ALL_COMPLETE status. This signals that no suitable features are left to process, preventing idle time in the workflow.

Yes, you can manage retry scenarios because the script explicitly checks for features marked in_progress before pending ones. This ensures that previously started but unfinished tasks are prioritized for the next development cycle.

You need a JSON file containing a list of features with defined status fields like pending and in_progress. The script processes this structure to extract the next actionable item and output the selected feature or an ALL_COMPLETE status.

The best way to select the next feature is using an automated script that evaluates status priority. It locates in_progress items for retries, then pending items, and finally returns ALL_COMPLETE if the list is exhausted.