---
name: Plan
slug: plan-6
category: Automation
description: Plan structures non-trivial coding work into phases, tasks, dependencies, and validation before any edits. Use it when a request spans multiple files or needs sequencing decisions.
github: "https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/plan"
language: JavaScript
stars: 210
forks: 27
install: "npx degit https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/plan ~/.claude/skills/plan"
installs_to: ~/.claude/skills/plan
source_path: skills/plan/SKILL.md
collection_size: 11
category_size: 1860
collection_url: "https://dirskills.com/collections/Joonghyun-Lee-Frieren/oh-my-antigravity"
added: 2026-09-04T05:26:21.891Z
last_synced: 2026-09-04T05:26:21.891Z
canonical_url: "https://dirskills.com/skills/plan-6"
---

# Plan

Plan structures non-trivial coding work into phases, tasks, dependencies, and validation before any edits. Use it when a request spans multiple files or needs sequencing decisions.

**Install:**

```bash
npx degit https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/plan ~/.claude/skills/plan
```

## README

## Purpose

Use this skill when the request is non-trivial and should be planned before editing code.

## Trigger

- User asks for strategy, roadmap, or migration plan
- Scope touches multiple files or subsystems
- Work needs sequencing or parallelization decisions

## Workflow

1. Restate goals, constraints, and acceptance criteria.
2. Inspect only the repository areas required for planning.
3. Keep this stage read-only (no edits).
4. Break work into phases and atomic tasks.
5. Mark dependencies, critical path tasks, and parallelizable sidecars.
6. Add validation checkpoints and rollback notes.
7. List 3-5 critical files for implementation focus.

## Output Template

```markdown
## Goal
- ...

## Phase Plan
1. Phase 1 - ...
2. Phase 2 - ...

## Task Breakdown
1. ...
2. ...

## Critical Files
- ...

## Risks
- ...

## Validation
- ...
```

## Notes

- Delegate architecture tradeoffs to `oma-architect` when needed.
- Keep plans executable and testable, not abstract.