cmd-workflow-write-plan

Create structured implementation plans with exact file paths, tests, and commits.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill cmd-workflow-write-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-workflow-write-plan
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-workflow-write-plan
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-workflow-write-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured implementation plan from user requirements that specifies exact file paths, tests, and commits.

Core Features & Use Cases

  • Generates step-by-step tasks with exact paths for new features or refactors.
  • Enforces bite-sized tasks (2-5 minutes) and idempotent steps to ensure repeatable workflows.
  • Saves plans to a deterministic location: docs/plans/YYYY-MM-DD-<feature-name>.md.

Quick Start

Use a project requirement and I will generate a complete plan ready for review and execution.

Frequently Asked Questions about cmd-workflow-write-plan

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

FAQPage Schema
How do I create a structured implementation plan from feature requirements?

To create a structured implementation plan, provide your feature requirements to generate step-by-step tasks specifying exact file paths, tests, and commits. The plan enforces bite-sized, idempotent tasks and saves to docs/plans/YYYY-MM-DD-<feature-name>.md for review and execution.

What is the best way to plan refactoring tasks using test-driven development?

Planning refactoring tasks with test-driven development involves generating a plan that integrates TDD sequencing and bite-sized tasks. This approach specifies exact file paths and tests needed for each step, ensuring repeatable workflows before you begin coding the refactor.

How do I break down software features into bite-sized tasks for development?

To break down software features into bite-sized tasks, use a planning tool that enforces 2-5 minute task durations and idempotent steps. This ensures each generated task specifies exact file paths, tests, and commits for a repeatable development workflow.

Can I generate a development plan for a new feature without writing code first?

Yes, you can generate a complete development plan before writing any code. By supplying a project requirement, the tool outputs a step-by-step plan with exact file paths, tests, and commits saved as a markdown file, ready for execution.

Where should I save implementation plans for new software features?

Implementation plans for new software features should be saved to a deterministic location: docs/plans/YYYY-MM-DD-<feature-name>.md. This structured file path ensures plans are organized by date and feature name for easy retrieval.