Skip to main content

​
What it does

/plan converts an approved design document into a detailed, executable implementation plan. Every task is sized to 2–5 minutes and includes exact file paths, complete code, and exact commands with expected output. The plan is saved to docs/plans/ and becomes the source of truth for the /implement command.

​
When to use

Use /plan after you have an approved design doc from /brainstorm. If you don’t have an approved design yet, run /brainstorm first.

​
Prerequisites

Planning Mode must be active in Antigravity settings while writing the plan. The plan requires deep reasoning to produce accurate task breakdowns and file paths.
  • An approved design document at docs/plans/*-design.md — if not present, run /brainstorm first.

​
Conversation mode

Planning Mode — required while writing the plan. Switch to Fast Mode when executing the plan via /implement.

​
What happens

1

Load the writing-plans skill

The writing-plans skill is loaded and followed exactly. This provides the structure and quality standards for a complete implementation plan.
2

Write the plan

Antigravity writes a comprehensive plan with bite-sized tasks (2–5 minutes each). Each task includes exact file paths, complete code, and exact commands with expected output.
3

Save the plan

The plan is saved to docs/plans/YYYY-MM-DD-<feature-name>.md.
4

Offer execution options

After saving, Antigravity presents two ways to execute:
  1. Subagent-Driven (this session) — fresh subagent per task with review. Recommended: switch to Fast Mode.
  2. Parallel Session (separate) — open a new session with the executing-plans skill.

​
Skills invoked

  • writing-plans — plan structure, task sizing, and quality standards
  • executing-plans — available for the parallel session execution path

​
Example

Antigravity reads your approved design doc, then writes a plan with tasks like:
  • Task 1: Create src/notifications/types.ts — define Notification and NotificationChannel interfaces
  • Task 2: Write failing test for NotificationService.send() in src/notifications/service.test.ts
  • Task 3: Implement NotificationService.send() in src/notifications/service.ts
Each task includes the exact code to write and the exact command to verify it passes.

/brainstorm

Step 1 — run this first to produce the design doc that /plan consumes.

/implement

Step 3 — executes the plan you just wrote, task by task.

/estimate

Run before /plan if you need time estimates before committing to implementation.

/research

Run before /plan to confirm architecture decisions with sourced findings.