skills.rest
fryanpan
fryanpanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

persist-plan

Copies ephemeral session plans from .claude/plans/ into version-controlled docs/product/plans/ files.

Updated May 12, 2026
Search Tags:#documentation#markdown#claude code#persistence#linear#git commit#plan mode
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill persist-plan-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persist-plan
Source: https://github.com/fryanpan/ai-team-lead/tree/main/plugin/team-lead-fleet/skills/persist-plan
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill persist-plan-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans created during Claude Code plan mode live in the ephemeral .claude/plans/ directory and are lost when sessions end, leaving no permanent record of design decisions in the project repository. ## Core Features & Use Cases - Plan Discovery: Locates the active plan file from context or by scanning .claude/plans/*.md for the most recently modified file. - Naming Conventions: Derives filenames from Linear ticket IDs (e.g., bik-12-feature-plan.md) or sprint numbers, falling back to asking the user. - Version-Controlled Persistence: Writes the plan to docs/product/plans/ and commits it with a descriptive message, with overwrite confirmation for existing files. - Use Case: After exiting plan mode on a feature tied to ticket BIK-12, invoke this Skill to save the plan as docs/product/plans/bik-12-feature-plan.md and commit it automatically. ## Quick Start Save the current plan from plan mode to the project docs folder and commit it.

Frequently Asked Questions about persist-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a Claude Code plan permanently?▼

Invoke the persist-plan skill after exiting plan mode or by saying "save the plan". It copies the plan from .claude/plans/ into docs/product/plans/ and commits it to version control.

Where does Claude Code store plan mode files?▼

Claude Code stores plan mode files in the ephemeral .claude/plans/ directory, which is internal to sessions. To keep plans permanently, copy them into a version-controlled folder like docs/product/plans/.

How is the persisted plan file named?▼

The filename follows a priority order: a Linear ticket ID with a slug (e.g., bik-12-feature-plan.md), then a sprint number (sprint-<N>-plan.md), otherwise the user is asked to provide a name.

What happens if the plan file already exists in docs?▼

The skill asks for confirmation before overwriting an existing file in docs/product/plans/, preventing accidental loss of previously saved plans.

When should I not use plan persistence?▼

Skip persistence for throwaway exploration plans that were never approved or acted on. Persisting every draft clutters docs/product/plans/ with obsolete design documents.

Related Skills

Explore More Software Engineering Skills→
SKNETWORKS-FAMILY-AICAMPSKNETWORKS-FAMILY-AICAMP

implement

Apply plan file changes to source files with type checking after each edit.

Official
Intermediate
OmniNode-aiOmniNode-ai
3

executing-plans

Converts implementation plans into Linear tickets and routes them by project scope.

Official
Advanced
vankichivankichi

notion-ticket-plan

Generate implementation plans from Notion, Linear, and GitHub Issue tickets.

Community
Advanced
sanity-iosanity-io
952

grill-with-docs

Stress-tests plans against domain glossaries and records decisions in CONTEXT.md and ADRs.

Official
Intermediate