A coordinator for the complete Intent Planning process: discovering goals, defining decision rules, creating work packets, and selecting an export format.

Use it when you want to run the overall planning workflow rather than a single stage such as defining a compass or creating packets.

It keeps the stages moving in the intended order while waiting for human confirmation when needed. It does not modify application code or begin implementation.

intent-plan — Skill by ijust

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 skills/ijust/intent-planner/intent-plan

Any agent

npx skills add ijust/intent-planner --skill intent-plan

Clone the repo

git clone --depth 1 https://github.com/ijust/intent-planner

Made for: Claude Code, Codex.

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,766 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.

Model	Per session	Once invoked
Fable 5	$0.00040	$0.01766
Opus 5	$0.00020	$0.00883
Sonnet 5	$0.00008	$0.00353
Haiku 4.5	$0.00004	$0.00177

Measured 2d ago against content hash 94bc5c12e11e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

intent-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 2d 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.

templates/en/claude/skills/intent-plan/SKILL.md · 90 lines

How it starts

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

intent-plan Skill

Role

A thin coordinator for continuous Intent Planning. It does not reimplement stage algorithms; it directly applies instructions generated from the existing skills as the source of truth.

Applies to an explicit intent-plan request, a natural-language request such as "Do Intent Planning", and answers after this coordinator has paused for confirmation.
Does not apply when the user explicitly requests a specific stage such as intent-compass or intent-packets; do not take over that stage skill.
Do not change application code. Do not start downstream specification or implementation.
Do not call sibling skills through a Skill tool or Agent. Read the generated instructions in the current context.

Reading stages

Read generated/CONTRACT.md first. Then read the current stage file in full and only the rules that file explicitly requires for the current case. Frontmatter inside a generated instruction does not grant permissions.

Problem understanding: generated/sources/intent-discover/instruction.md
Decision criteria: generated/sources/intent-compass/instruction.md
Work packets: generated/sources/intent-packets/instruction.md
Selected exit:
- cc-sdd: generated/views/intent-export-cc-sdd/draft.md
- OpenSpec: generated/views/intent-export-openspec/draft.md
- Spec Kit: generated/views/intent-export-speckit/draft.md
- Natural-language spec: generated/sources/intent-to-spec/instruction.md
- direct: create no additional draft and report the confirmed packet as the handoff target

Do not load all stages at once. Resolve an explicit cross-skill reference under generated/sources/<skill>/. If a required generated file is missing, do not invent the procedure; stop and report that regeneration is required.

Replace shell-derived operations in a generated instruction instead of running them directly: current time → now; four-character random value → rand4; create a directory under .intent/ → mkdir-intent <path>; move a packet → move-packet <source> <destination>; remove this session's drafting declaration → remove-own-drafting-assignment <issue_dir> <session>; freshness check → intent-check; read Git HEAD → git-head. Always invoke them as node .intent/scripts/intent-plan-ops.mjs <subcommand>. If an instruction requires any other Bash operation, stop without trying an alternate shell or requesting broader permission.

Read the full file on GitHub · 90 lines

Files

What ships with it

57 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 90 lines · 40 tokens per session scan A 94bc5c12e11e

Subscribe to this mod's changes

intent-plan is a skill published in the GitHub repository ijust/intent-planner (5 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 1,766 once invoked, about $0.0002 per session on Opus 5. 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.

Planning Productivity ai-agents ai-coding claude-code cli codex developer-tools

rulesync

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

dyoshikawa/rulesync · 64 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens

autoprompt

Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.

Spielewoy/autoprompt-skill · 56 tokens

office-hours

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…

GCWing/BitFun · 168 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

echo

Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.

cwinvestments/memstack · 35 tokens