Skill

spawn-planning-repo

Create a sibling planning repo for the current project, seed it with planning context moved out of the main repo, and push to GitHub. Use when the user says "create a planning repo alongside this", "spin off planning", or "split planning into its own repo".

npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-hopper

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create a dedicated planning repository that lives alongside the current code repo. Planning material (roadmaps, notes, specs, brainstorms) is moved out of the main repo into the new one, keeping the code repo lean.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitApr 29, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Spawn Planning Repo

Steps

Identify the current repo root and parent directory:

root=$(git rev-parse --show-toplevel)
name=$(basename "$root")
parent=$(dirname "$root")

Propose a planning repo name (default: <name>-planning) and confirm with the user.

Survey the current repo for planning-flavored files/dirs — e.g. planning/, docs/planning, ROADMAP.md, NOTES.md, TODO.md, ideas/, brainstorm markdown. Present the list to the user and confirm what should move. Do not guess silently.

Create the new repo directory and initialize it:

mkdir "$parent/<planning-name>"
cd "$parent/<planning-name>"
git init -b main

Seed it with:

A README.md naming the sibling code repo and explaining this is its planning companion.
A CLAUDE.md briefly stating: this repo holds planning/spec/roadmap context for <name>, which lives at <path> / <github url>.
The planning files moved (via git mv in the source repo, then copied over — or mv if they're untracked) from the main repo.

In the main repo: remove the moved files with git rm (or rm if untracked), commit with a message like chore: move planning into sibling <planning-name> repo. Do NOT push the main repo unless the user asks.

In the new planning repo: git add -A, initial commit, then create the GitHub repo and push:

gh repo create danielrosehill/<planning-name> --private --source . --remote origin --push

Report: new repo path, GitHub URL, list of files moved, and the pending (uncommitted-pushed) state of the main repo.

Notes

Always confirm the file list before moving anything — planning material is subjective.

Use git mv then physically move when possible so history is preserved in the source commit that removes them.

The new repo is private by default; ask if the user wants public.