create-plan
/create-plan
Writes an implementation plan file (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, file changes and runnable success criteria. Use when research is done and a reviewable plan is needed before code.
- Author
- yonatangross ↗
- Repository
- orchestkit ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/artifact.mjs
What it does and when to use it
Writes an implementation plan file (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, file changes and runnable success criteria. Use when research is done and a reviewable plan is needed before code.
Arguments
/create-plan <task> [slug]
Original author description
Writes an implementation plan file (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, file changes and runnable success criteria. Use when research is done and a reviewable plan is needed before code.
How it works
- Steps
- Rules
- Related Skills
SKILL.md preview
---
name: create-plan
description: "Writes an implementation plan file (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, file changes and runnable success criteria. Use when research is done and a reviewable plan is needed before code."
argument-hint: "<task> [slug]"
user-invocable: true
allowed-tools: "Bash Read Write Grep Glob"
compatibility: "Claude Code 2.1.277+. Node 22+."
metadata:
version: "1.0.0"
author: "OrchestKit"
complexity: "medium"
tags: "planning, artifacts, review, task-directory, workflow"
---
# create-plan
Turn what is known about a task into one plan file that a person can review line by line. The plan
lives in the task directory, and comments are written into the file, so the review history stays
with the plan and survives a new session.
The layout (path, file name, front matter, comment block, the "done" signal) is fixed in
[references/artifact-layout.md](references/artifact-layout.md). Only `scripts/artifact.mjs` writes
the front matter.
## Steps
1. **Find the task directory.** Ask for the task name if it was not given (kebab-case, one per
branch, issue or lane). List what is already there:
```bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" status --task-dir .ork/tasks/<task>
```
2. **Read every artifact in it in full**, in NN order: research, earlier plans, and their comment
blocks. Open comments on an earlier artifact are requirements unless they were resolved.
3. **Read the code the research points at.** Every file the plan changes must be opened, so file
paths and code in the plan are real.
4. **Write the body** to a scratch file, using
[references/plan-template.md](references/plan-template.md). Each phase is testable on its own,
names the files it changes, and ends with runnable automated checks.
5. **Create the artifact** through the script (never write the file directly):
```bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" create \
--task <task> --kind plan --slug <slug> --title "<title>" --author <your seat> --body /tmp/plan-body.md
# prints .ork/tasks/<task>/NN-plan-<slug>.md
```
6. **Reply with the path and stop.** Ask the reviewer to comment in the file (or run
`/ork:review-artifact-comments` after they do). Do not start implementing.
## Rules
- When documents disagree, the newest wins: plan over research over the original ask.
- Out of scope is a section, not an afterthought: list what the plan will not do.
- Manual checks only where a person really has to look; do not pad phases with them.
- A second plan for the same task is a new artifact (new NN), not an edit of the old one. Revising
the same plan is `iterate-plan`.
## Related Skills
- `/ork:iterate-plan`: revise this plan from review comments, keeping every comment.
- `/ork:create-research`: the research artifact this plan should read first.
- `/ork:review-artifact-comments`: read, answer and resolve comments on any artifact.
Files in this package (4)
- SKILL.md 3 KB
- references/artifact-layout.md 6 KB
- references/plan-template.md 1 KB
- scripts/artifact.mjs 15 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · yonatangross/orchestkit | 100 | MIT |
| drosam/agents | 100 | MIT |
| tzachbon/srulik-toolkit | 100 | MIT |
| atomicinnovation/accelerator | 100 | MIT |
| jkaloger/lazyspec | 100 | MIT |
| davila7/claude-code-templates | 100 | MIT |
| humansintheloop-dev/humansintheloop-dev-workflow-and-tools | 100 | Apache-2.0 |
| flc1125/skills | 100 | MIT |
| joshgons/agent-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 4fbee44a9a59 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100plan-writing
Writes a short plan file of 5-10 verifiable tasks with dependencies. Use when breaking down a new project, feature, complex bug fix or multi-file refactor. - 100plan-work
Break down an issue or task into concrete implementation steps with file locations, code changes, and acceptance criteria. Use when the user asks to "plan the implementation", "break down this task", "create an implementation plan", or needs a structured plan before coding. - 100plan
This skill should be used when the user asks to 'write a plan', 'plan implementation', 'plan milestone', 'create implementation plan', or when planning complex changes — new features, architecture changes, multi-file work, or anything with ambiguous scope. Writes a validated… - 100scope
Use when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes. Writes `.hyperflow/tasks/<slug>.md` with batched sub-tasks, then **auto-chains into `/hyperflow:dispatch`** — no manual gate. - 100quest
Use for multi-file or multi-step changes that need research and a plan — not single-file fixes under ~50 lines that follow an existing pattern (see Escape Hatch below). Runs the Research → Plan → Implement → Review lifecycle with a hard gate leaving each of the first three… - 95write-implementation-plan
Use this skill when the user says 'plan before coding', 'write an implementation plan', 'implementation_plan.md', 'propose changes first', 'what files would you change', 'plan this feature', or when a coding task touches multiple files/modules and approval is expected before…