plan

You can generate a structured markdown implementation plan before coding by defining feature goals, context, file changes, testing steps, and risks. This planning workflow organizes software development tasks and saves the roadmap as a workspace document without modifying project code.

The best way to organize project planning for repository changes is to generate a markdown plan that explicitly lists goals, tradeoffs, open questions, and validation steps. This ensures all engineering assumptions and risks are documented before execution begins.

No, you cannot execute code or modify project files while generating a development plan. The planning workflow is restricted to producing markdown documentation and organizing tasks, ensuring a clear separation between planning and implementation actions.

To prepare a testing and validation plan for a new software feature, document the expected validation steps and testing preparation within a markdown implementation plan. This captures the necessary engineering workflow organization before any code execution begins.

Yes, implementation planning works for complex engineering workflows by structuring risks, tradeoffs, and open questions into defined markdown sections. This approach clarifies assumptions and organizes development preparation for tasks with multiple variables.

You should not use markdown for project planning if your software development task requires immediate code execution or automated implementation actions. This planning approach is restricted to documenting goals, assumptions, and risks without running execution steps.