branch-plan

Generate a PLAN.<sanitized-name>.md branch plan and update CLAUDE.local.md references.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/soumyaray/ray-ai-skills --skill branch-plan-soumyaray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-plan
Source: https://github.com/soumyaray/ray-ai-skills/tree/main/ray-branch-plan
Command: npx skills add https://github.com/soumyaray/ray-ai-skills --skill branch-plan-soumyaray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a standardized branch plan to align feature work with branching strategy, reducing ambiguity in development.

Core Features & Use Cases

  • Creates a PLAN.<sanitized-name>.md branch plan file based on a consistent template.
  • Updates CLAUDE.local.md references to point to the current plan.
  • Provides traceability of scope, decisions, and tasks across branches.

Quick Start

Create a plan for the current or new branch using the standard template and update CLAUDE.local accordingly.

Frequently Asked Questions about branch-plan

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

FAQPage Schema
How do I create a structured plan for a git branch?

A branch plan document provides traceability of scope, decisions, and tasks across your repository. It aligns feature work with your branching strategy to reduce development ambiguity by creating a standardized reference file.

How do I document project decisions and scope for a specific branch?

You document project decisions and scope by generating a standardized markdown plan file for the branch. This creates a living document that tracks decisions, scope, and tasks for traceability throughout the development lifecycle.

What's the best way to track tasks and decisions across multiple git branches?

Tracking tasks across branches is managed by creating a sanitized PLAN.<name>.md file for each branch. This provides consistent traceability of decisions and tasks, ensuring the output is ready for activation by the Claude Code workflow.

Do I need any specific dependencies to generate a branch plan document?

No specific dependencies are required to generate a branch plan document. The tool operates independently to create the standardized markdown file and update local reference files for your project management workflow.

How does the branch plan integrate with local development workflow files?

The branch plan integrates by updating CLAUDE.local.md references to point to the current plan. This ensures the living plan document remains accessible and ready for activation by your development workflow.