codex-plan-mode

Produces decision-complete implementation plans through a three-phase ground-plan-handoff workflow.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/maopujie10-sys/Bailongma --skill codex-plan-mode-maopujie10-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-plan-mode
Source: https://github.com/maopujie10-sys/Bailongma/tree/main/skills/hermes-skills/autonomous-ai-agents/codex-plan-mode
Command: npx skills add https://github.com/maopujie10-sys/Bailongma --skill codex-plan-mode-maopujie10-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents premature code changes by enforcing a structured planning discipline: explore the codebase first, produce a complete plan, and only execute after explicit approval. ## Core Features & Use Cases - Ground Phase: Inspects files, directories, and existing code to resolve unknowns through exploration instead of asking the user. - Plan Phase: Generates a decision-complete plan specifying which files to change, what changes to make, how to verify, and the rollback path. - Hand Off Phase: Presents the plan for approval and blocks all mutations until the user confirms. - Use Case: Before refactoring a module, trigger plan mode so the agent reads the relevant code, drafts a step-by-step change plan with verification steps, and waits for your sign-off before editing anything. ## Quick Start Ask the agent to make a plan for your intended change, for example by saying plan this refactor before writing any code.

Frequently Asked Questions about codex-plan-mode

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

FAQPage Schema
How do I make an AI agent plan before writing code?

Trigger plan mode with phrases like make a plan or plan this. The agent then explores the codebase read-only, drafts a complete implementation plan, and waits for your approval before editing any files.

What should a good implementation plan include?

A decision-complete plan specifies which files change, what the changes are, how to verify the result, and a rollback path. Another engineer should be able to execute it without making any further decisions.

Can the agent edit files during plan mode?

No. Plan mode permits only non-mutating exploration such as reading, searching, listing, and dry-runs. File editing and code changes are blocked until the plan is approved in the hand-off phase.

When should I use plan mode instead of direct execution?

Use it for multi-file refactors, architecture changes, or unfamiliar codebases where wrong edits are costly. Skip it for trivial single-line fixes where planning overhead exceeds the risk.