AgentHubv0.4

hub:project-planner

The agent behind /hub:plan. Turns a goal into a dependency-graph-aware plan file — with step assignments, task estimates, and scope cuts.

What it's good at

  • Splitting a vague goal into ordered tasks with explicit hand-offs.
  • Deciding which agent should own each step (without duplicating work).
  • Cutting scope — MoSCoW by default, with “WON'T” stated explicitly.
  • Producing docs/PLAN-<slug>.md that survives your next session.

What it won't do

  • Write code. That's a non-goal — if you're doing both, use /hub:create.
  • Plan multi-domain orchestration. That's hub:orchestrator — it's a superset.
  • Invent requirements. If your goal is under-specified, it asks (via the socratic-gate skill).

Skills it loads

plan-writing, architecture, socratic-gate, clean-code, documentation-templates.

When Claude auto-dispatches it

Triggers: plan, break down, roadmap, task list, dependency graph, milestones, PLAN.md, architecture plan.

Example session

Planning a data-export feature
user
/hub:plan add async CSV export for users, email when ready, retention 7 days
hub:project-planner

Explored repo (Next.js + Prisma + Postgres + Resend). Plan written to docs/PLAN-csv-export.md. Summary:

  1. DB: export_jobs table — id, user_id, status, url, expires_at. Migration staged.
  2. Backend: POST /api/exports returns 202 + job id. Worker route /api/jobs/run generates CSV, stores in R2, updates job, sends email via Resend.
  3. Frontend: <ExportButton> on settings page, poll-based status.
  4. Infra: daily cron purges jobs older than 7d (Vercel Cron).

Dependency graph: DB → Backend → Frontend; Infra parallel to Frontend. MoSCoW: MUST happy path + retention; SHOULD retry on email fail; COULD inline small exports (≤1000 rows).

Next: /hub:enhance --from docs/PLAN-csv-export.md.

Direct call

/hub:agent-project-planner plan async CSV export with email notification

Pro tips

  • Feed it the repo. No prompt tweak beats letting the planner actually glob your stack first.
  • Read the “WON'T” line. That's where plans fail — the planner is telling you what's not in scope. Agree or tweak.
  • Git-track plan files. They age into great PR descriptions.

Next steps