run-plan

Load, validate, and execute plan tasks in dependency order.

124|22|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/tmdgusya/engineering-discipline --skill run-plan-tmdgusya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-plan
Source: https://github.com/tmdgusya/engineering-discipline/tree/main/skills/run-plan
Command: npx skills add https://github.com/tmdgusya/engineering-discipline --skill run-plan-tmdgusya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the execution of a written implementation plan by loading the plan, critically reviewing it, and carrying out tasks in dependency order using a worker-validator loop to enforce verification and prevent drift.

Core Features & Use Cases

  • Load and review a plan document before execution to ensure clarity and feasibility.
  • Execute tasks in dependency order with explicit compliance checks, parallelization where safe, and independent worker/validator roles.
  • Provide progress reporting and guardrails to stop on blockers or ambiguities, ensuring safe plan execution.

Quick Start

Load a plan document, review it thoroughly, and start executing tasks with a worker-validator loop.

Frequently Asked Questions about run-plan

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

FAQPage Schema
How do I automate execution of a written implementation plan in dependency order?

Automating plan execution requires loading a plan document, validating its steps and dependencies, and driving tasks sequentially using a worker-validator loop to enforce verification and prevent drift.

What is a worker-validator loop in task orchestration?

A worker-validator loop in task orchestration separates task execution from compliance checking, using independent roles to verify acceptance criteria and ensure safe, drift-free plan execution.

Can I parallelize tasks when executing a software engineering implementation plan?

Yes, you can parallelize tasks in plan execution where safe, utilizing separate worker and validator roles to manage independent task streams while maintaining dependency order guardrails.

Do I need acceptance criteria to execute tasks with structured orchestration?

Yes, structured task orchestration requires a clearly defined plan with explicit steps, dependencies, and acceptance criteria to validate task completion and report progress accurately.

What happens if the plan execution encounters ambiguities or blockers?

Plan execution includes guardrails that automatically stop the workflow when encountering blockers or ambiguities, preventing drift and ensuring safe execution until issues are resolved.

Does task orchestration work without a pre-written plan document?

No, task orchestration applies to software engineering projects where a clearly defined plan document governs task sequencing, verification, and progress reporting throughout execution.