plan-mode

Creates a verified, 4-phase implementation plan requiring explicit user approval before coding begins.

3|Updated Apr 21, 2024
One-click install
npx skills add https://github.com/gabrielfruet/.dotfiles --skill plan-mode-gabrielfruet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-mode
Source: https://github.com/gabrielfruet/.dotfiles/tree/main/pi/agent/skills/plan-mode
Command: npx skills add https://github.com/gabrielfruet/.dotfiles --skill plan-mode-gabrielfruet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the common pitfall of rushing into implementation without proper planning, which often leads to missed requirements, broken existing functionality, and wasted development time.

Core Features & Use Cases

  • Structured 4-Phase Planning Workflow: Guides users through task understanding, critical thinking, verified action plan building, and approval presentation before any changes are made.
  • Read-Only Inspection Mandate: Requires verification of all external APIs, dependencies, and change surfaces via read-only checks to avoid building plans on unverified assumptions.
  • Explicit Approval Gate: Blocks all implementation actions until the user provides clear, explicit confirmation, preventing unintended system modifications.
  • Use Case: Ideal for complex code refactors, feature additions, or configuration changes where missing a dependency or edge case can cause significant downstream issues.

Quick Start

Invoke the plan-mode skill when you want to create a detailed, verified implementation plan for your next coding task before writing any code.

Frequently Asked Questions about plan-mode

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

FAQPage Schema
How do I enforce pre-coding planning to prevent costly rework in software engineering?

Pre-coding planning is enforced by applying a gated workflow that mandates read-only codebase inspection, explicit user approval, and minimal-change principles before implementation begins. This structured process eliminates unverified assumptions and prevents downstream issues.

How do I create a verified implementation plan before writing code?

To create a verified implementation plan, follow a structured 4-phase workflow: task understanding, critical thinking, verified action plan building, and approval presentation. This process requires read-only inspection of external APIs and dependencies to avoid building plans on unverified assumptions.

What is the best way to scope code changes and identify edge cases before implementation?

Scoping code changes and identifying edge cases is best achieved through a gated planning workflow that requires read-only inspection of relevant codebases and documentation. This ensures all change surfaces are verified before any execution occurs.

Does plan-mode support approval workflows for complex code refactors and configuration changes?

Plan-mode supports complex code refactors and configuration changes by utilizing an explicit approval gate. This gate blocks all implementation actions until the user provides clear confirmation, preventing unintended system modifications during critical system updates.

When should I use a gated planning workflow for software development tasks?

A gated planning workflow should be used for software development tasks involving complex code refactors, feature additions, or configuration changes where missing a dependency or edge case can cause significant downstream issues and costly rework.