skills.rest
herren-official
herren-officialOFFICIAL
Explore all skills by this author →
WebsiteGitHub

b2b-backend-plan-doc

Save the current implementation plan to .claude/plan/{branch}-plan.md.

Updated Aug 23, 2026
Search Tags:#git#planning#documentation#markdown#branching#plan
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2b-backend-plan-doc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: b2b-backend-plan-doc
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2b-backend/plan-doc
Command: npx skills add https://github.com/herren-official/product-agents --skill b2b-backend-plan-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Current conversations and decisions about implementation plans are ephemeral. This Skill saves the plan to a stable Markdown document, enabling versioning and easy retrieval.

Core Features & Use Cases

  • Persist plan to .claude/plan/{branch}-plan.md inside the repository root.
  • Normalize branch names by replacing / with - when forming the file path.
  • Create the .claude/plan directory if it does not exist.
  • Prompt before overwriting an existing plan file to avoid data loss.
  • Capture the plan content from the conversation and store it in a structured Markdown document for later reference.

Quick Start

Invoke the plan capture to save the current implementation plan to the repository at .claude/plan/{branch}-plan.md, creating directories as needed and prompting before overwriting.

Frequently Asked Questions about b2b-backend-plan-doc

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

FAQPage Schema
How do I save an implementation plan to a Markdown file in my Git repository?▼

To save an implementation plan, the conversation context is captured and written to a Markdown file named {branch}-plan.md inside the .claude/plan directory at your repository root, ensuring the plan is versioned and retrievable across sessions.

What is the best way to track development plans across different Git branches?▼

Tracking development plans across Git branches is achieved by saving the plan as a Markdown file under .claude/plan, using the current branch name as the file name to keep plans isolated and organized per branch.

Does the plan capture tool sanitize Git branch names with slashes for file storage?▼

Yes, Git branch names containing slashes are sanitized by replacing the slash character with a hyphen, ensuring the generated Markdown file path remains valid across different operating systems.

Can I automatically overwrite an existing plan Markdown file without losing data?▼

You cannot automatically overwrite existing plan files, because the tool prompts you before overwriting any pre-existing Markdown document to prevent accidental data loss during the plan capture process.

How do I create the .claude/plan directory if it does not exist in my project?▼

The .claude/plan directory is created automatically if it is missing, by first reading the repository root via Git and then initializing the required folder structure before saving the Markdown plan document.

Related Skills

Explore More Software Engineering Skills→
shellicarshellicar

detect-convention

Detect the active Git repository convention and default branch as JSON.

Community
Intermediate
CherrySalmonCherrySalmon
1

branch-plan

Generate a structured Markdown plan file for a Git branch.

Official
Intermediate
ogghstogghst

pm

Update sprint and product backlogs and track iteration progress in Backcast EVS.

Community
Basic
uutauuta
1

plan-on-md

Save planning outputs as Markdown files under project and branch paths.

Community
Basic