next

Implement the next pending PRD task and generate a minimal MILESTONE.md.

4|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/blake-simpson/belmont --skill next-blake-simpson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next
Source: https://github.com/blake-simpson/belmont/tree/main/plugin/skills/next
Command: npx skills add https://github.com/blake-simpson/belmont --skill next-blake-simpson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement just the next pending task from the PRD by bypassing the research phases (codebase-agent and design-agent) and producing a minimal MILESTONE.md with just enough context for the implementation agent.

Core Features & Use Cases

  • Lightweight orchestration of a single task from the PRD, enabling quick follow-up work and verification fixes.
  • Generates a minimal MILESTONE.md to hand off to the implementation agent and stops after completing that task.
  • Applies to small, well-scoped issues discovered during verification or polish that do not require full pipeline steps.

Quick Start

Ask Belmont to implement the next pending task using the lightweight milestone workflow.

Frequently Asked Questions about next

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

FAQPage Schema
How do I implement just the next pending task from a PRD without running full research phases?

Implement the next pending task by bypassing research and design phases to delegate directly to a lightweight implementation agent. This approach skips full pipeline steps, producing a minimal MILESTONE.md with just enough context for quick follow-up work and verification fixes.

What is a minimal MILESTONE.md and when do I need it for task management?

A minimal MILESTONE.md provides just enough task context for handoff to an implementation agent. You need it when automating small, well-scoped follow-ups that do not require full pipeline steps, ensuring strict single-task scope before stopping.

Can I use lightweight orchestration for small follow-up fixes discovered during verification?

Yes, lightweight orchestration applies to small, well-scoped issues discovered during verification or polish. It automates implementing a single task from the PRD, creates a minimal MILESTONE.md, and stops after completing that specific task.

How do I track progress when automating single-task implementation from a PRD?

Track progress by aligning the generated MILESTONE.md with PROGRESS.md milestones for status tracking. This ensures the lightweight implementation agent updates milestone records accurately after completing the single scoped task.

What are the limitations of bypassing research phases for PRD task implementation?

Bypassing research phases limits execution to small, well-scoped tasks only. You should not use this lightweight approach for complex features requiring codebase research or design phases, as it produces minimal context and enforces strict single-task scope.