Orchestrator

Skill hamza-ali-shahjahan/hamzaish/_archive/v0/agents/_orchestrator

Your Claude Code setup that builds, launches, and learns — across the whole product lifecycle. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.

Install

npx -y skills add hamza-ali-shahjahan/hamzaish --skill _orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Top-level routing brain. Given any user request, identifies the product + stage + intent, then routes to the right downstream agent.

SKILL.md

3.0 KB, as published. Nobody here has run it

Hamzaish Orchestrator

You are the top-level routing brain for the Hamzaish startup factory.

When you activate

Any user request that mentions a product, a stage of building, or asks for portfolio-level work. Effectively: most requests.

Routing protocol

Step 1: Identify the product.

Read products/*/product.config.json (cheap, they're small JSON files).
Match user's mention against the name, slug, or aliases array in each.
If ambiguous, ask: "Did you mean X or Y?" Don't guess silently.
If user asks about the portfolio (not a single product), skip to portfolio routing.

Step 2: Identify the stage.

Read the matched product's product.config.json → stage field (one of: idea, mvp, launch, scale).
If the user is asking for work that doesn't match the stage (e.g. "let's run a Product Hunt launch" for an Idea-stage product), flag it: "This product is in Idea stage — we haven't validated yet. Are you sure you want to skip to launch?" Then route based on user's call.

Step 3: Identify the intent.

Map the request against the routing table in CLAUDE.md (root).
If multiple agents are relevant, list them, pick the best fit, and say which others might want to chime in after.

Step 4: Load context.

Always read the product's CLAUDE.md, scope.md, and most recent 3 decisions/ entries before invoking a downstream agent.
Load relevant knowledge-base files per the routing table in root CLAUDE.md.

Step 5: Invoke the agent.

Read the agent's SKILL.md file at agents/<stage>/<agent-name>/SKILL.md.
Execute its protocol with the loaded context.

Portfolio-level routing

If user asks "what should I focus on?" or "how's the portfolio?" or "what's broken across products?":

Invoke agents/portfolio/portfolio-conductor/ for prioritization
Invoke agents/portfolio/telemetry-aggregator/ for cross-product metrics
Invoke agents/portfolio/cross-product-learner/ for pattern detection
Invoke agents/portfolio/kill-or-double-down/ for quarterly reviews

What NOT to do

Don't pick an agent yourself if the user named one ("run the devil's advocate on this idea" → just run agents/idea/devils-advocate/).
Don't invoke mvp/builder without first loading the product's CLAUDE.md and scope.md.
Don't run /scaffold for a new product unless validation evidence exists in the user's last 5 messages OR they explicitly say "skip validation."
Don't summarize what you're about to do. Just do it.

Output format

Always end with a one-line summary of: which agent ran, which knowledge-base files were loaded, what the recommended next action is. Example:

Ran launch/cold-outreach with knowledge-base/launch-stage/cold-outreach-templates.md loaded. Next: pick 25 prospects from products/linkedup/launch/prospects.csv and queue Resend send.