no-plan-mode

Enforce direct execution by disallowing plan-mode prompts in autonomous agent runs.

16|9|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/en-dash-consulting/n-dx --skill no-plan-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-plan-mode
Source: https://github.com/en-dash-consulting/n-dx/tree/main/.agents/skills/no-plan-mode
Command: npx skills add https://github.com/en-dash-consulting/n-dx --skill no-plan-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-mode stalls disrupt autonomous hench agent runs by delaying execution and breaking the loop.

Core Features & Use Cases

  • Enforces the No Plan Mode rule during execution tasks to prevent stalls.
  • Guides decisions and documentation by referencing architecture notes (CLAUDE.md, PACKAGE_GUIDELINES.md) and logging decisions with append_log.
  • Applies across ndx work automation and continuous agent loops to maintain momentum.

Quick Start

Enforce the no-plan-mode rule at the start of each execution task to ensure direct implementation without plan-mode prompts.

Frequently Asked Questions about no-plan-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent plan-mode stalls in autonomous agent runs?

Preventing plan-mode stalls in autonomous agent runs requires enforcing direct execution by disallowing EnterPlanMode and ExitPlanMode operations. This skill maintains continuous task flow by directing decisions via append_log and referencing CLAUDE.md architecture guidelines.

Why does my hench agent loop stall during execution tasks?

Hench agent loops stall during execution tasks when plan-mode prompts interrupt autonomous workflows. Disabling EnterPlanMode and ExitPlanMode commands enforces direct implementation, preventing delays and maintaining continuous ndx work loop momentum.

How do I enforce no-plan-mode rules at the start of execution tasks?

Enforcing no-plan-mode rules at the start of execution tasks involves blocking plan-mode entry and exit commands. The skill directs autonomous decisions through append_log entries and guides implementation actions using CLAUDE.md and PACKAGE_GUIDELINES.md references.

Can I use append_log to maintain autonomous agent workflow momentum?

Using append_log to maintain autonomous agent workflow momentum ensures decisions are documented without triggering plan-mode prompts. This approach keeps hench agent runs flowing by replacing interactive planning steps with direct execution and continuous logging.

What's the best way to keep continuous agent loops from breaking during ndx work?

Keeping continuous agent loops from breaking during ndx work requires disallowing plan-mode operations entirely. By referencing CLAUDE.md and PACKAGE_GUIDELINES.md for guidance and logging decisions with append_log, autonomous task flows maintain steady execution momentum.

When should I not use no-plan-mode for autonomous agent workflows?

No-plan-mode should not be used for autonomous agent workflows requiring explicit planning approval or complex architectural review before implementation. It is designed strictly for execution-oriented tasks where direct action and continuous logging via append_log are operationally required.