Plan

Splits a spec into small tasks, each a working slice an agent can finish in one pull request. Use when a spec is too big for one PR, or to create tracker tickets.

434 stars 73 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add owainlewis/blueprint --skill plan
Manual install
git clone --depth 1 https://github.com/owainlewis/blueprint.git /tmp/blueprint
mkdir -p ~/.claude/skills
cp -r /tmp/blueprint/skills/plan ~/.claude/skills/plan

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Plan

Split decided work into tasks that each deliver something that works, end to end, in one pull request. Split by result, never by layer: "add a task and see it after a restart" is one task covering input, storage, and output, not three.

## Steps

1. Read the spec, the repository instructions, and the code it touches. If a decision is missing, return to [spec](../spec/SKILL.md).
2. Write each task with the template below. Keep shared contracts in one task, and put refactoring in its own task if it would hide a behavior change.
3. Order tasks by dependency. Group them into milestones only when a milestone is itself a usable result.
4. Return the plan in chat. Create tracker tickets only if the user asks. Do not write a plan file or start building.

## Template

```markdown
## <Action and result, in plain words>

### What are we building?
<One to three sentences: what is missing today and what will work after this task.>

### Why?
<One or two sentences on the value to a user or developer.>

### Done when
- <Three to seven results someone can see or test. Keep AC-n, J-n, and REQ-n IDs.>

### How to check
<Exact commands, and any manual check.>

### Agent notes
- Depends on: <task titles, or None>
- Source: <link to the spec section>
- <Decisions and failure rules specific to this task. Link the spec for the rest.>

### Out of scope
- <Nearby work this task might absorb by mistake.>
```

## Rules
Read the full skill on GitHub

Details

Skill name
plan
Path
skills/plan/SKILL.md
License
MIT
Repo updated
10 November 2026

FAQ

What does the Plan skill do?

Splits a spec into small tasks, each a working slice an agent can finish in one pull request. Use when a spec is too big for one PR, or to create tracker tickets.

How do I install the Plan skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add owainlewis/blueprint --skill plan. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Plan popular?

It lives in owainlewis/blueprint, which has 434 GitHub stars and 73 forks.

Related skills

Architecture

434

owainlewis/blueprint

Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every feature must follow. Use for a new system or a change to its boundaries, data, or deployment.

Software Development73

Architecture Review

434

owainlewis/blueprint

Reviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that would make it wrong, unsafe, or impossible to prove, and the open questions that block building it.

Software Development73

Codex Issue Coordinator

434

owainlewis/blueprint

Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.

Software Development73

Review

434

owainlewis/blueprint

Runs an independent, read-only review of a code change in two parts: does it match the spec, and does it work. Tries bad input, checks security, and checks that the tests would catch a regression. Use for a diff, branch, commit, or PR.

Git & Code Review73

Greploop

437

greptileai/skills

Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review, and repeats. Use when the user wants to fully optimize a PR/MR/CL against Greptile's code review standards.

Git & Code Review47

Task to PR

434

owainlewis/blueprint

Delivers a spec, issue, or decided task as a pull request that passes its checks, CI, and an independent review. Leaves the PR open unless merging was explicitly authorized.

Git & Code Review73

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.