Does this replace our project plan?
No. It covers the first week only, which is the part most teams improvise. Your longer delivery plan picks up from the milestone dates it sets.
Ops
Turn a signed deal into a first week that feels organized instead of improvised.
Follows the Agent Skills open format, works with Claude Code, Cursor, Hermes Agent, OpenClaw, and 30+ compatible agents.
What it does
This skill closes the gap between a signed contract and real work starting. It reads the deal context, the scope you sold, and your standard delivery motion, then produces a day-by-day plan for the first week, a kickoff email the client can act on, and an internal checklist with owners.
The first week sets the tone for the whole engagement, and it is usually where agencies lose trust: access requests trickle in, the kickoff call has no agenda, and the client wonders what they bought. This pack front-loads the asks, sequences them, and names what you need before each milestone.
It is deliberately opinionated about what happens when the client goes quiet. Every runbook includes a chase schedule and a clear line for what slips if access does not arrive on time.
Who it is for
Requirements
Signed scope
What you sold, the deliverables, and the agreed start date
Deal notes
Discovery context, stakeholders, and anything promised on the call
Access list
Optional. The accounts and tools you need before work can start.
Task tracker
Optional. Useful for loading the internal checklist with owners and dates.
Sample output
Client: Copper & Vine (regional wine retailer) Scope sold: Paid search rebuild plus monthly reporting Kickoff call: Thursday Day 1 - Send kickoff email with access list and the pre-call questionnaire. Day 2 - Internal: pull baseline metrics, draft the account audit outline. Day 3 - Chase any missing access. Confirm the decision-maker attending Thursday. Day 4 - Kickoff call. Agenda: goals, current spend, approval path, reporting cadence. Day 5 - Send the recap with agreed scope, first milestone date, and open items. Access needed by Day 3: ad account admin, analytics read access, product feed. If access is late: the audit slips a week. Say this in the Day 3 chase, not on Day 10. Internal owners: Account lead (client comms), Analyst (baseline pull), Strategist (audit).
What's in this pack
Included: Outcome definition
What exact job this pack solves
Included: Operating instructions
Step-by-step workflow the agent follows
Included: Input contract
Required and optional fields defined as a schema
Included: Output contract
Exact output structure the agent must return
Included: Worked examples(6 files)
3 standard, 1 ambiguous, 1 bad-fit, and 1 edge-case scenario
Test & eval set
FAQ
No. It covers the first week only, which is the part most teams improvise. Your longer delivery plan picks up from the milestone dates it sets.
Yes, because the runbook is populated with this client's scope, stakeholders, and promises from the call. The structure is repeatable, the content is not.
The runbook includes a chase schedule and states which milestone slips. That gives you a specific thing to say on day three instead of a difficult conversation on day fifteen.
Bundle option
This pack is also included in Agency Revenue Pack, which groups related workflows for a faster setup.
View bundleRelated packs
Ops
Turn a messy process walkthrough into a step-by-step SOP your team or agent can run.
Test cases with expected outputs and pass/fail criteria
Included: QA checklist
Human review checklist for output quality
Sales
Convert messy notes or transcripts into a client-ready proposal draft with scope, assumptions, and next steps.
Support
Classify support tickets, flag urgency, draft the next action, and reduce queue chaos for lean teams.