handbooksThe orchestrator skill
develop-new-digital-product does not do any of the work itself. It names three phases, in order, and which skill to invoke for each one.
Claude CodeLast reviewed September 3, 2026
In one minute
- This is the top of the tree in the Skills Showcase. Nothing invokes it, it invokes everything else.
- Its job is routing, not doing. The body is a three-phase list with instructions for which skill to reach for at each one.
- Its
descriptionhas to cover the whole process in one or two sentences, specific enough that Claude reaches for it, and not a phase skill directly, when the request is genuinely "build me something new." - All three phases fan out into their own sub-skills. Unlike the first draft of this example, no phase here is a bare leaf.
SKILL.md
.claude/skills/develop-new-digital-product/SKILL.md
yaml
---
name: develop-new-digital-product
description: Runs the full process for building a new digital product, from a raw idea to a validated, accessible, SEO-ready launch. Use when the user wants to build something new and does not yet have a plan broken into phases.
---
## Phases, in order
1. Definition and planning -> invoke /definition-and-planning
(covers understanding the idea, research, product definition, and planning)
2. Implementation -> invoke /implementation
(covers the database, backend, frontend, and integration and deployment)
3. Pre-launch activities -> invoke /pre-launch-activities
(covers validation and testing, SEO, accessibility, and UI/UX polish)
Work through these phases in order. Do not skip a phase without telling the user which one and why.- Each phase line names what it covers in parentheses, the same trick the earlier version of this skill used for research and planning. That is what tells Claude a phase is not a single step, without needing a fourth level in the tree to prove it.
- "Do not skip a phase without telling the user" is the one enforcement-flavored line in the whole file, and it is still advice. A rule that must never be skipped belongs in a hook, not a skill description.
Why the description matters most here
An orchestrator's description has to do two jobs a phase skill's does not. It has to be broad enough to match "I want to build X" before any phase has even been chosen, and specific enough that Claude does not reach for it once the user is already deep in one phase. "Review my database schema" should match Database implementation directly, not restart the whole process from the top.
Where it fits
Nothing sits above this skill. It is the entry point for the whole example. It hands off to three phase skills, in a fixed order: Definition & planning, Implementation, and Pre-launch activities.
Last reviewed September 3, 2026