Evening Routine: Evening Close SKILL.md
end of day close skill
Chapter VII
Cards marked with a teaser are in the Vault. Unlock everything — $97, one time.
end of day close skill
end of day workday close
evening close pattern review
define the one job + what done looks like
find the execution bottleneck
pre-flight before shipping
automate only what survives subtraction
find tasks to delete entirely
lower frequency/fidelity, see what survives
a living connected knowledge base
cut the noise from your AI info sources
one weekly summary replaces the firehose
audit tools against actual workflows
5 questions before chasing anything new
set up your projects/areas context files
close out the week cleanly
compress errands to cut decisions
scripts to protect the weekend
audit hidden weekend sub-decisions
design real active recovery
design an analog commitment
autopsy past goal failures
weekly integration review
build an integrated life+business 12-week sprint
escape recurring fire-fighting
Prompt 4: The Fire-Fighting Escape Designer Architecture: Structuralist | Format: XML Use this when you suspect you’re trapped in crisis mode but can’t see the exit. <role> You are an organizational health consultant specializing in escaping the fire-fighting trap. </role> <context> I think my team is stuck in reactive mode. Recent crises: [LIST 3-5] How we typically respond: [DESCRIBE PATTERN] What happens when things calm down: [DESCRIBE] Time ratio (prevention vs. reaction): [ESTIMATE] </context> <task> Diagnose whether we're in a fire-fighting trap and design a specific escape path. </task> <methodology> 1. Identify the fire-fighting loop structure 2. Find what prevents root cause work even during calm periods 3. Surface the "success trap" (how fire-fighting gets rewarded) 4. Design interventions that don't require crisis to end first </methodology> <output_format> ## Diagnosis ### The Loop You're In [Crisis] → [Response] → [Temporary stability] → [Why stability leads to next crisis] ### Why Prevention Doesn't Happen During crisis: [Barrier] After crisis: [Barrier] ### The Success Trap [How current incentives reward fire-fighting over prevention] ## Escape Path ### This Week (no permission needed) - [Specific action] ### This Month (requires protected time) - [Specific action] - [How to protect it from being consumed by fires] ### Metrics to Track Instead Replace: [Fire-fighting metrics like response time] With: [Prevention metrics like fire frequency, severity trend] </output_format>
causal chains + missed feedback loops
validate a feedback loop
rank leverage points
expand the system boundary
fragmentation score + shadow systems
domain-authority map + minimal tools
implement + optimize the system
decisions + rationale + dissent over time
pre-mortem meeting decisions
turn archives into searchable assets
surface tribal knowledge + implicit criteria
team dynamics + influence patterns
AARs from project meeting history
decide ship or kill for each loop
Prompt 2: Ship or Kill
Pattern: Forced-choice sorting with built-in constraints
This prompt eliminates “maybe later” as an option. Every project gets sorted into a category that closes the loop.
You are a ruthless portfolio manager for my time and energy. Your job is to force binary decisions on every open project. You are allergic to "maybe later." You believe most ideas should die so the few that matter can thrive.
Sort each item from my inventory into exactly one category. No exceptions. No "thinking about it more."
MY OPEN LOOPS:
[Paste full list from Prompt 1]
---
SORTING RULES
EXECUTE (Hard limit: 3 items)
- 90-day path to done exists
- I would feel genuine loss if this never happened
- Creates real value: money, audience, career leverage, or compounding skill
KILL (Default category when uncertain)
- Over 12 months old with no real progress
- Original reason no longer applies
- Someone else already does this better
- I wanted to want this more than I actually wanted it
TRANSFORM (Use only when obvious)
- Idea is right, execution model is wrong
- Can become a component of an EXECUTE item instead of standalone
ARCHIVE (Not a hiding place)
- Genuinely good, but missing a specific resource
- I can name the exact trigger that would reactivate it
- I am releasing it from active memory with a retrieval condition
---
OUTPUT FORMAT
For each item, give me:
[Item name]
Category: [EXECUTE / KILL / TRANSFORM / ARCHIVE]
Reason: [One sentence]
Closure action:
- If EXECUTE: Minimum viable version that counts as "done"
- If KILL: Permission statement ("I am choosing not to pursue this because...")
- If TRANSFORM: What it becomes and which EXECUTE project absorbs it
- If ARCHIVE: Specific trigger that would move it to EXECUTE
---
CONSTRAINTS
- If I have more than 3 EXECUTE items, force me to cut
- If ARCHIVE has more than 3 items, challenge whether I am using it to avoid hard decisions
- Default to KILL when genuinely uncertainkill a project gracefully
Prompt 4: The Goodbye Pattern: Structured post-mortem with emotional closure Killing a project is harder than it should be. This prompt turns abandonment into a completed transaction. You are an executive coach who specializes in helping high performers let go of projects without shame. You know that killing a project well is a skill, and that unprocessed endings create cognitive debt. Your job is to help me extract real value, conduct an honest autopsy, and close this loop permanently. I am closing this project permanently. Help me do it properly so my brain stops circling back. PROJECT: [Name] STARTED: [When] WHY I STARTED: [Original motivation] TIME INVESTED: [Rough estimate] WHERE IT DIED: [What stage and what happened] WHY THIS IS HARD: [What makes letting go difficult] --- CLOSE THE LOOP 1. WHAT I GOT FROM THIS List only real value. No invented silver linings. Consider: - Skills I developed or sharpened - Knowledge I would not otherwise have - Clarity about what I do or do not want - Relationships or connections made - Assets I can repurpose elsewhere 2. WHY IT ACTUALLY DIED Go past the surface reason. Which of these is true? - The idea was flawed from the start - The execution model did not fit my real life - I wanted the identity more than the work - I was chasing external validation - Circumstances changed and I did not adapt - I was never willing to pay the real cost Pick the truest answer. No judgment, just accuracy. 3. THE RELEASE STATEMENT Write 3 sentences I can say out loud: - Sentence 1: What I am letting go and why - Sentence 2: What I learned or gained - Sentence 3: Where I am redirecting that energy 4. FUTURE FILTER Based on why this died, complete this sentence: "Before I commit to a project like this again, I will require _______________." 5. ARCHIVE NOTE Write a 2-3 sentence summary to file with any salvageable materials. If future-me considers resurrecting this, what should they know? --- When you finish, I should feel like this is a closed chapter, not an open wound.
hour-by-hour finish a project
park a project deliberately
dump + analyze where projects die
time-boxed strategic agenda
stakeholder map + hidden dynamics
capture decisions + follow-ups
salvage a derailing meeting
anticipate objections
yearly goals → 12-week targets
quarterly goals → weekly deliverables
sustainable operating cadence
match ambition to real resources
track leading indicators
plan contingencies in advance
adjust at week 6
the review habit that compounds
extract lessons + launch next sprint
invest reclaimed time deliberately
find the 20% that drives results
protect reclaimed time
a weekly time-investment plan
compound reclaimed time over 90 days
extract what worked from 12 months
stated vs revealed priorities
resolve postponed decisions
insights → calendar-ready action
clear mental clutter before strategy
actual vs perceived time use
Prompt 1: Time reality audit - expose where your hours actually go THE PURPOSE : Here’s something most people don’t want to admit: they have no idea where their time actually goes. They underestimate how long routine tasks take. They overestimate time spent on strategic work. This gap between perceived and actual time allocation is like living in a different reference frame than reality. You can’t compress time you haven’t measured. This prompt forces an honest accounting, because the first step to changing anything is seeing it clearly. Copy and customize this prompt: I need to understand where my work hours actually go versus where I think they go. My work context: - Role: [Your job title and primary responsibilities] - Typical week structure: [Remote/hybrid/office, meeting culture, deadlines] - Hours I aim to work weekly: [Target number] Here’s everything I did last week (be brutally honest): - Meetings attended: [List with approximate durations] - Communication time: [Email, Slack, calls - estimate hours] - Deep work sessions: [What you worked on, how long] - Administrative tasks: [Reports, scheduling, expenses, etc.] - Reactive work: [Interruptions, urgent requests, firefighting] Analyze my time allocation: 1. ACTUAL TIME BREAKDOWN Calculate the percentage of my week spent on: - Strategic/high-value work (directly advances goals) - Necessary operational work (keeps things running) - Low-value busywork (could be eliminated or compressed) - Reactive/unplanned work (responding to others’ priorities) 2. PERCEPTION GAP ANALYSIS Compare my stated priorities to my actual time investment. Where is the largest disconnect between what I say matters and what I actually spend time on? 3. TIME COMPRESSION OPPORTUNITIES Identify the top 5 time sinks that could be reduced by 50% or more using AI or systems. For each: current time spent, compression potential, specific approach. 4. WEEKLY TIME BUDGET Create a realistic time budget that allocates hours to categories based on actual importance, not habit. Output as a clear report showing where time goes now versus where it should go.
find highest time-savings tasks
run work simultaneously, not sequentially
create once, deploy infinitely
cut deliberation on recurring choices
a personalized tidying method
design a workspace renewal
optimize space for focus
reduce decisions in your environment
build a digital inventory system
rank tasks by revenue impact
prioritize what to delegate
eliminate low-value tasks
align peak energy with revenue work
audit your Monday energy
architect the week
prep Sunday for a strong Monday
map your engagement patterns
map your energy for blocking
batch similar tasks
eliminate context switches
design weekly time blocks
map energy across multiple income streams
reduce costly context switching
prioritize by income impact
find overlaps that serve multiple goals
design a sustainable weekly structure
first draft of a document via a 'successful future' template
reverse-engineer steps from a completed goal
automatic self-maintaining household/admin system
14-day accelerated learning plan
executive briefing on any topic in 30 minutes
find the 20% of tasks driving 80% of results
redesign a team workflow with AI replacing steps
master a concept via simple-explanation + analogies
close Monday by logging wins
neutralize anticipatory Sunday anxiety
quick wins + deep-work blocks for Monday
match tasks to energy windows + rituals
get ahead of Monday communications
AI Process Playbook (workflows, decision trees)
design irreversible Q4 pre-commitments
public-accountability system + exact post
consistency automation chains (AI/Zapier/Make)
design habits that survive low willpower
lower friction to start the right behavior
engineer the environment so good choices are easy
chain habits to compound momentum
honest review that course-corrects
a 12-week execution system
rank tasks by automation ROI → action plan
response templates that keep your voice
AI decision-support frameworks for recurring choices
day-by-day automation adoption plan
pre/during/post meeting automation stack
sustainable email triage + folder system
15-min weekly review + 5-min daily maintenance
CRITICAL/IMPORTANT/USEFUL/NOISE → today's 3
interview-first → custom organizing system
chaotic to-do list → time-blocked focused plan
tackle the hardest avoided task first
time-blocked schedule matched to energy
combine two productivity methods into one custom system (Level-Up)
match top-3 of 12 systems to your brain + 7-day trial
6 tasks, single-tasking plan + distraction defense
find the 20% of activities driving 80% of results
process mental clutter into GTD lists
categorize tasks into 4 quadrants + action plan
redesign a workflow for 40%+ gains + $ impact + 30-day plan
rank by impact + what NOT to do this week
if-then statements + pre-task ritual (CoT)
5 micro-tasks + 5-min MVP to build momentum
daily check-in + weekly review + metrics
challenge negative thoughts; AI critiques itself
find triggers + early-warning system (few-shot)
full fill-in ideal-week system
deep-work protection + meeting batching
protect creative-surge periods + recovery
family-variable schedule + protected self-care
interview-first weekly blueprint matched to energy
transform actual schedule into ideal
find energy-activity mismatches in a schedule
variation — 'I don't have enough control over my schedule for this to work.' Use this prompt variation: 'Create an
retrieval-first org system built around your access patterns
hierarchy + naming + index + renewal calendar + backup
standardized structures, role access, compliance checkpoints
cross-platform tagging + master dashboard + future-me protocol
adds [IMPLEMENTATION] — 'I start organizing but never finish the project.' This system is designed for incremental implementation. Add this parameter:
full fill-in mental-load management system
AI delegation for high-performer cognitive overhead
family logistics offloading + shared system
offload non-creative maintenance to preserve bandwidth
map cognitive overhead → AI offloading protocols
4-week trust-building AI delegation program
surface unconscious mental loops from a day description
variation — 'My mental load is necessary—these are things I need to keep track of.' Use this prompt modification: 'Design
write OKF concept files
answer what did we decide and why
make notes AI-readable (OKF)