continue

Resume paused stories or tasks by locating progress files and executing one workflow step.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill continue-is-ivanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continue
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/continue
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill continue-is-ivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams safely resume partially completed development work without losing context, skipping required workflow steps, or forgetting to update progress tracking. It is especially useful when a story or task spans multiple sessions and must continue in a strict, auditable sequence.

Core Features & Use Cases

  • Progress-aware resumption: Finds the active story or task, reads its progress file, and selects the next actionable work unit.
  • Workflow enforcement: Routes each checkbox type to the correct sub-skill flow, including testing, refactoring, coverage, design alignment, and acceptance handling.
  • Tracking and status updates: Updates progress records, story phase tables, and completion state, including moving finished tasks to done.
  • Use Case: After stopping midway through a backend story, use this Skill to reopen the correct progress file, execute the next red or green phase with the required review steps, commit the result, and report what comes next.

Quick Start

Ask the AI to continue story 5 or task 2 so it finds the next work unit, executes exactly one full step, updates progress, and stops with a status report.

Frequently Asked Questions about continue

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

FAQPage Schema
How do I resume a paused development story without losing workflow context?

You can resume paused story execution by locating the active progress file, selecting the next actionable work unit, and completing exactly one controlled workflow step with enforced commit discipline and status updates.

What is the best way to enforce a single step in a red green refactor cycle?

Enforcing single step execution during red green refactor cycles is achieved by routing the current checkbox type to the required sub-skill flow, executing one full step, updating progress tracking, and stopping with a status report.

How does task resumption maintain progress management across multiple sessions?

Task resumption maintains progress by reading the active progress file, executing the next work unit, updating progress records and story phase tables, and moving finished tasks to done within a strict, auditable sequence.

Can I use automated story tracking for backend acceptance testing and design alignment?

Yes, story tracking applies to structured software delivery scenarios involving acceptance testing, design alignment, adapter discovery, and backlog promotion by dispatching required sub-skills and enforcing stop on failure behavior.

Why does my workflow stop after completing one task step?

Your workflow stops after one step because single step execution is enforced to ensure required review steps, commit discipline, and test result reporting are completed before proceeding to the next work unit.

Does agent dispatch support test orchestration for partially completed tasks?

Agent dispatch supports test orchestration by routing checkbox types to the correct sub-skill flow, executing one controlled step, reporting test results, and stopping on failure to ensure safe task resumption.