claude

project-manager

Multi-persona, GitHub-tracked project management pipeline (producer/architect/planner/workers/system-validator)

1 on GitHubby whale_netupdated 1 month ago
/

Plugin project-manager from marketplace everything-marketplace in whale-net/everything. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (11)

  • design

    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 ever

  • help

    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 behin

  • implement

    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

  • loop-design-panel

    Drives 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-validate

    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 plan

  • plan

    Task 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.

  • product

    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>/P

  • review

    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

  • stakeholder-meeting

    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 archite

  • status

    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

  • validate

    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.

Subagents (11)

  • architect

    Architecture persona — reviews the producer's draft plan inside a GitHub Discussion, reconciles it against this repo's conventions and design strategies, asks questions via Discussion comments until only nitpicks remain, then signs off for human review. Use after producer posts or updates a draft pl

  • help

    Help/triage persona — reads a free-form question about the project-manager pipeline and recommends the exact next skill and command to run, grounded in CONVENTIONS.md and (when a plan/product is named) its actual GitHub state. Use when a user isn't sure which project-manager skill applies to their s

  • mergepush

    Push/PR integration worker — takes a batch of task branches that worker/validator subagents already committed to (worktree already created by the orchestrator) and, one at a time, pushes each task's branch to origin as-is, opens or refreshes its own plain PR based on its real `Depends on:` parent —

  • planner

    Planning persona — converts an approved root-plan issue into a GitHub Project with swimlanes (Scaffold → Implementation → Testing → Validation → Done), creates cohesive task issues that progress through swimlanes, converts system-validator findings into follow-up tasks, and triages scope notes. Use

  • producer

    Product persona — interviews the requester to gather requirements and user stories in a GitHub Discussion, drafts the specification, responds to architect reconciliation and human feedback in the Discussion, and publishes the final approved root plan Issue. Use to kick off a new plan (including from

  • project-manager

    Lightweight project-management persona for quick task breakdowns, cross-domain dependencies, and doc upkeep (TOC/ARCHITECTURE/README/ENV) on small-to-medium requests. For a full feature that should go through producer → architect → planner → GitHub-tracked worker execution, use those personas instea

  • reviewer

    Agent reviewer persona — stands in for the human review gate when a plan runs through /project-manager:loop-design-panel unattended. Breaks a standing stakeholder disagreement once the meeting's own round cap is hit, and renders the Approve / Request changes call that /project-manager:review would o

  • stakeholder

    Stakeholder persona — role-plays exactly one persona named in a plan's specification, reviews the draft from that persona's point of view inside the GitHub Discussion (or root plan Issue), and posts guidance, non-blocking feedback, and numbered blocker issues. Use once per persona during a stakehold

  • system-validator

    Whole-system validation persona — runs the merged result end-to-end in the local Tilt environment and grades it against a root plan's acceptance criteria, writing up findings as follow-up planner tickets. Use once every task issue on a root plan's Project is Done, before considering the plan complet

  • validator

    Validation worker — picks up one ready task issue from a plan's Project in the Validation swimlane, checks its acceptance criteria against code and tests (read-only), moves it to Done and closes the issue, or routes it back to Implementation on failure. Use to execute a single task issue whose Proje

  • worker

    Execution worker — picks up one ready task issue from a plan's Project in Scaffold, Implementation, or Testing swimlane, executes that phase's work inside a dedicated worktree, commits to the task's own branch, and advances the task to the next swimlane. Use to execute a single task issue whose Proj

View source on GitHub

More from whale-net/everything

All 9 plugins →

Work-axis krill plugin: MCP access to krill's spec surface plus the milestone/delivery-axis tools and create_task, plus planner/worker/validator/system-validator/mergepush personas and plan/implement/validate skills forked from project-manager

5 skills · 7 agents · 6 MCP servers

1

Design-axis krill plugin: MCP access to krill's spec, design-session, and milestone/delivery-axis surfaces, plus producer/architect/reviewer/stakeholder personas and design/product/review skills forked from project-manager

5 skills · 5 agents · 6 MCP servers

1

Streamable-HTTP MCP access to the Audience Score System server across dev/prod, plus researcher/analyst agents and loop skills for research, schedule, and outcomes

3 skills · 2 agents · 2 MCP servers

1

Streamable-HTTP MCP access to whagent-net's Agent API (start_session/send_turn/stop_session/get_session/read_transcript) across tilt/dev/prod

3 MCP servers

1

Postgres MCP access (crystaldba postgres-mcp) to the App Registry database across tilt/dev/prod

1

Postgres MCP access (crystaldba postgres-mcp) to the Audience Score System database across tilt/dev/prod

1

Maintain project-manager?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins9 plugins