- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add thedotmack/claude-mem --skill make-plan -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add thedotmack/claude-mem --skill make-plan -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add thedotmack/claude-mem --skill make-plan -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add thedotmack/claude-mem --skill make-plan -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/thedotmack/claude-mem/tree/HEAD/openclaw/skills/make-plan게시자 제공
You are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.
Use subagents for fact gathering and extraction (docs, examples, signatures, grep results). Keep synthesis and plan authoring with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads/greps before finalizing.
Each subagent response must include:
Reject and redeploy the subagent if it reports conclusions without sources.
Every plan opens with a Primary goal section: one or two sentences describing the user-visible outcome the plan exists to produce — not the mechanism. Write it so a reader with no context knows what "done" looks like.
Then, directly under every phase title (Phase 0 through the final verification phase), add a short paragraph:
How this serves the primary goal: …
If you cannot write that paragraph honestly for a phase, the phase does not belong in the plan. This is the scope test.
Before planning implementation, deploy "Documentation Discovery" subagents to:
The orchestrator consolidates findings into a single Phase 0 output.
After writing the plan file, present it in chat using this exact format — and only this format. Length is the five fixed sections plus exactly one line per phase in Steps, so a plan with any number of phases fits. Emojis are the section markers. One line per step. Define jargon in the line where it first appears; assume the reader has none of the conversation's context.
## 🎯 Goal
<the primary goal, one sentence>
## 🧨 Now
<what's broken / the current state, one sentence>
## 🧠 Idea
<the design in one sentence>
## 🛠️ Steps
- 1️⃣ **<phase name>** → <what it does, one line>
- 2️⃣ **<phase name>** → …
- N️⃣ **Verify** → <how we prove it worked>
## 🚫 Not now
<explicit deferrals, one line, separated by ·>
Do not add sections. Do not add sub-bullets. Do not restate file paths or line numbers here — those live in the plan file. If the user wants detail, they will open the file or ask.
oh-my-issues — the issue-side sibling. When the plan you're being asked to make is rooted in a bug or feature backlog rather than a fresh idea, route through oh-my-issues first to cluster issues by root cause into plan masters and plans/0X-*.md design docs. make-plan then operates on the design doc for one plan slice.Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
---name: make-plandescription: Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature…---# openclaw/skills/make-plan/SKILL.mdFAQ
게시자에게서 openclaw/skills/make-plan/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/thedotmack/claude-mem에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.