save-plan

Save Claude Code /plan output as a docs/work plan.md initiative file.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/bpawlakj/ai-devkit --skill save-plan-bpawlakj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-plan
Source: https://github.com/bpawlakj/ai-devkit/tree/main/claude/skills/save-plan
Command: npx skills add https://github.com/bpawlakj/ai-devkit --skill save-plan-bpawlakj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code’s /plan mode shows an approved plan but doesn’t automatically store it in your docs/work conventions, which forces you to manually create initiative folders and plan.md files.

Core Features & Use Cases

  • Automatically saves plans to docs/work: Writes the most recent approved plan into docs/work/NNN-<slug>/plan.md so downstream tooling like /atomize can consume it.
  • Smart plan source detection: Chooses the plan from an inline file argument, Claude’s plan store (~/.claude/plans/), recent conversation context, or prompts you to paste when nothing is detected.
  • Roadmap-shaped plan handling: Detects top-down roadmap structures and (after user confirmation) saves them to docs/roadmap.md instead of creating an initiative change-set.

Quick Start

Ask Claude to run the plan first and then invoke /save-plan with no arguments to store the newest approved plan into a numbered docs/work initiative folder.

Frequently Asked Questions about save-plan

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

FAQPage Schema
How do I save Claude Code plan output to a markdown file?

You can save Claude Code plan output by invoking the skill to write the newest approved plan into a numbered docs/work/NNN-<slug>/plan.md file, sourcing content from an inline file, conversation context, or the Claude plan store.

Can I automatically generate a kebab-case slug for initiative planning folders?

Yes, the skill computes a kebab-case slug and a sequential NNN folder number automatically when persisting your approved plan into the docs/work directory for later atomization.

What happens when I save a roadmap-shaped plan instead of a standard task plan?

When a top-down roadmap structure is detected, the skill requests explicit user confirmation to route the content directly to docs/roadmap.md instead of creating a standard numbered initiative change-set folder.

How do I handle file collisions when writing documentation workflow files?

The skill performs collision-safe writes by offering overwrite or versioned options when the target plan.md file already exists in the computed initiative folder, ensuring no previous work is lost.

Does the save-plan skill require a dedicated workspace setup before use?

Yes, the skill requires workspace checks for an existing docs/work directory before saving, ensuring your documentation workflow environment is correctly configured for initiative planning and downstream atomization.