# Outperform 99% Of Vibe Coders With This Planning Method
Table of Contents
These notes are based on the YouTube video by Sean Kochel
Planning Method for Vibe Coders
The planning process for vibe coders, as outlined by Sean Kochel, involves a structured approach that can help minimize the chances of getting lost in the development process and ensures a robust plan. While Kochel has discussed various planning frameworks, including four-step and eight-step systems in other recent videos, the three-stage process described here is one version of his evolving methodology.
Architecting Stage
The architecting stage involves defining the features and technical requirements of the project. This includes:
- Defining the MVP flow
- Identifying the features and their core requirements
- Determining the technical requirements for each feature
- Defining the main components of the app and their relationships, which may involve creating a system diagram or similar representation, although this is not always a formal requirement.
To achieve this, a prompt is used with the following structure:
# Goal* Define the project's goal and scope# Format* Specify the format for the response# Context* Provide context for the project, including audience notes and MVP flowFor example:
# GoalYou are a senior software engineer. We are brainstorming the overall structure of my new project.# FormatPlease respond in markdown format.# ContextWe are building a Michelin star recipe guide for home cooks.Designing Stage
The designing stage involves creating a detailed design brief for the project. This includes:
- Defining the general aesthetics of the app
- Identifying the features and their requirements
- Creating a design brief for each feature
To achieve this, a prompt is used with the following structure:
# Goal* Define the project's goal and scope# Format* Specify the format for the response# Context* Provide context for the project, including features and requirementsFor example:
# GoalYou are an industry veteran SaaS product designer. Your goal is to take the context below and turn it into a design brief.# FormatPlease respond in markdown format.# ContextWe are building a Michelin star recipe guide for home cooks. The features include authentication, camera integration, and recipe generation.Task Planning Stage
The task planning stage involves creating a detailed technical plan for the project. This includes:
- Defining the file system structure
- Identifying the features and their requirements
- Creating a technical plan for each feature
To achieve this, a prompt is used with the following structure:
# Goal* Define the project's goal and scope# Format* Specify the format for the response# Context* Provide context for the project, including features and requirementsFor example:
# GoalYou are a veteran software engineer responsible for writing detailed step-by-step technical specifications for each feature.# FormatPlease respond in markdown format.# ContextWe are building a Michelin star recipe guide for home cooks. The features include authentication, camera integration, and recipe generation.Summary
The planning method for vibe coders, as described by Sean Kochel, involves a structured three-stage process: architecting, designing, and task planning. By using prompts with a specific structure, developers can create a robust plan for their project, minimizing the chances of getting lost in the development process. The output of this process can be used to generate tasks and inform further planning, potentially integrating with other tools and systems. While the specific application and evolution of this methodology may vary, the core principles of robust planning and structured approach remain key to successful project development.
