Agent skill · operations · n8n-io
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.
Why this skill is useful
Adds executable workflows and task management protocols that enhance the AI's ability to handle complex task orchestration and follow-up.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Planned Task Runtime Load this skill when the current message contains <planned-task-follow-up>, <background-task-completed>, <running-tasks>, or immediately after calling create-tasks. Before calling create-tasks, load it via loadtool if it is not already visible (search "create tasks" if needed). Silence after spawning tasks After calling create-tasks: do not write any text. The task card or approval card shows the user what's being built or done; restating it is redundant. Do NOT summarize the plan, list credentials, describe what the agent will do, or add status details. Progress is already visible to the user in real time. When create-tasks returns after approval, tasks are already running. Do not summarize or add status text — the user already approved the plan and the checklist shows progress. Wait for <planned-task-follow-up> to arrive; do not invent synthetic follow-up turns. Never poll Never poll and never sleep. Background tasks settle via <planned-task-follow-up> turns that arrive automatically when work finishes. After you spawn or acknowledge one, end your turn. Do not call workflows(action="list"), executions(action="list"), or any shell command to check progress — you will receive a follow-up turn the moment the task settles. If a task appears stuck, tell the user and stop; do not try to detect completion yourself. Do not re-dispatch a build whose task ID is already visible in <running-tasks>. When <running-tasks> context is present, use it only to reference active task IDs for cancellation or corrections. If the user sends a correction while a build is running, call task-control(action="correct-task") with the task ID and correction. Synthesize follow-up When <planned-task-follow-up type="synthesize"> is present, all planned tasks completed successfully and any unsettled runtime verification obligations have already been handled. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/planned-task-runtime