continue-task

Advance an in-progress task to its next dev-loop checkpoint from task-status files.

1|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ezagent42/prd2impl --skill continue-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continue-task
Source: https://github.com/ezagent42/prd2impl/tree/main/skills/skill-6-continue-task
Command: npx skills add https://github.com/ezagent42/prd2impl --skill continue-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resume a task in_progress by determining its last checkpoint and advancing to the next dev-loop step, minimizing manual coordination.

Core Features & Use Cases

  • Determine current task state from task-status.md or tasks.yaml and verify in_progress status.
  • Progress a task through the dev-loop stages (eval → test-plan → test-code → implement → test-run → complete) with autopilot options.
  • Update artifacts and status accordingly, handling user approvals or blockers to ensure reliable completion.

Quick Start

Use the /continue-task command with the Task ID to advance the in_progress task to its next checkpoint.

Frequently Asked Questions about continue-task

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

FAQPage Schema
How do I resume an in-progress task and advance it to the next workflow checkpoint?

To resume an in-progress task, the system identifies its last checkpoint from tasks.yaml or task-status.md and advances it to the next dev-loop stage, updating artifacts and status automatically to minimize manual coordination.

What are the sequential stages in the dev-loop for task automation?

The dev-loop progresses sequentially through eval, test-plan, test-code, implement, test-run, and complete stages. The automation advances tasks through these checkpoints, handling artifacts progression and user confirmations along the way.

How can I automate task progression without manual approval at every checkpoint?

You can automate task progression by using autopilot settings to override STOP points. This allows the workflow to advance continuously through dev-loop checkpoints without requiring manual user confirmations at each stage.

How do I track task status and artifacts during the development loop?

Task status and artifacts are tracked using tasks.yaml or task-status.md files. The system determines the current state from these files and produces updated task-status and artifacts as it advances to each new checkpoint.

Can I use continue-task to bypass STOP points in my workflow?

Yes, you can bypass STOP points by providing autopilot overrides. Unless an autopilot setting is applied, the system will respect STOP points and pause task progression until user confirmation is received.

What is the best way to handle blockers when automating task progression?

Handling blockers during task progression involves respecting STOP points and managing user approvals. The system pauses advancement when blockers occur, ensuring reliable completion by waiting for manual intervention or autopilot configuration.