plan-only

Generate detailed implementation plans for user-approved coding tasks.

29|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/jbdamask/john-claude-skills --skill plan-only
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-only
Source: https://github.com/jbdamask/john-claude-skills/tree/main/plugins/beads-planner/skills/plan-only
Command: npx skills add https://github.com/jbdamask/john-claude-skills --skill plan-only

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows users to generate and approve detailed execution plans for coding tasks without the risk of immediate, automatic code modification, ensuring full control over the development process.

Core Features & Use Cases

  • Plan Generation: Creates comprehensive implementation plans based on user requests.
  • User Approval Workflow: Stops execution after the user approves the plan, preventing unintended changes.
  • Use Case: When you need to outline a complex refactoring task, get feedback on the proposed changes, and only proceed after explicit sign-off.

Quick Start

Use the plan-only skill to generate a plan for refactoring the user authentication module.

Frequently Asked Questions about plan-only

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

FAQPage Schema
How do I generate an implementation plan for code changes without executing them?

You can generate an implementation plan without execution by using a strict read-only workflow that writes a proposed plan file to a designated directory, requiring explicit user approval before any code modification occurs.

Can I stop automatic code modification during development workflows?

Yes, you can stop automatic code modification by enforcing an approval workflow that halts execution after presenting a detailed plan, ensuring full user control over the development process.

How does a user approval workflow function for task management?

A user approval workflow for task management functions by generating a comprehensive plan, pausing execution for review, and preventing unintended changes until explicit sign-off is provided.

What is the best way to outline a complex refactoring task for review?

The best way to outline a complex refactoring task is to generate a detailed plan file in read-only mode, presenting the proposed changes for feedback and securing explicit sign-off before implementation.

Does this planning approach require a read-only mode for all tools?

Yes, this planning approach requires a strict read-only mode for all tools except writing the plan file itself to a designated directory, ensuring proposed changes are safely isolated for review.

When do I need to enforce explicit oversight of proposed code changes?

You need to enforce explicit oversight of proposed code changes when outlining complex development workflows, ensuring that automatic code modification is prevented and implementation only proceeds after user approval.