Skip to main content
skill CX Codex

01-plan — Claude Code skill: phased plan and install

01-plan turns a request, a ticket or a file into a phased implementation plan: gather the input, read the code, hand back a plan.

MIT ★ 571 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-framework
Open on GitHub

What 01-plan does

Point the skill at a request, a ticket or a file and it returns an implementation plan split into phases. The run goes through three actions: capture records the input, explore reads the code, conclude writes the plan. Each one lives in its own file under actions/, so the agent opens the file and follows it.

While explore runs, the agent comes back with a question whenever a decision blocks it. You get asked rather than guessed at. It also stays quiet otherwise: questions and the final reply, tool calls in between.

Plan files are the only thing it writes. That makes this a step before coding, not a replacement for it — expect a plan and a stop unless you ask for the build separately.

What it helps with

  • break a ticket into phases before coding starts
  • draft a feature plan from the existing codebase
  • keep the agent from writing code too early
  • surface blocking decisions as questions to you
  • turn a written request into a plan file

Example prompts for the agent

  • Plan the AUTH-142 ticket as phases and save the plan.
  • Read spec.md and write a phased implementation plan, no code yet.
  • Split this request into phases and ask me wherever a decision blocks you.

How to install 01-plan

1Plugin marketplace

/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-framework

This installs the whole aidd-dev plugin with all its skills

2Skills CLI (Vercel)

npx skills add ai-driven-dev/framework --skill 01-plan -a claude-code

3Manually: put the files in place

~/.claude/skills/01-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/01-plan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 01-plan

How do I install 01-plan in Cursor?

Run npx skills add ai-driven-dev/framework --skill 01-plan -a cursor. The skill lands at .cursor/skills/01-plan/SKILL.md.

What does 01-plan do?

It turns a request, ticket or file into a phased implementation plan through three actions: capture, explore and conclude.

Does it write code?

No. Plan files are the only output, so run it before implementation and request the build separately.

Source text

SKILL.md · MIT
---
name: 01-plan
description: Turn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Not for writing code or reviewing a diff.
argument-hint: request | ticket | file
---
# Plan

## Actions

```mermaid
flowchart LR
  capture --> explore
  explore -->|"the code opens a question"| explore
  explore -->|"a decision blocks"| user((user answers))
  user --> explore
  explore -->|"nothing blocks"| conclude
  conclude -->|"correct: revise, ask again"| conclude
  conclude -->|"explore more"| explore
  conclude -->|"approve"| done((done))
```

Read an action's file, then do what it says.

| Action | File |
| ------ | ---- |
| capture | [actions/01-capture.md](actions/01-capture.md) |
| explore | [actions/02-explore.md](actions/02-explore.md) |
| conclude | [actions/03-conclude.md](actions/03-conclude.md) |

## Transversal rules

- Speak only to ask or to give the final reply; otherwise call tools.
- Plan only: the plan files are the only files you write.

© AI-Driven Dev · MIT · ai-driven-dev/framework

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set80

The whole set →
03-context-generate The 03-context-generate skill routes requests to create skills, rules, agents, commands, or hooks to the matching generator. If you leave out the artifact type, it asks which one you mean. CX Codex +1 ★ 571repo stars 04-spec 04-spec writes spec.md, the contract for a single feature, from a request, a PRD or review notes. Or rewrites a spec that already exists. CX Codex +1 ★ 571repo stars resolve-conflict resolve-conflict resolves deterministic Git conflicts during merge, rebase, or cherry-pick. Stops right after staging modified files. CX Codex +1 ★ 571repo stars 0-deps-wiring The 0-deps-wiring rule sets where application dependencies are composed and how the graph is reused. It fits TypeScript projects with command handlers and use cases. CX Codex +1 ★ 571repo stars 05-improve 05-improve examines conversation logs, evaluates visible token usage, and suggests targeted refinements without touching your code. CX Codex +1 ★ 571repo stars 1-documentation The 1-documentation rule guides edits to project Markdown: it keeps decisions and useful commands while removing repetition and temporary records. It applies to selected files and folders. CX Codex +1 ★ 571repo stars 03-prd 03-prd turns a need, idea or brainstorm into a structured product requirements document: a draft from a template, saved only once you approve it. CX Codex +1 ★ 571repo stars 08-three-amigos 08-three-amigos evaluates epics and user stories through product, delivery, or quality perspectives, then reconciles three separate reports before backlog edits. CX Codex +1 ★ 571repo stars

Project sponsors

Companies that keep this analytics open