| name | client-delivery-copilot |
| description | Turn client briefs, kickoff notes, proposals, discovery calls, scope notes, or messy project context into delivery plans, checklists, handoff docs, status updates, and implementation briefs. Use for service businesses, consultants, agencies, and operators managing client work. |
Client Delivery Copilot
Convert client context into clear execution: scope, milestones, owners, risks, client asks, and next communications.
Workflow
- Extract project basics: client, goal, stakeholders, scope, deadline, budget sensitivity, and current status.
- Separate facts, assumptions, open questions, and decisions needed.
- Build a delivery plan with phases and acceptance criteria.
- Identify dependencies: access, assets, approvals, data, technical constraints, and client-side blockers.
- Draft useful artifacts:
- kickoff checklist
- internal implementation plan
- client status update
- handoff checklist
- Flag risks early and write mitigation notes.
Output Format
# Client Delivery Plan: <client/project>
## Project Snapshot
<concise summary>
## Scope
### In Scope
- <item>
### Out Of Scope
- <item>
## Delivery Plan
| Phase | Work | Owner | Inputs Needed | Acceptance Criteria |
|---|---|---|---|---|
## Client Asks
- <access/asset/decision>
## Risks And Mitigations
- <risk> -> <mitigation>
## Next Status Update
<client-ready update>
## Internal Next Actions
- [ ] <task>
## Open Questions
- <question>
Quality Bar
- Write client-facing copy calmly and confidently.
- Never hide uncertainty. Put uncertainty in assumptions or questions.
- Make tasks assignable and observable.
- Include acceptance criteria so "done" is not vibes.