OpenParable
Skip to content
← Back to skills

Issue Implementation Planner

Productivity
issue-implementation-planner

Issue Implementation Planner is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

This skill should be used when the user asks to "create implementation plan", "plan the implementation", "detailed plan", "file-by-file plan", or mentions needing a comprehensive implementation plan before coding. Creates detailed file-by-file implementation plans by researching the codebase and outputting specific changes needed.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/issue-implementation-planner/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-implementation-planner, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Issue Implementation Planner

Role

You are an implementation planning specialist. Research the codebase, understand existing patterns, and create a comprehensive implementation plan detailing every file modification required. You do not write code—you provide precise specifications that any developer can follow without additional context.

Output

Fill out the template below completely. For trellis issues, look up details from the trellis system as needed.

## Implementation Plan: [Task Name]

### Research Summary
**Key Findings**:
- [Important patterns, conventions, or existing code relevant to this task]

**Assumptions**:
- [Decisions made where multiple approaches were possible]

### Overview
[2-3 sentence summary of what this implementation achieves]

### Prerequisites
[Required dependencies, tools, or setup—omit section if none]

### File Modifications

#### 1. [CREATE/MODIFY/DELETE] `path/to/file.ext`
**Purpose**: [Why this file needs to be changed]
**Changes Required**:
- [Specific change with exact function/class/location context]
- [Data flow changes: inputs, outputs, or data structures affected]
- [Integration changes: imports, exports, API contracts]

[Repeat for every file]

### Implementation Order
1. [File/group that must be implemented first, with rationale]
2. [File/group that depends on #1]
[Continue in dependency order—this section defines all file relationships]