Writing Plans Skill

When to Use

• After completing brainstorming for a feature
• When asked to create an implementation plan
• Before starting complex multi-step work
• When breaking down large tasks into manageable pieces

When NOT to Use

• Tasks estimated under 1 hour that can be done in a single uninterrupted flow — the plan overhead exceeds the benefit
• When requirements are still undefined or actively changing — wait until the scope is stable before creating a plan
• Micro-tasks like fixing a single bug or updating a config value — an inline comment is sufficient
• When an existing plan already covers the work — update the existing plan rather than creating a duplicate

Instructions

Step 1: Define Scope and Context