work-plan

Creates structured execution plans for infrastructure, configuration, and documentation work without testable behavior.

Updated Jul 4, 2023
One-click install
npx skills add https://github.com/kohdice/dotfiles --skill work-plan-kohdice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-plan
Source: https://github.com/kohdice/dotfiles/tree/main/config/agents/skills/work-plan
Command: npx skills add https://github.com/kohdice/dotfiles --skill work-plan-kohdice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-TDD work like Terraform changes, Nix configuration, CI pipelines, and documentation lacks a Red-Green test gate, so it is easy to execute ad hoc without verifiable completion criteria. This Skill produces a structured plan file where every work item carries a concrete verification step and expected outcome. ## Core Features & Use Cases - Verify-Required Planning: Every work item includes a Verify step with a command and concrete expected outcome, replacing TDD's test gate for non-application work. - Apply-Tier Safety: Live-state mutations (terraform apply, nix switch, kubectl apply) are marked as apply items, gated behind validation steps, and carry explicit Rollback instructions. - Portable Plan Files: Plans are written to .plans/ as self-contained Markdown that a fresh executor, agent, or human can run with zero session context. - Use Case: You need to migrate Terraform state to an S3 backend. The Skill analyzes the repository, identifies check commands like terraform plan, and writes .plans/s3-state-backend.md with ordered, verifiable tasks ready for execution. ## Quick Start Ask the agent to create a work plan for your infrastructure or configuration change, for example: plan the migration of our CI release pipeline to a new workflow.

Frequently Asked Questions about work-plan

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

FAQPage Schema
How do I plan infrastructure changes without tests?▼

Create a work plan where each item has a Verify step: a command like terraform plan or nix flake check plus the concrete expected output. This substitutes for TDD's Red-Green gate by making pass or fail mechanically decidable.

When should I use work-plan instead of TDD planning?▼

Use work-plan when the change has no automatically testable application behavior, such as Terraform, Nix, CI pipelines, documentation, or migrations. If the change alters testable application behavior, route it to tdd-plan instead.

What is a Task (apply) item in a work plan?▼

A Task (apply) item marks any live-state mutation such as terraform apply, nix run .#switch, or kubectl apply. It must be gated by prior validation items, carry a Rollback line, and is never executed without explicit user confirmation.

Where are work plan files stored?▼

Plan files are written to the .plans/ directory at the project root with descriptive kebab-case filenames like s3-state-backend.md. The file is self-contained so a fresh executor can run it without the original conversation.

What happens if a work item cannot be verified?▼

An item whose Verify step cannot be written is not plannable yet. It must be split into smaller items, clarified with the requester, or escalated as an open question before the plan is finalized.