skills.rest
hyvanmielenpelit
hyvanmielenpelitOFFICIAL
Explore all skills by this author →
WebsiteGitHub

claude-plan-mode

Reconciles Claude Code plan mode with the shared plans repository workflow.

Updated Aug 25, 2026
Search Tags:#versioning#implementation planning#claude code#plan mode#exitplanmode#ai agent workflow#plans repository
One-click install
npx skills add https://github.com/hyvanmielenpelit/SharedAgentSkills --skill claude-plan-mode-hyvanmielenpelit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-plan-mode
Source: https://github.com/hyvanmielenpelit/SharedAgentSkills/tree/main/skills-claude/claude-plan-mode
Command: npx skills add https://github.com/hyvanmielenpelit/SharedAgentSkills --skill claude-plan-mode-hyvanmielenpelit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code's plan mode restricts editing to its own plan file in ~/.claude/plans/, while team conventions require plans to live in a shared plans repository. This Skill resolves that conflict by defining exactly when and how to copy, commit, and report the plan without violating plan mode restrictions. ## Core Features & Use Cases - Plan Reconciliation Workflow: Write the plan in the harness plan file, copy it to the plans repository before ExitPlanMode, and commit the planning round so the plan is shared at approval time. - Tier-Aware Behavior: Applies the copy-and-commit steps only to tier 1 (shared plans repository), with distinct handling for tier 2 (gitignored .plans/ fallback) and tier 3 (chat-only plans). - Versioning and Reporting Rules: Enforces in-place editing of the harness file versus _v<N> versioning in the plans repository, and requires reporting the plan as a clickable absolute link rather than a bare path. - Use Case: When planning a feature under Claude Code with plan mode active, follow this Skill to produce the plan, publish it to the shared plans repository, commit the round, and request approval via ExitPlanMode with a clickable link. ## Quick Start Read this Skill before planning under Claude Code plan mode so the finished plan is copied to the shared plans repository and committed before calling ExitPlanMode.

Frequently Asked Questions about claude-plan-mode

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

FAQPage Schema
How do I use Claude Code plan mode with a shared plans repository?▼

Write the plan to the harness plan file in ~/.claude/plans/, then copy it to the plans repository under <organization>/<repository>/YYYY-MM-DD/task_name/ before requesting approval. Commit the planning round, post a clickable absolute link, and call ExitPlanMode.

Why can I copy the plan file during plan mode if editing is restricted?▼

Plan mode restricts changes to the project itself, not the planning artifact. Copying the plan to its canonical location touches no source, build, or data files, so it is permitted while everything that changes the project still waits for approval.

What permissions does Claude Code need to write to the plans repository?▼

The plans root sits outside the project directory, so it requires permissions.additionalDirectories in the repository's .claude/settings.json (for example "../plans") or a one-off /add-dir. If neither is available, drop to tier 2 or 3 and say so.

When should I version a plan with _v<N> instead of editing in place?▼

Edit the harness plan file in ~/.claude/plans/ in place; versioning does not apply there. In the plans repository or a .plans/ fallback, never overwrite—increment the _v<N> suffix for each revision.

Do Explore and Plan research agents need user approval under plan mode?▼

No. Explore and Plan agents are read-only, run before the plan exists, and are already authorized by the harness. The plan's Subagent Use section governs only execution-phase agents that edit files after approval.

Related Skills

Explore More Software Engineering Skills→
arthur-debertarthur-debert

lex-multirepo

Clone sibling lex-fmt repositories into a shared /tmp/lex-fmt cache.

Community
Intermediate
dthompson-jtidthompson-jti

implement-feature

Execute approved implementation plans with validation checkpoints and task tracking.

Community
Advanced
zerobias-orgzerobias-org

name-phase-outputs

Enforce standard phase output file naming and path conventions across module lifecycles.

Official
Basic
autopus-aiautopus-ai
111

using-autopus

Installs and configures the Autopus-ADK harness across AI coding CLI platforms.

Official
Intermediate