plan

To write an implementation plan without modifying code, describe your software task and request a planning-only response. The output is a markdown file saved under .jarvis/plans/ containing goals, approach, files, tests, and risks instead of execution steps.

A workspace-safe software development plan is a markdown document that outlines implementation steps, assumptions, and risks without taking mutating actions or altering project code. It stays attached to the active workspace by saving output inside the .jarvis/plans/ directory.

To outline a bug fix or refactor before implementation, request a planning-only response for your task. The generated markdown plan captures the approach, files likely to change, validation steps, and open questions to guide the actual execution later.

Yes, this planning workflow supports coordination scenarios in software development by generating concrete markdown plans. It captures goals, assumptions, approach, risks, and open questions, providing clear execution guidance for teams without running mutating commands.

The best way to scope a feature request into actionable steps is to generate a markdown implementation plan. This process identifies goals, assumptions, approach, files to change, validation steps, and risks, saving the output safely under .jarvis/plans/.

Yes, you can use markdown planning to prepare a codebase refactor without running commands. This approach produces a plan-only markdown file that avoids code changes and mutating actions, outlining the refactor approach and validation steps instead.