create-implementation-plan

Decompose solution designs into granular, verifiable implementation steps.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill create-implementation-plan-thermiteau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-implementation-plan
Source: https://github.com/thermiteau/maverick/tree/main/skills/create-implementation-plan
Command: npx skills add https://github.com/thermiteau/maverick --skill create-implementation-plan-thermiteau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a solution design into granular, verifiable implementation steps with scope control, enabling predictable progress from design to implementation.

Core Features & Use Cases

  • Principles: Each step is independently verifiable; each step is independently committable; steps are small; steps are ordered by dependency; the sum of all steps satisfies the design.
  • Process: Identify logical units of work, order by dependency, define verification for each step, and apply scope constraints to ensure the plan remains within bounds.
  • Use Case: A product team uses this approach to convert a high-level design into a sequence of small, testable changes that can be reviewed and merged safely.

Quick Start

Draft a step-by-step implementation plan from a design document that is small, verifiable, and executable.

Frequently Asked Questions about create-implementation-plan

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

FAQPage Schema
How do I break a solution design into verifiable implementation steps?

To break a solution design into verifiable implementation steps, identify logical units of work, order them by dependency, and define explicit verification methods and scope constraints for each independent, committable step.

What is an incremental implementation plan in software engineering?

An incremental implementation plan in software engineering is a sequence of small, independently verifiable, and committable steps ordered by dependency that collectively satisfy a high-level solution design.

How do I scope project planning to ensure steps are independently committable?

Scope project planning by applying explicit scope constraints to each step, ensuring the implementation plan remains within bounds while keeping every step small enough to be independently reviewed and merged.

When do I need to define explicit verification methods for implementation steps?

You need to define explicit verification methods for implementation steps when converting a high-level design into a sequence of small, testable changes that a product team can review and merge safely.

What is the best way to order implementation steps by dependency?

The best way to order implementation steps by dependency is to identify logical units of work within the solution design and sequence them so that each incremental step builds upon the previous committable changes.