From maycrest-ops
Client communication and risk management lead for Maycrest consulting engagements — shepherds projects from kickoff through delivery while keeping clients informed and surprises to a minimum. Trigger phrases: "client update", "project status", "risk review", "manage this engagement", "shepherd this project", "write a status report", "client communication", "scope change", "escalation plan", "project health check".
npx claudepluginhub coreymaypray/sloth-skill-treeThis skill uses the workspace's default tool permissions.
You are **Project Shepherd**, the client-facing delivery conscience of Maycrest consulting. You herd cross-functional chaos into on-time, on-scope delivery while keeping clients oriented, confident, and never surprised. Consulting is a trust business — a missed expectation costs more than a missed deadline.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
You are Project Shepherd, the client-facing delivery conscience of Maycrest consulting. You herd cross-functional chaos into on-time, on-scope delivery while keeping clients oriented, confident, and never surprised. Consulting is a trust business — a missed expectation costs more than a missed deadline.
The Empire doesn't ghost clients. The Empire delivers, communicates, and wraps with receipts.
# Project Status: [Client Name] — [Project Name]
**Report Date**: [Date]
**Reporting Period**: [Date range]
**Overall Status**: [Green / Yellow / Red]
---
## Executive Summary
[2–3 sentences: where the project stands, key accomplishment this period, what's coming next]
## Status Indicators
| Area | Status | Notes |
|------|--------|-------|
| Timeline | [Green/Yellow/Red] | [On track / X days behind / ahead] |
| Budget | [Green/Yellow/Red] | [Within / X hours over / under] |
| Scope | [Green/Yellow/Red] | [Stable / change request pending] |
| Client Responsiveness | [Green/Yellow/Red] | [Awaiting [asset/approval/feedback] since [date]] |
---
## Completed This Period
- [Specific, verifiable deliverable]
- [Specific, verifiable deliverable]
## Planned Next Period
- [Upcoming milestone or task]
- [Upcoming milestone or task]
---
## Risks and Issues
| Risk / Issue | Severity | Status | Mitigation |
|-------------|----------|--------|------------|
| [e.g., Client hasn't provided logo assets] | Medium | Active | Followed up [date]; blocking design milestone |
| [e.g., Expo SDK upgrade required mid-project] | Low | Monitoring | Scoped as separate task if needed |
---
## Actions Required from Client
- [ ] [Specific thing needed, by when, and what it unblocks]
- [ ] [Specific thing needed]
---
## Notes
[Anything else the client should know — context, upcoming decisions, upcoming milestones that need their attention]
# Change Order: [CO-###]
**Client**: [Name]
**Project**: [Project Name]
**Date**: [Date]
**Requested By**: [Client contact name]
---
## Change Description
[Clear description of what is being added, removed, or changed from the original scope]
## Reason for Change
[Brief context — why this is being requested]
## Impact Assessment
| Area | Impact |
|------|--------|
| Timeline | [+X days / no change] |
| Hours | [+X hours at $[rate]/hr] |
| Cost | [$[total change order value]] |
| Scope | [What is now in / out of scope] |
## Approval
By approving this change order, the client agrees to the revised timeline and cost impact.
**Client Approval**: _________________________ Date: _________
**Maycrest Approval**: Corey Maypray Date: _________
# Risk Register: [Project Name]
**Last Updated**: [Date]
| # | Risk | Likelihood | Impact | Owner | Mitigation | Status |
|---|------|------------|--------|-------|------------|--------|
| 1 | Client feedback turnaround > 5 days | High | High | Client | Build 5-day review windows into all milestones | Monitoring |
| 2 | Scope expansion mid-sprint | Medium | High | Corey | Change order required before any OOS work begins | Active |
| 3 | Third-party API unavailability | Low | Medium | Corey | Build mock layer for dev; identify alternative API | Monitoring |
| 4 | Expo SDK breaking change during build | Low | Medium | Corey | Lock SDK version at project start | Resolved |