pm-manager_skill

This skill helps you manage projects and schedules by coordinating milestones, resources, risks, and progress across agile and kanban workflows.
  • Makefile

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shaul1991/shaul-agents-plugin --skill pm-manager

  • SKILL.md2.1 KB

Overview

This skill is a PM Manager Agent that handles project planning, scheduling, resource allocation, and risk monitoring. I coordinate milestones, create work breakdowns, and keep progress visible with standups, reviews, and burndown-style tracking. The goal is to keep projects on schedule, balance team load, and surface risks early.

How this skill works

I inspect project scope and deadlines, then define milestones and break work into tasks with dependencies. I allocate team members by skills, propose load balancing, and produce schedule artifacts such as Gantt-like timelines and milestone trackers. I also run progress routines: daily standups, weekly reviews, and retrospectives, and flag risks with impact and response plans.

When to use it

  • Starting a new project or sprint planning session
  • Rebalancing work when team load or priorities change
  • When tracking milestone slippage or schedule risk
  • Preparing sprint reviews, retrospectives, or stakeholder updates
  • Onboarding new team members into project tasks

Best practices

  • Define clear, time-boxed milestones and publish a simple milestone tracker
  • Break features into a WBS with explicit dependencies to surface sequencing risks
  • Match tasks to team members by demonstrated skills, and rotate work to avoid burnout
  • Keep daily standups time-boxed and focused on blockers and commitments
  • Document schedules and meeting notes in consistent locations (e.g., docs/plans and docs/meetings)

Example use cases

  • Create a sprint plan: define sprint goals, WBS, and sprint backlog with task estimates
  • Resource rebalance: reassign tasks when a key engineer is overloaded or unavailable
  • Risk assessment: identify top 3 project risks, score impact/likelihood, and propose mitigation steps
  • Progress reporting: produce a weekly status with burndown-style summary and milestone updates
  • Run a retrospective: collect keep/problem/try items and convert action items into tracked tasks

FAQ

I produce a milestone tracker, text-based Gantt timeline, task list with dependencies, meeting notes, and risk register.

How do you handle task dependencies?

I model dependencies in the WBS and reflect them in the schedule; I recommend sequencing and buffer time for critical path tasks.

Where should I store schedules and meeting notes?

Store schedules in docs/plans/[project]-schedule.md and meetings in docs/meetings/YYYY-MM-DD.md to keep records consistent.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
pm-manager skill by shaul1991/shaul-agents-plugin | VeilStrat