skills.rest
jmrplens
jmrplensCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-implementation-plan

Generates structured implementation plan Markdown files for features, refactoring, and upgrades.

37|4|Updated Apr 11, 2026
Search Tags:#planning#markdown#refactoring#feature development#ai agents#task breakdown#implementation plan
One-click install
npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill create-implementation-plan-jmrplens
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-implementation-plan
Source: https://github.com/jmrplens/gitlab-mcp-server/tree/main/.github/skills/create-implementation-plan
Command: npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill create-implementation-plan-jmrplens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing implementation plans that both humans and AI agents can execute consistently is hard; this Skill produces deterministic, machine-readable plan files with a strict template so work can be executed autonomously without ambiguity. ## Core Features & Use Cases - Standardized Plan Template: Enforces a mandatory Markdown structure with front matter, requirements, phased tasks, dependencies, risks, and testing sections. - AI-Optimized Output: Uses unambiguous language, standardized identifier prefixes (REQ-, TASK-, GOAL-), and tables so plans are parseable and executable by AI agents. - Use Case: When starting a package upgrade or new feature, ask for an implementation plan and receive a complete file saved to the /plan/ directory with phases, task tables, status badges, and validation criteria. ## Quick Start Create an implementation plan for upgrading the authentication module to the new token-based system.

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 an implementation plan for a new feature?▼

Invoke the skill with the plan purpose, such as the feature name, and it generates a complete Markdown plan file. The output follows a mandatory template with requirements, phased tasks, dependencies, and testing sections saved to the /plan/ directory.

What is the file naming convention for implementation plans?▼

Plan files use the pattern [purpose]-[component]-[version].md, where purpose is one of upgrade, refactor, feature, data, infrastructure, process, architecture, or design. An example is feature-auth-module-1.md.

Where are implementation plan files saved?▼

Plans are saved in the /plan/ directory, which is gitignored as local working notes per ADR-0013. Plans are never committed, so anything that must persist goes into an ADR or a GitHub issue.

What status values can an implementation plan have?▼

The status field in the front matter must be one of Completed, In progress, Planned, Deprecated, or On Hold. Each status also appears as a colored badge in the plan's introduction section.

What sections must an implementation plan template include?▼

The mandatory sections are Introduction, Requirements & Constraints, Implementation Steps with phases and task tables, Alternatives, Dependencies, Files, Testing, Risks & Assumptions, and Related Specifications. All headers must match exactly and no placeholder text may remain.

Related Skills

Explore More Software Engineering Skills→
atomicinnovationatomicinnovation
30

create-adr

Create architecture decision records with context, alternatives, and consequences.

Official
Advanced
XentinusXentinus

task-execution

Executes pending task phases by validating prerequisites, running tests, and updating task status files.

Community
Intermediate
jkhowlandjkhowland

plan-eng-review

Identify engineering plan gaps across architecture, data flow, edge cases, tests, and performance.

Community
Advanced
davepoondavepoon
3.4k

gsd:quick

Executes small ad-hoc tasks with atomic commits and STATE.md tracking in the GSD workflow.

Community
Advanced