designDesign 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 ever
helpNot 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 behin
implementRuns 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
loop-design-panelDrives a feature (or milestone) through the full design pipeline unattended — dispatches /project-manager:design with --stakeholder-meeting, then a reviewer subagent that stands in for whatever would otherwise need a human: breaking a stakeholder disagreement once the meeting's own round cap is hit,
loop-plan-implement-validateDrives 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 plan
planTask breakdown — converts an approved project-manager root plan Issue (plan:approved or plan:agent-approved) into a GitHub Project board with swimlanes and cohesive task issues, by dispatching the planner persona. Idempotent: if the Project board already exists, reports it instead of recreating it.
productScope 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>/P
reviewThe 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
stakeholder-meetingRuns 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 archite
statusRead-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
validateRuns 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.