Skip the Plan — Just Do It

To bypass planning and execute tasks directly, invoke the `/no-plan` command to override default workflow mandates, skipping brainstorming, plan writing, and design proposals while retaining safety checks.

Yes, you can override the default execution workflow by explicitly invoking `/no-plan`, which bypasses brainstorming, testing, debugging, code review, and branch cleanup phases for direct task execution.

Bypassing the planning workflow still performs safety checks, ensuring verification before completion, respecting domain skills as tools, and confirming risks for destructive actions to maintain a safety floor.

The best way to reduce time spent on unnecessary documentation is using the `/no-plan` command to bypass plan writing and design proposals, enabling direct task execution with built-in safety measures.

You should not use a planning bypass for tasks involving destructive actions without risk confirmation, as the skill enforces safety floors, verification before completion, and respects domain skills as tools.