# Implementation Plan Template

Use this for changes that touch multiple files, alter operational behavior, or add new repository conventions.

## Goal

State the operational or maintenance outcome.

## Current State

Summarize the directories and conventions inspected.

## Scope

List files or directories expected to change.

## Non-Goals

Name what will not be redesigned, renamed, deleted, or claimed as complete.

## Plan

1. Inspect relevant scripts, playbooks, docs, and examples.
2. Make the smallest structural or documentation changes needed.
3. Update validation or runbook guidance.
4. Run focused checks.
5. Summarize residual risk and follow-ups.

## Validation

List commands to run, including fallback behavior for missing tools.

## Risks

Call out destructive operations, platform assumptions, missing lab environments, or checks that require real systems.