Close Deadline Commander
A close calendar that actually drives behavior
A close orchestration workflow that translates the close calendar into daily priorities, owners, dependencies, and escalation actions. One status view for leadership instead of a dozen "where are we?" Slack messages.
INGREDIENTS
PROMPT
Create a skill called "Close Deadline Commander". It should: - Create a close plan with tasks, due dates, owners, dependencies, and definition of done - Send a daily close briefing with priorities, blockers, and next actions - Maintain a single close dashboard - Escalate overdue or blocked tasks based on a defined responsibility chain - Produce a close retrospective after completion Ask me for our target close timeline and recurring close tasks before building the plan.
How It Works
Close work becomes chaotic when tasks are tribal knowledge and dependencies are unclear.
This recipe coordinates the close with explicit ownership, dependencies, and daily briefing output.
What You Get
- Daily close briefing with priorities, blockers, and next actions
- Single close dashboard with status by task and owner
- Escalation messages for overdue or blocked work
- Close retrospective after completion
Setup Steps
- Build the close plan with tasks, owners, dependencies, and due dates
- Define definition-of-done for each close task
- Send a daily briefing every close morning
- Escalate blocked and overdue items based on policy
- Generate a retrospective when close is finished
Tips
- Keep the definition of done explicit for every task
- Make dependencies visible so blockers surface early
- Review retrospectives to shrink the next close cycle