Plan Mode
Productivityplan-modePlan Mode is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Guidelines for Plan Mode - focus on planning before implementation
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/design/plan-mode-monoppa-agentic-toolkit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plan-mode-d1b87d9f, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Plan Mode
Provides guidelines for Plan Mode workflow: planning and design before implementation.
Core Behaviour
Entry: Acknowledge with "Plan mode engaged." If this skill was loaded as part of a planning request, acknowledge after loading this skill.
- Clarifying questions: Identify ambiguities or missing requirements before drafting. Ask user open questions with recommended solutions. Ask questions early, don't assume.
- Present plan to user.
- Stay in Plan Mode until user says go (or proceed/continue).
- When the user confirmed with go, write the summary of the plan into a markdown file inside
artefacts/. Do not overwrite, always create a new summary file following this format:plan-summary-${MMDD hh:mm:ss}.
- Acknowledge with "Plan mode disengaged."
- Then begin implementation.
Restrictions:
- Create/update plans only
- No file edits except Markdown in
artefacts/ - Ask open questions to clarify requirements
- Use
todowritetool for task tracking - Research allowed: read files, search codebase, run diagnostic commands, answer questions
- No implementation: no edits, installs, or deployments
Exit: User says go
Changes summary
Write into a markdown file inside artefacts/ of a summary of the changes once done. Do not overwrite, always create a new summary file following this format: change-summary-${MMDD hh:mm:ss}
Open Questions
Ask clarifying questions for ambiguity or missing requirements.
In planning modes, if there are points for clarification that will significantly change the plan depending on its answer, ask them before creating plans.
For each question:
- Provide a clear recommended solution with reasoning
- Offer alternative approaches when applicable
- Include relevant considerations (technical, business, UX)
Example:
1. **Root page:** Should the root `/` page redirect to a default language (e.g., `/es`), or remain separate?
- a. Redirect to `/es` based on browser language detection _(recommended)_
- b. Show a language selection landing page
2. **Default role:** What should be the default user role upon registration?
- a. Basic user with limited permissions _(recommended)_
- b. Trial user with time-limited premium features
Example
### User:
/plan add dark mode
### Assistant:
**Plan mode engaged.**
[Reads files, creates todo list]
Before I draft the plan:
1. System detection? a) Yes (recommended) b) No
### User:
1a
### Assistant:
Here is the plan:
1. Add toggle to settings
2. Implement theme context
3. Update CSS variables
One detail:
2. Persist preference? a) localStorage (recommended) b) session-only
Ready when you say **go**.
### User:
2a, go
### Assistant:
**Plan mode disengaged.** [Begins implementation]