exec-simple

Execute one uncompleted task section from a markdown plan file.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/mkoziy/skills --skill exec-simple
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exec-simple
Source: https://github.com/mkoziy/skills/tree/main/.claude/skills/exec-simple
Command: npx skills add https://github.com/mkoziy/skills --skill exec-simple

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the controlled execution of a single unfinished task from a markdown plan file, enabling stepwise progress without automatic logging.

Core Features & Use Cases

  • Executes exactly one uncompleted task section from a plan file, then stops.
  • Skips completed tasks and marks non-automatable items for manual follow-up.
  • Use cases include plan-driven workflows, incremental verification, and guided task orchestration.

Quick Start

Provide the path to a plan file and run exec-simple to execute the first uncompleted task.

Frequently Asked Questions about exec-simple

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

FAQPage Schema
How do I execute a markdown plan file one task at a time?

To execute a markdown plan file one task at a time, provide the plan file path to the automation workflow. It reads ### Task N: or ### Iteration N: sections and runs exactly one uncompleted task before stopping.

What is the best way to automate stepwise task execution without progress logging?

The best way to automate stepwise task execution without progress logging is using a plan-driven workflow that processes one uncompleted task section and halts, skipping completed items and returning <<<ALL_TASKS_DONE>>> when finished.

How does a plan-driven workflow handle non-automatable checkboxes?

A plan-driven workflow handles non-automatable checkboxes by recognizing the [x] mark within the plan structure. It skips these completed or manual items to advance only to the next uncompleted [ ] checkbox section.

Does stepwise plan execution work with custom markdown task formats?

Stepwise plan execution requires specific markdown task formats to function correctly. It relies on parsing ### Task N: or ### Iteration N: headers alongside [ ] and [x] checkboxes to identify and execute the next actionable item.

Why does my plan automation stop after running a single task section?

Plan automation stops after running a single task section because it is designed for controlled, stepwise progress. This prevents runaway execution by halting after completing one uncompleted task, allowing incremental verification before proceeding.

When should I not use automated stepwise task execution for my workflow?

You should not use automated stepwise task execution if your workflow requires continuous, unattended batch processing or automatic progress logging. It is built specifically for controlled, single-step advancement and manual verification.