planner

Create, update, and close in-repo multi-session plans with frontmatter fields.

3|Updated May 13, 2025
One-click install
npx skills add https://github.com/wcygan/anton --skill planner-wcygan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/planner
Command: npx skills add https://github.com/wcygan/anton --skill planner-wcygan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Anton planner enables teams to author, update, and close multi-session initiatives directly in the repository, ensuring long-running work remains organized across sessions and memory hints are translated into durable plans.

Core Features & Use Cases

  • Create, list, update, and close plans that live in context/plans/NNNN-kebab-slug.md, capturing execution state, decisions, and next steps.
  • Use for migrations, rollouts, and refactors that span multiple commits or time horizons; keep ADRs and memory in sync.
  • Review open work, migrate in-flight memory into durable plans, and surface plan status in Claude Code sessions via an injected plans index.

Quick Start

Open a new plan for a multi-session initiative using /planner new "<title>" and complete the goal, acceptance criteria, and initial tasks.

Frequently Asked Questions about planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track multi-session initiatives across separate work sessions in a repository?

Multi-session initiatives are tracked by creating durable in-repo plans that persist execution state, decisions, and next steps across sessions. These plans live as markdown files within the context/plans directory and evolve as work progresses.

What's the best way to convert transient memory entries into durable project plans?

Migrating in-flight memory entries into durable plans is handled through a dedicated memory-to-plan workflow. This process translates temporary memory hints into structured plan files with frontmatter fields tracking status, opened dates, and related ADRs.

How do I create a new plan for a long-running refactor or rollout?

Creating a new plan for long-running refactors or rollouts starts by opening a plan with a title, then defining the goal, acceptance criteria, and initial tasks. The plan is saved as a numbered kebab-slug markdown file in the context/plans directory.

Can I enforce plan lifecycle rules like status tracking and review dates in markdown files?

Plan lifecycle rules are enforced using frontmatter fields such as status, opened, reviewed, and related-adrs within each plan file. These fields govern plan mutability and provide structured workflows for new, list, update, and close operations.

How does reviewing open work across multiple plans work during active development?

Reviewing open work across plans involves scanning the context/plans directory for status updates and next steps. An injected plans index surfaces current plan status directly in Claude Code sessions, keeping ADRs and memory synchronized as plans progress.