run-plan

Execute approved plan.md steps while enforcing governance gates and preventing publication.

14|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hungv47/meta-skills --skill run-plan-hungv47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-plan
Source: https://github.com/hungv47/meta-skills/tree/main/skills/meta/run-plan
Command: npx skills add https://github.com/hungv47/meta-skills --skill run-plan-hungv47

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates the execution of an approved plan.md by stepping through its steps and preventing any publish.

Core Features & Use Cases

  • Automatically executes an approved plan by stepping through ready tasks, while enforcing gating rules.
  • Narrates each step's application and status, keeping humans informed.
  • Honors publication and governance gates, stopping the run with no artifacts published or auto-approved.

Quick Start

Run the executor on an approved plan at .forsvn/runs/<slug>/plan.md to see narrated steps and gated halts.

Frequently Asked Questions about run-plan

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

FAQPage Schema
How do I execute an approved plan step-by-step while preventing automatic publishing?

To execute an approved plan step-by-step while preventing auto-publishing, this Skill orchestrates plan.md execution by stepping through tasks and halting at publish, spend, or irreversible gates. It ensures no artifacts are auto-published or auto-approved during the run.

What is plan execution gating and how does a governor check work?

Plan execution gating is a control mechanism that compares a plan's gates with live capability gates before each step. The governor check halts the run at irreversible, spend, or publish gates, preventing unauthorized actions and ensuring safe plan execution.

How do I run an executor on an approved plan stored in the .forsvn/runs directory?

To run an executor on an approved plan located at .forsvn/runs/<slug>/plan.md, the Skill automatically steps through ready tasks, narrates each applied play, and stops at governance gates without auto-publishing artifacts.

Can I use governor and plan APIs to advance or stop an automated workflow?

Yes, you can use bun bin/governor.ts and bin/plan.ts APIs to advance or stop an automated workflow. The Skill enforces gating via a governor check before each step, comparing the plan gate with live capability gates to determine whether to proceed or halt.

Does the plan runner support narration of applied plays during task execution?

Yes, the plan runner supports narration of applied plays during task execution. It narrates each step's application and status, keeping humans informed while honoring publication and governance gates by stopping the run safely.

What are the limitations of automated plan execution when hitting irreversible gates?

When hitting irreversible gates, the limitation is that the automated plan execution stops completely. The executor halts the run at publish, spend, or irreversible gates, ensuring no artifacts are published or auto-approved without explicit human intervention.