apply-plan

Executes remaining steps of a plan folder in dependency order with validation.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/kbukum/gokit --skill apply-plan-kbukum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apply-plan
Source: https://github.com/kbukum/gokit/tree/main/.github/skills/apply-plan
Command: npx skills add https://github.com/kbukum/gokit --skill apply-plan-kbukum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step implementation plans often get interrupted or partially completed, leaving developers unsure where to resume and risking skipped dependencies or unvalidated changes. This Skill drives a plan folder under tmp/ to completion by resuming from the first unfinished step and validating after each one. ## Core Features & Use Cases - Resumable execution: Reads the plan README and step files to find the first step not marked done, then continues in dependency order. - Step-by-step validation: Runs the validate workflow after each step and stops on failure rather than forcing a green result. - Idempotent and reviewable: Each step stays a standalone, reviewable unit; work is left uncommitted for the maintainer to commit. - Use Case: You have a plan folder tmp/storage-gcs-backend/ with five steps, two already done. Invoke this Skill to apply steps three through five in order, validating the affected Go modules after each. ## Quick Start Apply the remaining steps of the plan in tmp/storage-gcs-backend/ and validate after each step.

Frequently Asked Questions about apply-plan

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

FAQPage Schema
How do I resume an interrupted implementation plan?▼

Point the Skill at the plan folder under tmp/ and it finds the first step not marked done by reading each step file's Status field and acceptance checkboxes. Execution resumes from that step in dependency order.

How to execute a multi-step coding plan step by step?▼

The Skill reads the plan README for the ordered step index and dependency order, then applies each remaining step individually using the apply-step workflow. Each step is validated before moving to the next, keeping every change a standalone reviewable unit.

What happens if a plan step fails validation?▼

Execution stops on a red validation run and does not proceed to the next step. If a step's acceptance criteria cannot be met as written, the Skill reports the divergence instead of forcing a green result, since the plan may need revision.

Does applying a plan commit or push changes automatically?▼

No. Work is done on a branch cut from an up-to-date main, but all edits are left uncommitted. The maintainer commits and pushes, and a pull request is opened only when explicitly requested.

Can a step run before its dependencies are finished?▼

No. A step is eligible only when every step it depends on is already marked done. The Skill never starts a step ahead of an unfinished dependency and never batches multiple steps into one change.