skills.rest
takemi-ohama
takemi-ohamaCOMMUNITY
Explore all skills by this author →
GitHub

implementation-plan

Generate implementation plans from conversation history, git log, and git diff.

Updated Jan 30, 2026
Search Tags:#planning#implementation#issues#git-diff#engineering-workflow#pr-automation
One-click install
npx skills add https://github.com/takemi-ohama/ai-plugins --skill implementation-plan-takemi-ohama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/implementation-plan
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill implementation-plan-takemi-ohama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and reference of implementation plans to ensure planning artifacts exist for features and PRs.

Core Features & Use Cases

  • Automatic plan creation when starting work or before PR submission to ensure a persisted plan under issues/.
  • Reference and reuse of existing plans to guide development and enable better traceability.
  • PR-assisted planning where the plan is generated from conversation history, git log, and git diff if no plan already exists.

Quick Start

Create or locate an issues/implementation-plan file at the start of work or when opening a PR; if missing, generate one from conversation history and repository changes.

Frequently Asked Questions about implementation-plan

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

FAQPage Schema
Does this automated planning workflow require any external dependencies or specific environment setup?▼

No external dependencies or specific environment setups are required to use the automated planning workflow. It operates directly within the repository by reading git history and creating formatted plan files under the issues/ directory.

How do I automatically generate an implementation plan from git diff and conversation history?▼

Implementation plans are automatically generated from conversation history, git log, and git diff when no existing plan is found under the issues/ directory. This ensures planning artifacts persist for features and PRs without manual formatting effort.

What's the best way to ensure planning artifacts exist before submitting a PR across multiple files?▼

Planning artifacts are ensured by automatically creating or referencing a standardized implementation plan file under the issues/ directory before PR submission. If a plan is missing, it generates one from repository changes and conversation context.

How does PR-assisted planning work when there is no existing implementation plan in the repository?▼

PR-assisted planning analyzes conversation history, git log, and git diff to auto-generate a missing implementation plan. The generated plan is formatted under issues/ with standardized naming to maintain traceability for the feature.

Can I track implementation tasks for DB migrations using an automated engineering workflow?▼

Implementation task tracking for DB migrations is supported when starting work or creating PRs across multiple files. The workflow generates and persists plan files under issues/ to guide development and enable better traceability.

Does this automated planning workflow require any external dependencies or specific environment setup?▼

No external dependencies or specific environment setups are required to use the automated planning workflow. It operates directly within the repository by reading git history and creating formatted plan files under the issues/ directory.

Related Skills

Explore More Software Engineering Skills→
shredbxshredbx

research-git-patterns

Extract implementation patterns and story context from Git history.

Community
Intermediate
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
evrendomevrendom
289

pr-creation

Automate Git pull request creation with verification, diff review, and conventional commits.

Community
Advanced
BrennonTWilliamsBrennonTWilliams
7

scope-epic

Decompose project themes into EPIC issue files and child issue stubs.

Community
Advanced