Project Orchestrator

Overview

This developer keeps one personal-conventions skill per concern (stack, testing, git workflow, tool priority, superpowers-workflow wrapper) and reuses the same skills across most projects, since most projects share the same stacks. Rather than relying on each individual skill's description to win a naming contest against a well-known built-in skill (e.g. superpowers:brainstorming), this skill is the single mandatory dispatcher: invoke it first, unconditionally, before reaching for any other skill — then let it route to whichever of the skills below actually apply.

This is an ordering rule, not a name substitution: always call project-orchestrator before anything else, the same way EnterPlanMode always precedes superpowers:writing-plans. Once inside this skill, chain into the routed skill(s) below by name — that hand-off is reliable because it's an explicit instruction inside a skill already being followed, not a discovery choice between two similarly-described skills.

Routing Table

Match the current situation against every row that applies (more than one can apply at once — see Chaining below) and invoke the corresponding skill, only if it's installed in this environment: