plan

To generate a markdown plan without modifying repository files, use a planning-only workflow that inspects context and saves a structured plan to a designated directory. This ensures the repository remains untouched while producing an auditable, timestamped markdown deliverable.

Yes, you can decompose complex project tasks into steps without executing workspace changes by operating in a read-only planning mode. This approach inspects the codebase context to produce task decomposition and risk assessment documents without mutating any files.

A read-only planning workflow for project scoping is a process that inspects repository context to generate structured goals, steps, and validation criteria. It produces a deterministic markdown file for reviews and handoffs without running commands or applying codebase changes.

Planning mode requires only read-only access to inspect the repository and context, not write access to run commands. It safely generates a timestamped markdown file into a specific plans directory and never mutates files in the active workspace.

You need a timestamped markdown plan for codebase handoffs when you require a safe, auditable record of goals, approach, and validation criteria. This deterministic deliverable ensures reviewers understand the project scope without risking unexecuted workspace mutations.