create-implementation-plan

Create machine-readable implementation plans with atomic tasks and validation criteria.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shysssthanhtri/AI-tools --skill create-implementation-plan-shysssthanhtri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-implementation-plan
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/create-implementation-plan
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill create-implementation-plan-shysssthanhtri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity from project handoffs by producing machine-readable, deterministic implementation plans that can be executed by AI agents or engineering teams without further clarification.

Core Features & Use Cases

  • Deterministic Plans: Enforces a strict template and validation rules so outputs are parseable and reproducible.
  • Atomic Phases & Tasks: Breaks work into independent phases and executable tasks with explicit file paths, identifiers, and acceptance criteria.
  • AI-to-AI Execution: Tailored for automated workflows where another agent will consume the plan, validate template compliance, and perform changes.
  • Use Case: Preparing a release plan for upgrading a core dependency that includes exact file edits, tests to add, and automated validation steps.

Quick Start

Create an implementation plan for upgrading the payment library to version 3.0 that lists atomic tasks, file paths, validation checks, and the final status badge format.

Frequently Asked Questions about create-implementation-plan

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

FAQPage Schema
How do I create machine-readable implementation plans for AI agents?

Implementation plans are structured Markdown files with front matter, atomic phased tasks, explicit file paths, and validation criteria. They are needed when AI agents or engineering teams require deterministic, task-level instructions for features, refactors, or infrastructure changes without further clarification.

How do I generate a deterministic task plan for a dependency upgrade?

Implementation plans support features, refactors, package upgrades, design changes, architecture modifications, and infrastructure work. They are tailored for automated AI-to-AI workflows where another agent consumes the plan, validates template compliance, and performs the changes.

Does this implementation plan template work for automated AI-to-AI execution?

Yes, implementation plans are tailored for automated workflows where AI agents consume the plan, validate template compliance, and perform changes. They enforce strict templates, atomic phased tasks with explicit file paths, and validation criteria to ensure outputs are parseable and reproducible.

What is the best way to structure task-level instructions for engineering teams?

Implementation plans require a standardized naming convention, storage under /plan/, structured Markdown front matter, atomic phased tasks with explicit file paths, and fully machine-parseable identifiers. No external dependencies are needed, as the focus is on deterministic, reproducible template enforcement.

When do I need a deterministic implementation plan instead of a regular task list?

Implementation plans are tailored for automated AI-to-AI workflows where another agent consumes the plan, validates template compliance, and performs changes. They enforce strict templates, atomic phased tasks with explicit file paths, and validation criteria to ensure outputs are parseable and reproducible.

What format do implementation plans use for automated validation?

Implementation plans require a standardized naming convention, storage under /plan/, structured Markdown front matter, atomic phased tasks with explicit file paths, and fully machine-parseable identifiers. No external dependencies are needed, as the focus is on deterministic, reproducible template enforcement.