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.