plan

An implementation roadmap can be created without modifying the codebase by generating a markdown plan that outlines goals, assumptions, approach, likely file changes, and validation steps while strictly forbidding code execution or commits.

A plan-only workflow for software tasks produces a concrete, actionable markdown document detailing steps and risks without executing code, making mutating changes, or performing external actions on the repository.

To prepare tests and validation steps before writing code, generate a markdown implementation plan that explicitly includes test preparation and validation criteria while avoiding any actual code implementation or repository mutations.

Yes, you can generate a planning document that guarantees repository safety by following strict guardrails that forbid code implementation, external actions, and commit or push behavior during the planning process.

Markdown implementation plans are stored in the workspace by writing the plan to a timestamped file under the .zedclaw/plans/ directory, keeping the document tied to the active workspace.

Yes, the planning workflow supports coordinating approach and steps for code changes by producing a markdown document that details the implementation approach, likely file changes, and open questions without executing the changes.