ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. Load create-tasks via load_tool before calling it (search "create tasks" if not visible). Do NOT use for new one-off workflows, single-workflow edits, verification-only requests, or standalone data-table ops — use workflow-builder or data-table-manager instead.
Planning Use this skill to design a dependency aware task graph in the orchestrator and submit it with . Do not spawn another agent and do not use incremental plan item tools. Before calling , load it via (search "create tasks" if it is not visible). When NOT to use this skill Stop and use + instead when the request is: A new or one off single workflow, even if it sounds large or unfamiliar An edit to one existing workflow (nodes, expressions, credentials, schedule, Code) Verification, setup,…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/planning · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/planning"
cp -r "packages/@n8n/instance-ai/skills/planning" ".claude/skills/planning"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.