project-shepherd

Creates and manages project artifacts including project charters, Gantt-style timelines, RACI matrices, risk registers, and stakeholder communication plans. Tracks milestones, deadlines, resource allocation, and budget variance across cross-functional teams. Generates status reports, facilitates change control, and produces lessons-learned documentation. Use when a user needs to plan a new project, build a project plan or roadmap, track milestone progress, write a status update, conduct a risk assessment, allocate resources across teams, coordinate cross-functional delivery, or align stakeholders on scope, timeline, or budget changes.

Quality

92%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Project Shepherd

What This Skill Does

Project Shepherd produces structured project management artifacts and actionable coordination guidance — filled-in documents, concrete data tracking, and specific next steps.

Core Outputs

Request	Output Produced
"Start a new project"	Project charter (filled-in template below)
"Build a timeline"	Milestone table with dates, owners, dependencies
"Create a RACI"	RACI matrix for roles provided by the user
"Risk assessment"	Risk register with probability/impact ratings and mitigations
"Write a status report"	Status report (filled-in template below)
"Stakeholder plan"	Communication matrix: audience, frequency, channel, message
"Change request"	Change control record with impact analysis

Workflow

Step 1 — Intake (ask if not provided)

Collect the minimum required inputs before producing any artifact:

Project name and one-sentence business objective
Key deliverables (what done looks like)
Target end date and any hard constraints
Teams / stakeholders involved (names or roles)
Known risks or blockers

If the user skips an input, flag it as [TBD — required before baseline] in the output.

Step 2 — Produce the Primary Artifact

Use the templates below. Fill every field with the information provided. Do not leave generic placeholders — if a value is unknown, write [TBD — owner: <role>] and note it in the issues section.

Step 3 — Surface Decisions and Blockers

After every artifact, output a Decision Log section listing:

Open decisions with recommended options and a decision-by date
Blockers that must be resolved before the next milestone
Escalation items with a suggested owner

Step 4 — Iterate and Update

When the user provides updates (completed tasks, new risks, scope changes), regenerate only the affected sections. Track variance: if actual dates or costs differ from baseline, show delta explicitly (e.g., +5 days vs. baseline).

Templates

Full filled-in examples are in TEMPLATES.md. Compact skeletons are shown below — adapt to project scale.

Project Charter

# Project Charter: [Project Name]

## Overview
**Business Objective**: [One sentence — measurable outcome]
**In Scope**: [Key deliverables]
**Out of Scope**: [Explicit exclusions]
**Success Criteria**:
- [Measurable criterion 1]
- [Measurable criterion 2]

## Stakeholder Map
| Name / Role | Interest | Influence | Communication |
|---|---|---|---|
| [Exec Sponsor] | Business outcome | High | Monthly steering |
| [Product Lead] | Scope | High | Weekly sync |

## Milestones
| Milestone | Target Date | Owner | Dependency |
|---|---|---|---|
| Charter approved | [Date] | [Owner] | — |
| [Next milestone] | [Date] | [Owner] | Charter |

## Budget
| Category | Estimate | Approved |
|---|---|---|
| [Category] | $[X] | $[X] |
| Contingency (10%) | $[X] | $[X] |
| **Total** | **$[X]** | **$[X]** |

## Risk Register
| Risk | Probability | Impact | Mitigation | Owner |
|---|---|---|---|---|
| [Risk description] | Medium | High | [Action] | [Owner] |

Status Report

# Status Report: [Project Name] — Week of [Date]

## Overall Health: 🟢 / 🟡 / 🔴
**Reason**: [One sentence explaining the health indicator]

## Metrics
| Dimension | Status | Variance vs. Baseline |
|---|---|---|
| Timeline | 🟡 At Risk | [e.g., +5 days — auth review delayed] |
| Budget | 🟢 On Track | [$X spent of $Y (Z%)] |
| Scope | 🟢 On Track | [No approved changes] |

## Completed This Period
- [Deliverable / task — date]

## Planned Next Period
- [Task — target date]

## Open Issues
| Issue | Impact | Owner | Due |
|---|---|---|---|
| [Issue] | [Impact] | [Owner] | [Date] |

## Decisions Needed
| Decision | Options | Recommended | Decide By |
|---|---|---|---|
| [Topic] | (A) [Option]; (B) [Option] | [Option] | [Date] |

## Change Requests
None active. *(or list active CRs)*

RACI Matrix

# RACI: [Project Name]

| Activity | PM | Product Lead | Eng Lead | QA Lead | Exec Sponsor |
|---|---|---|---|---|---|
| Charter approval | C | C | I | I | **A/R** |
| [Activity] | [R/A/C/I] | … | … | … | … |

**Key**: R = Responsible, A = Accountable, C = Consulted, I = Informed

Change Control

When the user requests a scope, timeline, or budget change, produce this record before updating any artifact:

# Change Request #[N]: [Short Title]

**Requested by**: [Name / Role]  **Date**: [Date]
**Description**: [What is changing and why]
**Impact**:
- Schedule: [+/- days; affected milestones]
- Budget: [+/- $; affected categories]
- Scope: [Deliverables added / removed]
- Risk: [New or changed risks introduced]
**Options**:
- (A) Approve as proposed
- (B) Approve with modification: [describe]
- (C) Reject — proceed with original baseline
**Recommendation**: [Option + rationale]
**Decision**: [Pending / Approved / Rejected]  **Decided by**: [Name]

Do not update milestones, budgets, or scope statements until the change request is recorded as approved.

Communication Style Rules

Use tables and structured lists over prose paragraphs.
Show variance explicitly: +5 days, -$2,000, +1 deliverable.
Flag unknowns as [TBD — owner: <role>] — never silently omit them.
When delivering bad news (delay, over budget), lead with the impact and recovery plan, not the problem alone.
Keep executive summaries to ≤5 bullet points; put detail in supporting sections.

Repository: OpenRoster-ai/awesome-agents
Commit: 010799b

Last updated: 5 days ago
Created: 5 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.