task-next

Select the next oldest task ID from a timestamped tasks dataset.

6|1|Updated Jan 5, 2026

Search Tags:#automation #workflow #navigate #task #ordering #chronological #next

Ready to run

npx skills add https://github.com/JordanGunn/skills --skill task-next

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-next
Source: https://github.com/JordanGunn/skills/tree/main/skills/task/next
Command: npx skills add https://github.com/JordanGunn/skills --skill task-next

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Navigates to the next task in chronological order, returning the next older task's ID based on the created_at timestamp.

Core Features & Use Cases

Sequential navigation: move to the next task in a time-ordered task list.
Workflow compatibility: ideal for plan progression, task chaining, and automated progress tracking.
Example scenario: given a current task ID, retrieve the next task's ID to continue a multi-step workflow.

Quick Start

Ask the system to fetch the next task after a given ID from the tasks directory.

Frequently Asked Questions about task-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I navigate to the next task in chronological order?▼

To navigate to the next task in chronological order, provide a current task ID from your tasks dataset. The system selects the next oldest task using the created_at timestamp and returns its ID.

How does sequential task progression work for automated workflows?▼

Sequential task progression works by chaining tasks through their created_at timestamps. Given a current task ID, the system retrieves the next older task's ID to continue a multi-step workflow automatically.

Can I use this for task chaining in plan progression without extra dependencies?▼

Yes, you can use this for task chaining and plan progression without extra dependencies. It operates on timestamped tasks within a dataset to retrieve the next chronological ID.

What is the best way to fetch the next task after a given ID?▼

The best way to fetch the next task after a given ID is to request the system to navigate your timestamped tasks directory. It identifies the next oldest task by created_at time and outputs the ID.

Why does task navigation require a created_at timestamp?▼

Task navigation requires a created_at timestamp because the system determines chronological ordering by comparing these timestamps. It selects the next oldest task relative to the current ID to ensure sequential workflow progression.