create-workflow-command — Claude Code skill: what it does, setup
This skill generates multi-step workflow commands that delegate execution to sub-agents using dedicated task files, preventing context bloat in complex runs.
npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a claude-codeWhat create-workflow-command does
The skill builds workflow orchestrators designed to stop context bloat. Instead of dumping every step instruction into a single orchestrator prompt, it offloads heavy prompts into discrete files inside the tasks/ folder. The orchestrator stays lean at roughly 50 to 100 tokens per step, while sub-agents read their own 500-token instructions only when triggered.
It structures tasks for sequential handoffs, parallel sweeps across codebase reviews, or stateful continuation using the resume parameter with an existing agent ID. You can choose whether steps run on Claude Haiku or Sonnet based on workflow complexity.
Keep in mind that spawned sub-agents operate under specific limits: they cannot nest the Task tool to spawn further sub-agents, and they do not inherit active skills. Every tool requirement must go directly into the task markdown files.
What it helps with
- prevent orchestrator context bloat across multi-stage jobs
- generate structured markdown task prompts in the
tasks/directory - configure parallel sub-agent sweeps for code or security analysis
- chain execution steps using sub-agent IDs and the
resumeparameter
Example prompts for the agent
- Create a feature-implementation workflow command that splits work into research, planning, and coding phases
- Generate a code-audit workflow command that runs security and quality sub-agents in parallel
- Set up a multi-step release workflow that preserves context across stages using resume
How to install create-workflow-command
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a claude-code2Manually: put the files in place
~/.claude/skills/create-workflow-command/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-workflow-command/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a codex2Manually: put the files in place
.agents/skills/create-workflow-command/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a cursor2Manually: put the files in place
.cursor/skills/create-workflow-command/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NeoLabHQ/context-engineering-kit create-workflow-command2Manually: put the files in place
.github/skills/create-workflow-command/SKILL.md1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a gemini-cli2Platform CLI
gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/create-workflow-commandManually: put the files in place
.devin/skills/create-workflow-command/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-workflow-command
How do I install create-workflow-command in Claude Code?
Run npx skills add NeoLabHQ/context-engineering-kit --skill create-workflow-command -a claude-code.
Why does create-workflow-command store step instructions in separate files?
Storing detailed steps in the tasks/ directory prevents context bloat, keeping the orchestrator prompt around 50 to 100 tokens per step while sub-agents load instructions on demand.
Can sub-agents spawned by the workflow run their own sub-agents?
No, spawned sub-agents cannot nest the Task tool and do not automatically inherit installed skills.
