plan

To create an implementation plan without modifying project files, use a plan-only workflow that generates structured markdown documents capturing goals, approaches, and validation steps. This prevents code edits, commits, and other mutating actions while preparing your architecture.

Plan mode in software engineering workflows is a process that separates task analysis from execution, generating detailed markdown implementation roadmaps. It captures context, file paths, tests, risks, and open questions before any actual development work begins.

To structure a markdown implementation plan, organize sections for goals, assumptions, file change paths, task breakdowns, validation strategies, risks, and open questions. This provides a clear roadmap capturing context and approaches before development starts.

Yes, you can use planning workflows to prepare architecture and task breakdowns before coding. These workflows generate actionable planning documents that outline validation steps and approaches, ensuring all open questions are addressed prior to any file modifications.

Separating code analysis from execution prevents unintended modifications by enforcing a structured planning phase. It allows developers to validate assumptions, identify risks, and outline file paths first, resulting in safer, more organized implementation roadmaps.