next

Analyze worklog files and project plans to recommend the next actionable task.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/taewook486/real-estate-mcp --skill next-taewook486
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next
Source: https://github.com/taewook486/real-estate-mcp/tree/main/.claude/skills.nouse/next
Command: npx skills add https://github.com/taewook486/real-estate-mcp --skill next-taewook486

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users understand the next logical step in a project by analyzing the current work status and project plan.

Core Features & Use Cases

  • Task Prioritization: Identifies the most important task to tackle next based on project phase and existing work.
  • Progress Tracking: Cross-references implemented features with the project plan to highlight what's missing.
  • Use Case: When you're unsure what to code next, this Skill will tell you whether to finish your current task, pick the next item from the to-do list, or start implementing a new feature from the plan.

Quick Start

Use the next skill to determine the next task for the project.

Frequently Asked Questions about next

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

FAQPage Schema
How do I determine the next task to work on in my development project?

To determine the next task, analyze your project plans alongside 'worklog.doing.md' and 'worklog.todo.md' files. This cross-references implemented features against the plan to prioritize what to code next based on current project phase and worklog status.

What is the best way to prioritize tasks when unsure what to code next?

Task prioritization works by comparing your project plan against actual files in the 'src/' directory. This identifies missing implementations and highlights whether to finish a current task, pick a to-do item, or start a new feature.

Can I track development progress by comparing my project plan with source files?

Yes, you can track progress by identifying missing implementations through comparing the project plan against files in the 'src/' directory. This highlights what features are unfinished and helps maintain accurate progress tracking.

Do I need specific worklog files to analyze my project's next steps?

Yes, analyzing next steps requires 'worklog.doing.md' and 'worklog.todo.md' files along with your project plans. These worklog files provide the current work status needed to recommend the next actionable task accurately.

How does task prioritization work for different project phases?

Task prioritization analyzes the current project phase and existing work status from worklog files. It evaluates whether to continue an in-progress task or select a new item from the to-do list based on the active development phase.

What are the limitations of using worklog files for development planning?

Worklog-based development planning relies strictly on 'worklog.doing.md', 'worklog.todo.md', and 'src/' directory structures. It cannot recommend tasks if these files are missing or fail to identify missing implementations without an existing project plan.