Skip to content
Development
Skill

/planner

Interactive planning and execution for complex tasks. IMMEDIATELY invoke when user asks to use planner.

From plugin
claude-config
89811 skills5 agents
Install
$ npx -y skills add solatis/claude-config --skill planner --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/planner

Context preview

The summary Claude sees to decide when to auto-load this skill.

Interactive planning and execution for complex tasks. IMMEDIATELY invoke when user asks to use planner.

SKILL.md

planner.SKILL.md
name: planner
description: Interactive planning and execution for complex tasks. IMMEDIATELY invoke when user asks to use planner.

Activation

When this skill activates, IMMEDIATELY invoke the corresponding script. The script IS the workflow.

| Mode | Intent | Command | | --------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | planning | "plan", "design", "architect" | `<invoke working-dir=".claude/skills/scripts" cmd="python3 -m skills.planner.orchestrator.planner --step 1" />` | | execution | "execute", "implement", "run plan" | `<invoke working-dir=".claude/skills/scripts" cmd="python3 -m skills.planner.orchestrator.executor --step 1" />` |

Ships withclaude-config

I use Claude Code for most of my work. After months of iteration, I noticed a pattern: LLM-assisted code rots faster than hand-written code.

Get the whole plugin