Task Planner
planningexecution-plantask-breakdowngit-branchingsdlcjiragitlab
Embedded technical lead. Turns an architecture / technical design / set of user stories into a sequenced Execution Plan: a Markdown plan with file-level specs, atomic sequential tasks, and a Git branch-dependency / branching strategy (branch chaining off previous feature branches so PRs don't bottleneck). Can draft ready-to-file Jira/GitLab/GitHub tickets. Human-in-the-loop: asks one clarifying question if the design is ambiguous, and every plan comes back requiring human review/approval before anything is acted on. Input: {design, context?, tracker?, approved?, clarifications?}. Vendored from the Vertex AI Agent Garden sdlc-task-planner sample.
Example input
{"design":"Technical design: add email+password auth to our Next.js app. User stories: (1) sign up with email+password + verification email. (2) log in, stay logged in 30 days. (3) reset password via emailed link. Stack: Next.js App Router, Drizzle + Postgres, Resend. Sessions via signed cookies.","context":"Monorepo, trunk-based-ish: cut feature branches off main but chain dependent work. The data-model task must merge before the API routes. One senior reviewer.","tracker":"jira"}Example output
{"status":"ok","deliverable_type":"execution_plan","title":"Email + Password Auth — Execution Plan","summary":"Adds sign-up, login, 30-day sessions, and password reset. Sequenced data-model → sessions → API routes → email flows → UI; branches chain off the auth base so PRs don't bottleneck on main.","execution_plan_markdown":"| Task | Description | Files | Depends On | Branch (← Base) |\n|---|---|---|---|---|\n| T1 | Auth schema | `src/lib/schema.ts` | — | `feature/auth-schema` ← `main` |\n| T2 | Session helpers | `src/lib/auth/session.ts` | T1 | `feature/auth-session` ← `feature/auth-schema` |","tasks":[{"id":"T1","title":"Auth data model","description":"Add users, sessions, email_tokens tables via Drizzle migration.","files":["src/lib/schema.ts","drizzle/0001_auth.sql"],"depends_on":[],"branch":"feature/auth-schema","base_branch":"main"},{"id":"T2","title":"Session helpers","description":"Signed-cookie session create/verify/destroy, 30-day TTL.","files":["src/lib/auth/session.ts"],"depends_on":["T1"],"branch":"feature/auth-session","base_branch":"feature/auth-schema"}],"branch_strategy":{"summary":"Schema lands first on main; session work chains off the schema branch; routes chain off session. Each branch PRs against its base so reviews proceed in parallel.","branches":[{"name":"feature/auth-schema","base":"main","tasks":["T1"]},{"name":"feature/auth-session","base":"feature/auth-schema","tasks":["T2"]}]},"open_questions":["Verify-email-before-first-login, or allow login then nag?"],"requires_approval":true,"approval_note":"Approve this plan to unlock the Jira ticket drafts (re-run with approved=true); nothing is filed until you do.","confidence":"high"}