How do I install the Portable Adaptive Planning skill?

Run npx skillmds@latest add ezra144israel/portable-adaptive-planning in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Portable Adaptive Planning safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Portable Adaptive Planning?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Portable Adaptive Planning free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Portable Adaptive Planning?

Ezra144israel (@ezra144israel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Portable Adaptive Planning by ezra144israel

Name: Portable Adaptive Planning
Author: Ezra144israel

Portable Adaptive Planning

Use for planning, roadmaps, design, architecture, sequencing, or before consequential work when no current FINAL plan plus GO covers it. Fire before changes to data or schemas, credentials or auth, production or releases, repository or source-home boundaries, irreversible work, or materially costly mistakes. Re-enter when that scope appears mid-task or when restoring prior plan state. Skip factual answers, trivial reversible one-step work, and authorized Builder or Reviewer execution under a current FINAL blueprint plus GO unless a reopen condition fires.

Ezra144israel Updated Sep 17, 2026

File contents

Portable adaptive planning

Keep a compact Plan Capsule, not the planning transcript, for material work.

Plan Capsule

PLAN <id>: DRAFT | CHALLENGE-READY | FINAL
AS OF <latest operator instruction accounted for>
DEPTH: LIGHT | STANDARD | DEEP

ASKED
<operator's words that define the outcome>

GOAL
<accepted restatement>

DELIVERABLE
<what will exist>

PLAN
1. <step with a checkable completion condition>
2. <step with a checkable completion condition>

DONE
<smallest observable acceptance condition>

Add SOURCE HOME, BOUNDARIES, or OPEN only when they carry load-bearing information.

Copy ASKED from the operator. A continuation (proceed, yes) keeps ASKED and advances AS OF. A changed outcome replaces ASKED, updates the plan, and is read back.

Readback

Show the full current capsule when a load-bearing part of the plan changes, before challenge, on restore, and before final closeout. Append only applicable temporary sections:

CHANGED
- <changed plan state>

ADDED
- <new agent-added scope or requirement>

DROPPED
- <operator-requested item that disappeared or changed meaning>

Do not persist those temporary sections after the operator has seen them.

Depth and challenge

LIGHT: bounded, familiar, reversible work. No challenge by default.
STANDARD: several meaningful decisions or moderate uncertainty. Challenge when a load-bearing question remains, the operator asks, or error cost warrants it.
DEEP: architecture, broad blast radius, authority, safety, recovery, migration, expensive error, or major uncertainty. Challenge by default unless the operator skips it.

Raise depth when stakes rise. Read back every depth change.

Restore

Before continuing restored planning or execution:

Reproduce the latest complete capsule.
Verify that AS OF includes the current operator instruction.
Show the capsule readback before any mutation or execution.

If the capsule is complete, exact, and current, continue after the readback. Do not ask for another confirmation only because a session boundary occurred.

If state is incomplete, stale, conflicting, uncertain, or cannot reproduce the complete capsule exactly, mark RESTORED: UNVERIFIED, show the reconstruction, and hold for operator confirmation. A FINAL blueprint plus GO is not an exact restore when the complete capsule cannot be reproduced.

Final and GO

Ask: Is this the plan?

When the operator settles the plan, respond exactly:

Plan is FINAL. Execution waits for your GO.

FINAL never authorizes execution. Execute only after a later, separate, explicit GO.

Downstream blueprint

When a FINAL plan is handed to a Builder or Reviewer, read references/blueprint.md. Reopen planning before changing the objective, deliverable, source home, load-bearing boundary, acceptance condition, or plan currency.

---name: portable-adaptive-planningdescription: Use for planning, roadmaps, design, architecture, sequencing, or before consequential work when no current FINAL plan plus GO covers it. Fire before changes to data or schemas, credentials or auth, production or releases, repository or source-home boundaries, irreversible work, or materially costly mistakes. Re-enter when that scope appears mid-task or when restoring prior plan state. Skip factual answers, trivial reversible one-step work, and authorized Builder or Reviewer execution under a current FINAL blueprint plus GO unless a reopen condition fires.---# Portable adaptive planningKeep a compact Plan Capsule, not the planning transcript, for material work.## Plan Capsule```textPLAN <id>: DRAFT | CHALLENGE-READY | FINALAS OF <latest operator instruction accounted for>DEPTH: LIGHT | STANDARD | DEEPASKED<operator's words that define the outcome>GOAL<accepted restatement>DELIVERABLE<what will exist>PLAN1. <step with a checkable completion condition>2. <step with a checkable completion condition>DONE<smallest observable acceptance condition>```Add `SOURCE HOME`, `BOUNDARIES`, or `OPEN` only when they carry load-bearing information.Copy `ASKED` from the operator. A continuation (`proceed`, `yes`) keeps `ASKED` and advances `AS OF`. A changed outcome replaces `ASKED`, updates the plan, and is read back.## ReadbackShow the full current capsule when a load-bearing part of the plan changes, before challenge, on restore, and before final closeout. Append only applicable temporary sections:```textCHANGED- <changed plan state>ADDED- <new agent-added scope or requirement>DROPPED- <operator-requested item that disappeared or changed meaning>```Do not persist those temporary sections after the operator has seen them.## Depth and challenge- `LIGHT`: bounded, familiar, reversible work. No challenge by default.- `STANDARD`: several meaningful decisions or moderate uncertainty. Challenge when a load-bearing question remains, the operator asks, or error cost warrants it.- `DEEP`: architecture, broad blast radius, authority, safety, recovery, migration, expensive error, or major uncertainty. Challenge by default unless the operator skips it.Raise depth when stakes rise. Read back every depth change.## RestoreBefore continuing restored planning or execution:1. Reproduce the latest complete capsule.2. Verify that `AS OF` includes the current operator instruction.3. Show the capsule readback before any mutation or execution.If the capsule is complete, exact, and current, continue after the readback. Do not ask for another confirmation only because a session boundary occurred.If state is incomplete, stale, conflicting, uncertain, or cannot reproduce the complete capsule exactly, mark `RESTORED: UNVERIFIED`, show the reconstruction, and hold for operator confirmation. A FINAL blueprint plus GO is not an exact restore when the complete capsule cannot be reproduced.## Final and GOAsk: `Is this the plan?`When the operator settles the plan, respond exactly:`Plan is FINAL. Execution waits for your GO.``FINAL` never authorizes execution. Execute only after a later, separate, explicit `GO`.## Downstream blueprintWhen a FINAL plan is handed to a Builder or Reviewer, read `references/blueprint.md`. Reopen planning before changing the objective, deliverable, source home, load-bearing boundary, acceptance condition, or plan currency.

Frequently asked questions