How do I install the Curriculum Planner skill?

Run npx skillmds add majiayu000/curriculum-planner 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 Curriculum Planner safe to use?

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

Which AI agents work with Curriculum Planner?

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 Curriculum Planner free to use?

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

Who published Curriculum Planner?

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

Curriculum Planner by majiayu000 — Agent Skill

Name: Curriculum Planner
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Curriculum Planner

Generates sequences of high-leverage tasks that increase understanding and improve the code. Use when: - "what should I work on next?" - suggests prioritized tasks - "create a plan for this repo" - generates a curriculum - "what's the roadmap?" - shows curriculum overview - "help me onboard to this codebase" - creates learning tasks - "plan a refactor" - structures improvement work - "prioritize these features" - organizes work into tracks - "make an onboarding plan" - creates a learning path - "create a learning path for this repo" - sequences learning tasks - "roadmap this refactor" - plans improvement work - "write the curriculum to disk" - persists plan artifacts

majiayu000 3d14750 2 files · 3.7 KB Updated Sep 9, 2026 567 repo stars

File contents

Repo Curriculum Planner

Generates structured learning/improvement plans based on repo state and session brain.

Two Usage Modes

Mode 1: Propose in Chat (default)

When a user asks for planning help, propose tasks directly in the conversation without writing files. This is the default behavior for quick suggestions.

Examples:

"what should I work on next?" → Suggest 2-3 high-priority tasks in chat
"what's the roadmap?" → Describe the plan conversationally
"help me prioritize" → Discuss tradeoffs and recommend order

Mode 2: Write Artifacts to Disk

Only write to .claude/voyager/ when the user explicitly asks to persist the plan:

"write the curriculum to disk"
"save this plan"
"generate curriculum files"
"materialize the plan"

This writes:

.claude/voyager/curriculum.json — structured task backlog
.claude/voyager/curriculum.md — human-readable plan

Trigger Phrases

Use this skill when you hear:

"what should I work on next?"
"create a plan"
"what's the roadmap?"
"help me onboard"
"plan the work"
"prioritize features"
"what tasks remain?"
"make an onboarding plan"
"roadmap this refactor"

On-Disk Plan Artifacts

When persisted, the plan lives at:

.claude/voyager/curriculum.json — structured JSON with full task details
.claude/voyager/curriculum.md — rendered Markdown for human review

To refresh an existing plan, run:

voyager curriculum plan

To preview without saving:

voyager curriculum plan --dry-run

Task Structure

Each task includes:

id — unique identifier (e.g., t01)
title — short action-oriented title
why — rationale for the task
estimated_scope — trivial, small, medium, or large
acceptance_criteria — how to know it's done
suggested_files — where to look
commands_to_run — verification commands
depends_on — prerequisite task IDs
status — pending, in_progress, done, or blocked

Updating Task Status

Edit curriculum.json directly to update task status:

Change "status": "pending" to "in_progress" when starting
Change to "done" when complete

See reference.md for implementation details and schema reference.

---name: curriculum-plannerdescription: Generates sequences of high-leverage tasks that increase understanding and improve the code. Use when: - "what should I work on next?" - suggests prioritized tasks - "create a plan for this repo" - generates a curriculum - "what's the roadmap?" - shows curriculum overview - "help me onboard to this codebase" - creates learning tasks - "plan a refactor" - structures improvement work - "prioritize these features" - organizes work into tracks - "make an onboarding plan" - creates a learning path - "create a learning path for this repo" - sequences learning tasks - "roadmap this refactor" - plans improvement work - "write the curriculum to disk" - persists plan artifacts--- # Repo Curriculum Planner Generates structured learning/improvement plans based on repo state and session brain. ## Two Usage Modes ### Mode 1: Propose in Chat (default) When a user asks for planning help, **propose tasks directly in the conversation** without writing files. This is the default behavior for quick suggestions. Examples: - "what should I work on next?" → Suggest 2-3 high-priority tasks in chat - "what's the roadmap?" → Describe the plan conversationally - "help me prioritize" → Discuss tradeoffs and recommend order ### Mode 2: Write Artifacts to Disk Only write to `.claude/voyager/` when the user **explicitly asks** to persist the plan: - "write the curriculum to disk" - "save this plan" - "generate curriculum files" - "materialize the plan" This writes: - `.claude/voyager/curriculum.json` — structured task backlog - `.claude/voyager/curriculum.md` — human-readable plan ## Trigger Phrases Use this skill when you hear: - "what should I work on next?" - "create a plan" - "what's the roadmap?" - "help me onboard" - "plan the work" - "prioritize features" - "what tasks remain?" - "make an onboarding plan" - "roadmap this refactor" ## On-Disk Plan Artifacts When persisted, the plan lives at: - `.claude/voyager/curriculum.json` — structured JSON with full task details - `.claude/voyager/curriculum.md` — rendered Markdown for human review To refresh an existing plan, run: ```bash voyager curriculum plan ``` To preview without saving: ```bash voyager curriculum plan --dry-run ``` ## Task Structure Each task includes: - `id` — unique identifier (e.g., `t01`) - `title` — short action-oriented title - `why` — rationale for the task - `estimated_scope` — `trivial`, `small`, `medium`, or `large` - `acceptance_criteria` — how to know it's done - `suggested_files` — where to look - `commands_to_run` — verification commands - `depends_on` — prerequisite task IDs - `status` — `pending`, `in_progress`, `done`, or `blocked` ## Updating Task Status Edit `curriculum.json` directly to update task status: - Change `"status": "pending"` to `"in_progress"` when starting - Change to `"done"` when complete See `reference.md` for implementation details and schema reference.

Frequently asked questions