AgentHubv0.4

Plan

/hub:plan writes docs/PLAN-<slug>.md — a real file you can review, diff, and hand to an agent. No code yet. Just a plan.

When to use it

  • You've decided what to build and want to separate planning from implementation.
  • You're about to spend on a HEAVY command — /hub:plan first costs less than a bad /hub:create.
  • The change spans multiple agents (API + UI + DB) and you want the steps explicit.

When NOT to use it

  • Single-file changes. Skip the plan, go direct.
  • You're still exploring options. Run brainstorm first.

Invocation

/hub:plan add Stripe checkout + webhook + dashboard to the existing Next.js app

Approval gate

MEDIUM: dispatch hub:project-planner with plan-writing + architecture
estimate: ~32k tokens
output: docs/PLAN-stripe-checkout.md

Proceed? [y/n/tweak]

Example session

Planning a Stripe integration
user
/hub:plan add Stripe checkout + webhook + dashboard to the existing Next.js app
gate
MEDIUM · hub:project-planner · ~32k tokens · writes docs/PLAN-stripe-checkout.md · [y/n/tweak]
user
y
hub:project-planner

Explored the repo. Next.js 15 App Router, Prisma, Postgres. Wrote the plan to docs/PLAN-stripe-checkout.md. Highlights:

  • 4 tasks, dependency graph included
  • DB: new subscriptions table, migration staged
  • API: /api/checkout + /api/webhooks/stripe with signature verify
  • UI: /billing route + <PricingCard> component
  • Tests: contract test for webhook, E2E for happy-path checkout

Next: run /hub:enhance --from docs/PLAN-stripe-checkout.md to execute.

Pro tips

  • Review the plan before running the HEAVY command. A 5-minute read saves a 200k-token mistake.
  • Plan files are git-tracked. Commit them with the feature — they make great PR context.
  • Tweak via the plan, not the prompt. Edit the file, re-run enhance --from.

Next steps