plan

To generate a markdown plan without modifying the codebase, the tool inspects the active workspace context and writes a timestamped file to .rawclaw/plans/. It relies on read-only inspection, ensuring the project files remain untouched and unexecuted.

Formalizing task scoping and feature design intent is best achieved by generating a concrete, shareable markdown plan. This approach produces a deterministic document that enables clearer traceability without executing or mutating project code.

Yes, you can use this planning approach for pre-implementation research tasks. The process inspects current context to produce an actionable markdown plan, making it applicable for research, project scoping, and design reviews before any code execution.

Generated markdown plans are stored under the .rawclaw/plans/ directory in the active workspace. The plan is saved with a timestamped filename to ensure chronological organization and easy retrieval of planning documents.

Workspace planning does not execute code or mutate existing project files. The process is strictly limited to read-only workspace inspection to gather context needed to write the final markdown plan.