# Create Plan

> Create a .plan.md file when the user asks to make a plan, create a plan, write a plan, or similar

- Skill: `majiayu000/create-plan-11` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/create-plan-11`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/create-plan-11/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/create-plan-11

---


Follow the plan creation conventions defined in `.chalk/.cursor/plans/` and any project `AGENTS.md` if present.

## Quick Reference

### Where Plans Live

New plans go into the **unsorted backlog** (root of `.chalk/.cursor/plans/`) by default unless the user specifies a column (`todo/`, `inprogress/`, `testing/`, `done/`).

### Workflow

1. **Check the backlog** — Read filenames in the root of `.chalk/.cursor/plans/` (not subfolders) to find the highest numbered plan. The next plan number is that number + 1.
2. **Draft the plan** — Use the format specified in the conventions file. Break the work into concrete, actionable todos.
3. **Write the file** — Save to `.chalk/.cursor/plans/<number>_<slug>.plan.md`.
4. **Confirm** — Tell the user the plan was created with its filename and a brief summary.

### Filename Convention

```
<number>_<snake_case_slug>.plan.md
```

### Plan File Format

Every plan has YAML frontmatter (`name`, `overview`, `todos` with `id`/`content`/`status`) and a markdown body with `# Title`, `## Objective`, `## Architecture`, `## File Changes`, and `## Key Design Decisions` sections.

Refer to `AGENTS.md` for the full spec and format details.