AgentHubv0.4

Create

/hub:create is the heaviest workflow in AgentHub. It dispatches 4–5 specialists in sequence — planner → backend → frontend → database → devops — to scaffold a greenfield app.

When to use it

  • You're starting a new app from an empty directory.
  • You have a clear spec (ideally a plan file).
  • You've budgeted the token spend (~80k–200k typical).

When NOT to use it

  • You're adding to an existing app. Use enhance — it scopes the minimum diff.
  • You haven't decided the stack. Run brainstorm first.

Invocation

/hub:create Next.js SaaS landing with a waitlist form backed by Postgres

What the HEAVY gate looks like

HEAVY — /hub:create "Next.js SaaS landing with waitlist + Postgres"

Planned agents:
  - hub:project-planner       (plan.md, task graph)
  - hub:backend-specialist    (/api/waitlist route)
  - hub:frontend-specialist   (landing, form, confirmation)
  - hub:database-architect    (waitlist table + migration)
  - hub:devops-engineer       (Vercel + Neon config)

Skills loaded:
  nextjs-react-expert, tailwind-patterns, api-patterns,
  database-design, deployment-procedures, clean-code

Token estimate:  ~140k   (P50: ~110k, P95: ~190k)

MoSCoW scope:
  MUST   — landing, form, /api/waitlist, waitlist table, happy path
  SHOULD — email confirmation, rate limit, duplicate guard
  COULD  — Turnstile captcha, admin CSV export
  WON'T  — auth, payments, dashboards (out of scope; use /hub:enhance later)

Lighter alternatives:
  A) /hub:enhance  — if you already have a Next.js base
  B) /hub:plan only — ship the plan first, build tomorrow

Proceed? [y/n/tweak]

Example session (summary)

Building the waitlist app
user
/hub:create Next.js SaaS landing with a waitlist form backed by Postgres
gate
HEAVY · 5 agents · ~140k tokens · MoSCoW shown · [y/n/tweak]
user
y
hub:project-planner
Wrote docs/PLAN-create.md. 5-step graph, agent assignments explicit. Handing off…
hub:database-architect
Created prisma/schema.prisma + 0001_init migration. waitlist(email, created_at, source).
hub:backend-specialist
Added /api/waitlist. Zod input, Prisma insert, duplicate-safe upsert. Contract test included.
hub:frontend-specialist
Landing page, <WaitlistForm>, success state, Tailwind. Reads NEXT_PUBLIC_APP_NAME.
hub:devops-engineer
vercel.json, .env.example with DATABASE_URL + Neon guidance. README updated. All done.

Pro tips

  • Read the gate carefully. The MoSCoW shows what won't be built. Add those things to a follow-up /hub:enhance, not to this run.
  • Pass a plan file when you have one: /hub:create --from docs/PLAN-xyz.md. Drops estimate by ~30% because the planner skips discovery.
  • Watch the ledger afterwards. /hub:ledger last shows per-agent spend. If one agent ate 70% of the budget, that's a signal to tune its skills list.

Next steps

  • Orchestrate — for runs that need ≥3 agents across domains with stricter staging.
  • App builder — the skill that drives stack selection.
  • Tiers & gates — the mechanics behind HEAVY.