plan

Task planning documents are generated as concrete Markdown files saved under .clawg/plans/ with timestamped filenames. The tool reads relevant context and writes a reviewable plan without executing any side effects or mutating code.

Yes, you can scope software engineering tasks without executing code changes by generating a deterministic Markdown plan. It translates user intent into a reviewable document for approval, ensuring execution side effects remain off until validation is complete.

The best way to create a timestamped plan file for a CLAWG workflow is to request plan generation directly. It automatically writes a Markdown document under .clawg/plans/, capturing task scoping and validation steps for review.

Plan generation handles task validation by translating user intent into a structured document without side effects. It addresses planning sessions and validation steps within the CLAWG workflow, producing a Markdown file for review and approval before work begins.

No dependencies are required to write Markdown plan files. The tool operates independently within the active workspace to read relevant context and output timestamped documents under the .clawg/plans/ directory.

You should not use a plan generation tool when immediate code mutation or direct execution is required. It is designed strictly for reviewable planning and task scoping, intentionally keeping execution side effects off to ensure validation before work.