formalize-plan

Formalize project plans into structured documents before implementation.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/fredericpoitevin/.cursor --skill formalize-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formalize-plan
Source: https://github.com/fredericpoitevin/.cursor/tree/main/skills/formalize-plan
Command: npx skills add https://github.com/fredericpoitevin/.cursor --skill formalize-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalize the plan before proceeding. Forces Claude into plan mode to explore the codebase, design an approach, and get approval before implementation. Triggers on: formalize plan, structured plan, plan before proceeding, formal plan, write up your plan.

Core Features & Use Cases

  • Initiates plan-mode to outline objectives and scope before diving into work.
  • Generates a concise, review-ready plan document to share with stakeholders.
  • Useful in software projects to ensure alignment between design and implementation.

Quick Start

Outline a plan and obtain explicit approval before starting implementation.

Frequently Asked Questions about formalize-plan

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

FAQPage Schema
How do I formalize a project plan before starting code implementation?

To formalize a project plan before implementation, trigger plan-mode to explore the codebase, design an approach, and capture a structured plan document requiring explicit approval before proceeding with development.

What is plan-mode and how does it help with software design approval workflows?

Plan-mode is a pre-implementation state that forces codebase exploration and design discussion to produce a structured, review-ready plan document. It ensures stakeholders provide explicit approval before any implementation work begins.

How do I write a structured plan for codebase exploration and design discussions?

To write a structured plan for codebase exploration, outline project objectives and scope, design the technical approach, and capture everything in a concise document to share with stakeholders for alignment and approval.

Can I enforce pre-implementation validation and approval before modifying a codebase?

Yes, pre-implementation validation is enforced by triggering plan-mode to formalize the project plan. This ensures a structured plan is reviewed and explicitly approved before any codebase changes proceed.

When do I need a formal plan before proceeding with software development?

You need a formal plan before proceeding when a software project requires alignment between design and implementation. It ensures objectives, scope, and approach are reviewed and approved before development starts.

Does formalize-plan work without external dependencies or components?

Yes, formalize-plan operates with no external dependencies or components. It functions as a standalone workflow mechanism to trigger plan-mode, capture structured plans, and enforce approval before implementation.