run-plan

Executes pending skills sequentially from a task_plan.md file.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill run-plan-khamel83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-plan
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/run-plan
Command: npx skills add https://github.com/Khamel83/oneshot --skill run-plan-khamel83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads a continuous plan and deterministically executes each skill step in order based on task_plan.md, updating progress and findings as it goes.

Core Features & Use Cases

  • Sequential execution: Reads task_plan.md and runs each pending skill in the defined sequence.
  • Progress tracking: Updates progress.md and findings.md with execution results and errors.
  • Beads integration: Tracks each skill as a bead task for structured task management.

Quick Start

Run the run-plan executor from your project directory to begin processing the Skill Sequence.

Frequently Asked Questions about run-plan

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

FAQPage Schema
How do I automate sequential execution of a multi-step skill plan?

Automating sequential execution requires a task_plan.md file containing a Skill Sequence table. The run-plan executor reads this file and deterministically executes each pending skill step in the defined order.

How does deterministic task execution track progress and findings?

Deterministic task execution tracks progress by automatically updating progress.md and findings.md files with execution results and errors as it processes each skill step in the sequence.

Do I need a task_plan.md file to run a planned skill sequence?

Yes, you need a task_plan.md file structured with a Skill Sequence table to run a planned skill sequence. This file defines the execution order and tracks the status of each pending skill step.

What is the best way to manage multi-step skill execution deterministically?

The best way to manage multi-step skill execution deterministically is using a beads-integrated executor that reads task_plan.md, runs pending skills sequentially, and tracks each step as a structured bead task.

Why does my skill sequence execution stop or fail to update progress?

Skill sequence execution fails to update progress if the task_plan.md lacks a properly formatted Skill Sequence table. The executor requires this structure to identify pending skills, update status, and write execution results to progress.md.