# Write Implementation Plan

> Forces the agent to research and write a structured implementation plan before writing any code.

- Skill: `j4flmao/write-implementation-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add j4flmao/write-implementation-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/j4flmao/write-implementation-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: j4flmao (https://skillmd.com/u/j4flmao)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/j4flmao/write-implementation-plan

---


# ⚠️ MANDATORY DIRECTIVE: PLAN BEFORE EXECUTION

**DO NOT WRITE ANY CODE UNTIL `implementation_plan.md` IS DRAFTED AND APPROVED.**

## 1. THE PLANNING WORKFLOW

```mermaid
%%{init: {"theme": "default", "flowchart": {"useMaxWidth": true}}}%%
flowchart TD
    A[Task Received] --> B[Codebase Research]
    B --> C[Draft implementation_plan.md]
    C --> D{User Approval?}
    D -- No --> E[Refine Plan]
    E --> C
    D -- Yes --> F[Execute Code Changes]
    F --> G[Verify Output]
```

## 2. PLAN STRUCTURE REQUIREMENTS

Your `implementation_plan.md` MUST adhere strictly to this template:

### I. GOAL
State the exact objective. 1-2 sentences maximum. No fluff.

### II. OPEN QUESTIONS
Expose all ambiguities and missing context immediately using GitHub Alerts:
> [!WARNING]
> [Question or missing context here]

### III. PROPOSED CHANGES
Itemize file changes using strict tagging:
- `[NEW]` path/to/new_file.ext
- `[MODIFY]` path/to/existing_file.ext
- `[DELETE]` path/to/dead_file.ext

### IV. VERIFICATION PLAN
Actionable, exact steps to prove the implementation works.

## 3. RULES OF ENGAGEMENT
- **CONCISE & DENSE:** Zero preamble. Maximum information density.
- **AUTHORITATIVE:** State facts. Eliminate "I think" or "Maybe".
- **RESEARCH FIRST:** Blind planning is forbidden. Read files before proposing changes.