plan-mode

Convert a user's goal into a structured execution plan with success criteria and risk assessments.

12.6k|1.5k|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/nearai/ironclaw --skill plan-mode-nearai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-mode
Source: https://github.com/nearai/ironclaw/tree/main/skills/plan-mode
Command: npx skills add https://github.com/nearai/ironclaw --skill plan-mode-nearai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you transform an ambiguous goal into a structured execution plan with clear steps, risks, and measurable success criteria.

Core Features & Use Cases

  • Plan creation and storage: Builds a plan from context and writes it to workspace memory as a MemoryDoc for later execution.
  • Checklist-driven progress tracking: Updates step status (draft, pending, in_progress, completed, failed) to keep execution transparent.
  • Controlled autonomous execution: Requires explicit approval to create and fire a mission, then executes step-by-step using the specified tools.

Quick Start

Create a plan for your task by writing: "[PLAN MODE] Create <your goal>".

Frequently Asked Questions about plan-mode

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

FAQPage Schema
How do I turn an ambiguous goal into a step-by-step execution plan with risk assessments?

To turn an ambiguous goal into a step-by-step execution plan, you write "[PLAN MODE] Create <your goal>". The system then structures your goal with ordered steps, success criteria, risk assessments, and a verifiable checklist.

How does checklist-driven progress tracking work for autonomous task execution?

Checklist-driven progress tracking works by updating each step's status—draft, pending, in_progress, completed, or failed—during execution. This maintains transparency and allows you to verify progress within the autonomous task workflow.

Do I need explicit approval to launch autonomous missions for plan execution?

Yes, explicit approval is required to launch autonomous missions. The system requires your confirmation to create and fire a mission, ensuring controlled, step-by-step execution of the structured plan using specified tools.

What is the best way to persist and update execution plans across task workflows?

The best way to persist and update execution plans is by storing them as MemoryDocs in workspace memory. You retrieve prior context via memory search and update the plan state during execution to maintain continuity across task workflows.

Can I order task execution steps by dependencies for mission orchestration?

Yes, you can order task execution steps by dependencies for mission orchestration. The system fits planning workflows where steps must be strictly ordered by their dependencies and subsequently tracked during execution.