Open source · MIT

Feature plans for
LLM-assisted development.

One command sets up your project so any supported coding agent automatically creates, follows, and maintains structured feature plans across sessions.

Get started See how it works
$ uvx planager init
How it works

Plans that survive context windows.

Step 1

Install

Run uvx planager init in your project. Pick your agent from the menu and it sets up the right files. No config and no runtime.

Step 2

Plan

Use /planager to create a phased plan before tackling a feature. Your agent explores the codebase, drafts steps, and saves a plan file.

Step 3

Build

The agent checks, follows, and updates plans automatically every session. Use /planager-status to see progress across all features.

.plans/
Plan files (markdown or HTML) with metadata, phases, and checkboxes.
/planager
Create or resume a plan for any feature.
/planager-status
See progress across all plans in a table.
Agent skills
Auto-installed for Claude Code, pi.dev, or Codex. Plans are discovered without prompting.
Plain files

No special tools, just files.

Plans are plain files (markdown or HTML) checked into your repo. Any agent that can read files can follow them. Works with Claude Code, pi.dev, Codex, or any LLM-based workflow.

Idempotent - re-running init updates in place
No background processes or servers
MIT licensed, zero dependencies 
---
feature: auth
title: User Authentication
status: in-progress
created: 2026-04-18
---

## Context

Implement email/password auth with sessions.

## Phase 1: Database schema

- [x] Create users table migration
- [x] Add password hashing utility
- [ ] Add session table migration

## Phase 2: API endpoints

- [ ] POST /login
- [ ] POST /register

## Notes

Using bcrypt. Decided against JWT.
Documentation

Getting started

Prerequisites

Planager uses uv for installation. Install it with:

curl -LsSf https://astral.sh/uv/install.sh | sh

Install

Run this from your project root:

cd your-project
uvx planager init

You'll see a menu to pick your agent:

  Welcome to planager! Which agent are you using?

    1. Claude Code  —  Anthropic's Claude Code agent
    2. pi.dev  —  The pi coding agent
    3. Codex  —  OpenAI's Codex agent

  Select [1-3] (default: 1):

Full usage:

uvx planager init [target] [--path DIR] [--style markdown|html]
target Agent to set up: claude, pi, or codex. Omit to choose interactively.
--path Project root directory (default: current directory).
--style Plan file format: markdown (default) or html.

Idempotent — running it again updates files in place. You can init multiple agents in the same project.

What gets created

.plans/ Directory where feature plans live (markdown or HTML files).
<agent>/skills/planager/ Skill for creating and resuming plans. Installed to .claude/skills/, .pi/skills/, or .codex/skills/ depending on your selection.
<agent>/skills/planager-status/ Skill for checking progress across all plans.
CLAUDE.md or AGENTS.md Auto-injected snippet so your agent discovers plans without prompting.

Plan styles

By default, plans are markdown files. Pass --style html to use standalone HTML files instead (zero JS dependencies).

uvx planager init claude --style html

HTML plans use <meta> tags for metadata and data-status attributes for step tracking. They're viewable directly in a browser with styled checkmarks.

To switch an existing project, just re-run init with the new style. The instruction snippet and skill files are updated in place.

Slash commands

/planager  ·  /skill:planager  ·  $planager

Create a new feature plan or resume an existing one. With a description, it explores the codebase and drafts a phased plan. Without, it lists in-progress plans.

/planager-status  ·  /skill:planager-status  ·  $planager-status

Show a progress table across all plans — feature name, status, and step counts per phase.

Agent Skills dir Instruction file Commands
Claude Code .claude/skills/ CLAUDE.md /planager
pi.dev .pi/skills/ AGENTS.md /skill:planager
Codex .codex/skills/ AGENTS.md $planager