planner: Skill for Claude Code

.claude/skills/milestone/SKILL.md

milestone is a skill for Claude Code from nickmisasi/planner. It costs 0 tokens per session (2,121 once invoked), scanned A, original, MIT.

A workflow for closing a completed phase of software work as a milestone and preparing the project for its next phase.

In plain words
What is it for?
Archiving project plans and research, closing local worktrees with commits, writing a summary, and resetting working files.
Why use it?
It preserves planning history while cleaning up active planning files and affected worktrees.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool.

This is nickmisasi/planner's own configuration. It tells Claude Code how to work on planner itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything planner configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nickmisasi/planner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nickmisasi/planner/main/.claude/skills/milestone/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nickmisasi/planner

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for milestone

README.md
[![agentmods](https://agentmods.dev/badge/skills/nickmisasi/planner/milestone/github.svg)](https://agentmods.dev/skills/nickmisasi/planner/milestone)
Your own site
<a href="https://agentmods.dev/skills/nickmisasi/planner/milestone"><img src="https://agentmods.dev/badge/skills/nickmisasi/planner/milestone/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for milestone

Your own site · 80×15
<a href="https://agentmods.dev/skills/nickmisasi/planner/milestone"><img src="https://agentmods.dev/badge/skills/nickmisasi/planner/milestone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,121 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02121
Opus 5.5 $0.00000 $0.00848
Sonnet 5.5 $0.00000 $0.00424
Haiku 4.5 $0.00000 $0.00212

Measured 2mo ago against content hash bd0d306807bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

milestone scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/milestone/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

name: milestone description: Complete the current work as a milestone and start fresh for the next phase. Archives current idea files, including IMPL_ORCHESTRATION_PLAN.md when present, closes out affected worktrees with final local commits, archives repo-local .planning/PLAN.md files into milestone folders, writes a summary, and resets working files. Use when the user wants to mark a phase of work as done and move to the next.

Complete the current work on an idea as a milestone. Archive all current planning files (spec, research, assumptions, session, spikes, and IMPL_ORCHESTRATION_PLAN.md if present) into a milestone folder, close out affected implementation worktrees with final local commits, archive repo-local .planning/PLAN.md files into milestone folders inside each worktree, write a summary, and reset working files so the next phase starts clean — while preserving full historical context.

Instructions

When the user invokes /milestone, follow these steps:

1. Ensure Context is Loaded

If you haven't already loaded the current idea's files, read them now:

  • spec.md
  • session.md
  • assumptions.md
  • research.md
  • IMPL_ORCHESTRATION_PLAN.md (if it exists)
  • MILESTONES.md (if it exists — this means prior milestones already exist)

If no idea is currently active, trigger the /continue skill first to select one.

2. Draft the Milestone Summary

Before archiving, synthesize the current state into a milestone summary. Read session.md and spec.md to draft:

  • Milestone name: A short descriptive name (e.g., "POC Validation", "Core API Implementation")
  • Slug: URL-safe version (e.g., "poc-validation", "core-api")
  • Summary: 2-4 sentences capturing what was accomplished
  • Outcome: One of completed, partial, or pivoted
  • Key outcomes: Bullet list of concrete deliverables or validations
  • Key decisions: Carried from session.md
  • What carries forward: What context/decisions/constraints feed into the next milestone

Read the full file on GitHub · 180 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 180 lines · 0 tokens per session scan A bd0d306807bb

Subscribe to this mod's changes

milestone is a skill published in the GitHub repository nickmisasi/planner (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,121 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

milestone compared with skills from other repositories

milestone next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
milestonenickmisasi/plannerSkill56mo agoMITA0Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code