project-manager

Design one feature's or one milestone's specification — interviews you for requirements/user stories in a GitHub Discussion, drafts FRs/NFRs, then loops producer/architect in the Discussion until architect signs off, ready for /project-manager:review. Optionally holds a stakeholder meeting with every persona in the spec before hand-off. Run this before a Project board or task issues exist — for task breakdown after the root plan is approved, use /project-manager:plan instead. Takes --milestone M<n> against a product:approved brief to spec exactly one milestone; if the request is a whole product rather than one feature, run /project-manager:product first instead of designing it all at once.

Not sure which project-manager skill applies? Describe your situation or ask a question in plain language and this recommends the exact next skill and command — product, design, review, plan, implement, validate, loop-plan-implement-validate, status, or stakeholder-meeting — with the reasoning behind it. Use whenever you're unsure where a plan/product stands or which command to run next; run `/project-manager:status <n>` yourself instead if you already know the issue number and just want the raw state.

Runs the swimlane execution phase of a project-manager plan — orchestrates worker and validator personas in parallel batches, via per-task branches created in dedicated worktrees, over ready tasks across swimlanes until all tasks reach Done, then hands each batch's push/PR integration and continuous trunk-merge off to a mergepush subagent so this session's own context stays free of git/gh command output and each task lands on main as soon as it's validated and safe to. Requires the Project board (from /project-manager:plan) to already exist.

Drives a plan:approved (or plan:agent-approved — see /project-manager:loop-design-panel) root plan all the way to a set of merged PRs unattended — dispatches /project-manager:plan, /project-manager:implement, and /project-manager:validate each to their own fresh subagent (which in turn dispatch planner/worker/validator/mergepush/system-validator themselves), looping implement→validate again whenever validate routes findings back to Implementation, until validate reports a clean merge. Finishes with an independent final-verification subagent that re-checks every task's PR from a branch/PR description handed to it, so this orchestrating session's own context never absorbs any phase's gh/git output, start to finish. Use for "run this plan end to end", "loop plan/implement/validate until done", or "get this whole plan merged without me babysitting each phase".

Scope a product before any feature spec exists — interviews you for vision, personas, and a capability map in a GitHub Discussion, has the architect record current state and the load-bearing decisions that later capabilities depend on, then breaks the product into milestones and publishes <domain>/PRODUCT.md plus a thin tracking Issue (product:approved). Run this first when a request is a whole product/app rather than one feature; each milestone is then specced with /project-manager:design <product-issue> --milestone M<n>. Also the right target for "scope this out", "what should v1 be", "break this into milestones", or when a design has ballooned past ~20 FRs.

The human review gate for a project-manager plan — reviews an architect-approved draft in a GitHub Discussion, then either approves it (triggering creation of the final root plan Issue labeled plan:approved) or routes feedback back through producer/architect in the Discussion. For an unattended run with no human reviewer, see /project-manager:loop-design-panel instead — it produces a plan:agent-approved Issue via the same gate mechanics.

Runs a stakeholder meeting round on a plan — dispatches one stakeholder persona per persona named in the specification, collects guidance, non-blocking feedback, and numbered blockers, and posts consolidated minutes. Blockers route the plan back through the producer/architect loop. Use after architect sign-off, or against an approved root plan issue.

Read-only status dashboard for a project-manager root plan or product brief — for a plan, its lifecycle state and a breakdown of Project items across swimlanes; for a product:approved brief, the milestone roadmap ledger. Use to check where a plan or product stands before deciding which orchestration skill to run next.

Runs whole-system validation for a project-manager plan — dispatches system-validator to exercise the merged result in Tilt against the root plan's acceptance criteria, then routes any findings to planner for follow-up tasks.