plan

A group of project-planning commands for breaking down features, organizing sprints, and creating long-term roadmaps.

In plain words
What is it for?
Use it to plan features, prepare an iteration or sprint, and map a project roadmap.
Why use it?
It turns broad development work into tasks, priorities, dependencies, capacity plans, milestones, and timelines.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/data-wise/claude-plugins/plan
Clone the repo
git clone --depth 1 https://github.com/Data-Wise/claude-plugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.05189
Opus 5 $0.00000 $0.02594
Sonnet 5 $0.00000 $0.01038
Haiku 4.5 $0.00000 $0.00519

Measured yesterday against content hash 6d13075c6e5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan 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 yesterday.

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.

craft/docs/commands/plan.md · 669 lines

How it starts

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

Planning Commands

⏱️ 15 minutes • 🟡 Intermediate • ✓ Project planning and roadmaps

TL;DR (30 seconds)

  • What: 3 commands for feature planning, sprint organization, and roadmap creation
  • Why: Break down features into tasks, organize team capacity, and visualize long-term project direction
  • How: Use /craft:plan:feature to plan individual features, /craft:plan:sprint for iteration planning, /craft:plan:roadmap for timeline visualization
  • Next: Try /craft:plan:feature "your feature description" to see a structured plan

Craft's planning commands help you organize work, estimate effort, identify dependencies, and communicate project direction with AI-powered task breakdown and timeline visualization.


Commands Overview

Command Purpose Time (default) Focus
/craft:plan:feature Feature breakdown and scoping < 60s User stories, tasks, acceptance criteria
/craft:plan:sprint Sprint planning and capacity < 90s Prioritization, team capacity, goals
/craft:plan:roadmap Long-term roadmap creation < 120s Milestones, phases, timeline visualization

All commands support flexible scoping (MVP/full/enterprise) and multiple output formats.


/craft:plan:feature - Feature Planning

Break down features into actionable tasks with estimates, dependencies, and acceptance criteria.

Quick Start

/craft:plan:feature "user profile page with avatar upload"
/craft:plan:feature "search functionality" --scope mvp
/craft:plan:feature "payment integration" --include-tests
/craft:plan:feature "notifications" --format github --output PLAN.md

Options

Option Values Default Purpose
--scope mvp, full, enterprise full Planning scope
--format markdown, jira, github markdown Output format
--output filename stdout Save to file
--include-tests boolean false Include test planning

Read the full file on GitHub · 669 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. yesterday First seen · 669 lines · 0 tokens per session scan A 6d13075c6e5a

Subscribe to this mod's changes

plan is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,189 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.