Skip to content
Back to skills

Project Manager

ASecurity

Plan sprints, milestones, roadmaps, risks, dependencies, and stakeholder updates for team delivery.

  • 157 stars
  • 0 votes
  • 0 copies
  • 20 views
  • Added May 27, 2026
data-aigo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add HybridAIOne/hybridclaw --skill project-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Manager?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hybridaione-project-manager/badge)](https://www.skillsdirectory.com/skills/hybridaione-project-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-manager
description: Plan sprints, milestones, roadmaps, risks, dependencies, and stakeholder updates for team delivery.
user-invocable: true
metadata:
  hybridclaw:
    category: productivity
    short_description: "Delivery plans and roadmaps."
    tags:
      - planning
      - management
      - enterprise
      - delivery
    related_skills:
      - notion
      - trello
---
# Project Management

Use this skill for delivery planning and team-facing coordination artifacts.

## Core Outputs

When the user does not specify a format, default to one of these:

- implementation plan
- milestone table
- risk register
- stakeholder update
- sprint plan
- dependency map

## Default Structure

For delivery planning, use:

1. Goal
2. Scope
3. Milestones
4. Risks and mitigations
5. Dependencies
6. Owners or recommended owners
7. Next 3 concrete actions

For status updates, use:

1. Overall status
2. What moved this period
3. Current blockers
4. Decisions needed
5. Next checkpoint

## Working Rules

- Treat estimates as assumptions, not promises.
- Name the biggest risks early.
- Sequence high-uncertainty work before polish work.
- Prefer smaller deliverable increments over large all-at-once plans.
- If dates are requested without capacity data, state the assumption clearly.
- When the user asks for something pasteable into a team tool, keep formatting plain and compact.

## Common Patterns

### Risk Register

Use a compact table or bullet list with:

- risk
- impact
- probability
- mitigation
- owner

### Sprint Plan

Break work into:

- sprint goal
- committed items
- stretch items
- dependencies
- explicit exit criteria

### Stakeholder Update

Keep it short and decision-oriented:

- objective
- current state
- what changed
- risk or ask
- next checkpoint

## Pitfalls

- Do not commit to deadlines without listing assumptions.
- Do not hide dependencies in prose.
- Do not confuse activity with progress; anchor on outcomes.
- Do not generate ceremony for its own sake when a lighter artifact will do.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.