create-plan

Creates reviewable multi-step implementation plans as markdown files under a gitignored tmp folder.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial changes in the gokit repository need a written, reviewable contract before any code is touched. This Skill turns a feature, refactor, parity port, or release into a structured plan folder that other skills can execute iteratively, eliminating ad-hoc or untracked planning. ## Core Features & Use Cases - Standardized plan structure: Generates a README overview plus zero-padded, dependency-ordered step files (01-core.md, 02-...) under the gitignored tmp/<plan-name>/ directory. - Baseline-bound rules: Every plan restates gokit's engineering baseline — test-first TDD, acyclic layering, canonical reuse, typed minimal APIs, and no compatibility shims. - Progress tracking: Each step carries a Status field and checkbox acceptance criteria that the apply-plan and apply-step skills read and flip as work lands. - Use Case: When scoping a new storage backend, invoke this Skill to produce tmp/storage-gcs-backend/ with an indexed README and per-layer step files, each mapping to a standalone reviewable change. ## Quick Start Ask the assistant to create a plan for adding a GCS storage backend, and it will write the README and numbered step files under tmp/storage-gcs-backend/.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create an implementation plan for a gokit change?▼

Invoke the create-plan skill with a description of the change. It creates a kebab-case folder under tmp/ containing a README overview and, for multi-step work, numbered step markdown files ordered by dependency layer.

Where are gokit plans stored and are they committed?▼

Plans live under tmp/<plan-name>/ at the repo root. The tmp directory is gitignored, so plans are local working scratch that are never committed or shipped.

What goes into each step file of a plan?▼

Each step file has a title, layer, dependency and blocking info, a status field, scope, numbered concrete actions at real file paths, files touched, and checkbox acceptance criteria including test-first verification with -race -shuffle.

How are plans executed after being created?▼

Plans are applied with the apply-plan skill for the whole plan or apply-step for a single step. These skills read the Status field and checkboxes to find the first unfinished step and mark it done when it lands.

When should a plan use a single README instead of step files?▼

A genuinely small single-shot change can be one README with an inline step list. Split into numbered step files as soon as the work is iterative or spans multiple layers.