continuation

Generate next-agent continuation prompts and update task-card instructions.

26|3|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill continuation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuation
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/continuation
Command: npx skills add https://github.com/davidlee/spec-driver --skill continuation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents next-agent stalls and confusion by turning the current task state into clear, up-to-date instructions and a correctly routed handoff.

Core Features & Use Cases

  • Maintains the task card: Ensures task-card notes and a “New Agent Instructions” section are present and refreshed for the next agent.
  • Supports both prose and structured orchestration: Uses deterministic CLI-driven structured handoffs when workflow state exists, otherwise falls back to prose-only continuation.
  • Preserves delta context: When a task card is a delta, it uses notes.md plus parent delta information to keep onboarding specific and accurate.
  • Guides next actions: Identifies the next logical activity and prints instructions, including explicit preservation of unresolved assumptions and design tensions.

Quick Start

Use the continuation skill to produce a ready-to-run “next agent instructions” update for the current task card so the next agent can continue without losing context.

Frequently Asked Questions about continuation

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

FAQPage Schema
How do I hand off tasks between agents without losing context?

To hand off tasks between agents without losing context, update task-card instructions and generate a continuation prompt based on the current workflow state. This preserves delta context and unresolved assumptions, ensuring the next agent continues without stalling.

What is spec-driven development task card continuation?

Spec-driven task card continuation is the process of refreshing the "New Agent Instructions" section using current delta notes. It ensures the next agent receives specific, up-to-date context for writing, reviewing, or implementing phases within an orchestrated workflow.

How do I generate next-agent instructions for workflow orchestration?

Generate next-agent instructions by identifying the next logical activity and printing updated guidance. When workflow/state.yaml exists, invoke structured handoff CLI commands; otherwise, use prose-only continuation to route the active workflow state effectively.

Does agent handoff work without a workflow state file?

Agent handoff works without a workflow state file by falling back to prose-only continuation. If workflow/state.yaml does not exist, it updates the task card using prose instructions instead of invoking structured handoff CLI commands.

How do I preserve delta context during task card handoff?

Preserve delta context during task card handoff by using notes.md alongside parent delta information. This keeps onboarding specific and accurate, explicitly retaining unresolved design tensions and assumptions for the next agent.

When should I use structured handoff CLI commands for agent continuation?

Use structured handoff CLI commands for agent continuation when an active workflow orchestration state exists. Specifically, invoke these commands when a workflow/state.yaml file is present to ensure deterministic routing and task-card synchronization.