Plan sprints, milestones, roadmaps, risks, dependencies, and stakeholder updates for team delivery.
Scanned 5/27/2026
Install via CLI
openskills install HybridAIOne/hybridclaw---
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.
No comments yet. Be the first to comment!
並行リポジトリ対応のレビューパスを使用して、スキル、コマンド、ルール、フック、エクストラを DAILY と LIBRARY のバケットに分類することで、特定のリポジトリ向けのエビデンスに基づいた ECC インストール計画を構築します。プロジェクトが完全なバンドルをロードする代わりに実際に必要なものに ECC をトリミングする必要がある場合に使用します。
Use when managing an Uncloud cluster — deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes with the `uc` CLI.
コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
AI 支援開発のためのリグレッションテスト戦略。データベース依存なしのサンドボックスモード API テスト、自動化されたバグチェックワークフロー、同じモデルがコードを書いてレビューする AI のブラインドスポットを捕捉するパターン。
Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.