apply-step

Implements one plan step test-first against gokit's engineering baseline and validates affected modules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-step implementation plan requires carrying forward decisions from earlier steps; this Skill loads the full plan context and implements exactly one step correctly, test-first, without contradicting prior work. ## Core Features & Use Cases - Context-Aware Execution: Reads the plan README and all previous steps before editing, so naming, layering, and API decisions stay consistent across the plan. - Test-First Implementation: Enforces TDD (failing test, minimal code, refactor) plus gokit's engineering baseline: canonical reuse, typed APIs, acyclic layering, and no shims. - Validation and Sign-Off: Runs scoped module validation under -race -shuffle, structure checks, and review passes before marking the step done. - Use Case: Given tmp/storage-gcs-backend/02-registry.md, implement that step's actions, validate the touched Go modules, and flip its status to done so apply-plan can resume. ## Quick Start Apply step 02 of the plan in tmp/storage-gcs-backend by implementing it test-first and validating the affected modules.

Frequently Asked Questions about apply-step

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

FAQPage Schema
How do I implement one step of a multi-step coding plan?▼

Provide the path to one step file, such as tmp/plan-name/02-registry.md. The step is implemented test-first after reading the plan README and all previous steps, then validated and marked done when acceptance criteria pass.

What happens if a plan step depends on an unfinished step?▼

Execution stops before any edits. The step's declared dependencies must be marked done first; if a dependency is unfinished, the Skill reports the blocker instead of proceeding.

Does this enforce test-driven development for Go code?▼

Yes. Each behavior follows failing test, minimal code, then refactor while green, including failure paths. Production code is never written before its tests, and affected modules must pass validation under -race -shuffle.

Can I commit or open a PR after applying a step?▼

No. Edits are left uncommitted on a branch for the maintainer to commit and push. A pull request is opened only when explicitly requested, and branches are named by the change, not by step numbers.

What are the limitations of applying a single plan step?▼

The edit scope is fixed to the step's listed files; mis-scoped steps are reported rather than silently expanded. It also cannot override the repository's engineering baseline or contradict decisions from completed steps.