How does Save Plan name the file?

It generates a descriptive name (max 5 words, kebab-case) from the plan content and uses it in the filename.

Where is the saved file stored?

The file is stored in the repository root under .aicontext/ with a plan- - .md filename.

Can I customize the filename format or location?

The default workflow saves to .aicontext/ with a timestamped plan- - .md. Customizing would require adjusting the script or workflow.

save-plan

Scanned

npx machina-cli add skill esimkowitz/claude-plugins/save-plan --openclaw

Files (1)

SKILL.md

1.1 KB

Save Plan

Saves the current plan mode document to .aicontext/ in the repository root with a timestamped, descriptive filename.

When to Use

After completing a plan in plan mode
When you want to preserve planning context for future sessions
Before exiting plan mode if the plan contains valuable architectural decisions

Steps

Get the plan file path from plan mode context (shown in system message)
Read the plan content to understand what it covers
Generate a descriptive name (max 5 words, kebab-case) summarizing the plan
Run the script:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/save-plan.sh "<descriptive-name>" "<plan-file-path>"

Example

Given plan file at ~/.claude/plans/iterative-yawning-dahl.md about refactoring authentication:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/save-plan.sh "auth-session-refactor" ~/.claude/plans/iterative-yawning-dahl.md

Output: Saved to .aicontext/plan-2026-01-14-auth-session-refactor.md

Source

git clone https://github.com/esimkowitz/claude-plugins/blob/main/plugins/save-plan/skills/save-plan/SKILL.mdView on GitHub

Overview

Save Plan writes the current plan mode document to the repository root under .aicontext/ with a timestamped, descriptive filename. This keeps planning context and architectural decisions available for future sessions and reviews. It formalizes the end-of-plan process by preserving the planning record.

How This Skill Works

The skill reads the plan file path from the plan mode context, loads the plan content, generates a descriptive, kebab-case name (limited to 5 words), and executes save-plan.sh to store the file as .aicontext/plan-<date>-<name>.md in the repo.

When to Use It

After completing a plan in plan mode
When you want to preserve planning context for future sessions
Before exiting plan mode if the plan contains valuable architectural decisions
When documenting decisions for a specific sprint or release
If you need a historical record for audits or reviews

Quick Start

Step 1: Get the plan file path from plan mode context (shown in system message)
Step 2: Read the plan content to understand what it covers and generate a descriptive name
Step 3: Run the script: bash ${CLAUDE_PLUGIN_ROOT}/scripts/save-plan.sh "<descriptive-name>" "<plan-file-path>"

Best Practices

Keep the descriptive name within 5 words and in kebab-case
Verify the plan file path and ensure the plan content is up-to-date before saving
Ensure the repository root contains a .aicontext/ directory or allow the script to create it
Use a consistent timestamp format in filenames for easy sorting
Review the saved file to confirm it captured the intended planning decisions before committing

Example Use Cases

Saved auth-session-refactor plan from ~/.claude/plans/iterative-yawning-dahl.md to .aicontext/plan-2026-01-14-auth-session-refactor.md
Saved payment-flow-resilience plan from ~/.claude/plans/quarterly/payment-flow.md to .aicontext/plan-2026-02-03-payment-flow-resilience.md
Saved data-mesh-optimization plan from ~/.claude/plans/quarterly/data-mesh.md to .aicontext/plan-2026-02-18-data-mesh-optimization.md
Saved api-gateway-hardening plan from ~/.claude/plans/security/gateway.md to .aicontext/plan-2026-03-07-api-gateway-hardening.md
Saved mobile-login-flows plan from ~/.claude/plans/iterations/mobile-login.md to .aicontext/plan-2026-03-12-mobile-login-flows.md

Frequently Asked Questions

Add this skill to your agents