learn
Learn from this session. Extract what went well, what went wrong, and update documentation so future sessions are better. Also give direct feedback on how the user can work with Claude more efficiently.
Instructions
Parse $ARGUMENTS for optional focus area (e.g., mistakes, efficiency, workflow). If empty, do a full review.
Step 0: Efficiency Audit (Elon's 5-Step Framework)
Before anything else, audit the work done in this session against each step in order:
1. Make requirements less dumb
- Were any requirements stated as facts that were actually assumptions? Who said this had to be done this way?
- Did requirements come from someone who isn't going to be accountable for the outcome?
- Flag any requirement that, in hindsight, was dumb, wrong, or unnecessary.
2. Delete the part/process
- What steps, outputs, or artifacts could have been eliminated entirely without losing value?
- Was anything produced that won't be used? Any process run "because we always do"?
- If you can't defend why something stayed, it should have been cut.
More from kristenschumann/claude-skills
time-audit
Weekly personal time audit using macOS Screen Time and Chrome history, outputs an HTML visualization
2executive-critique
Executive critique with two modes: operational (Nick's lens — execution, timelines, dependencies) and strategic (John's lens — ROI, ambition, customer psychology)
2scope
Declares EXPAND/HOLD/REDUCE mode before planning sessions, monitors for scope drift, and maintains a parked ideas list
1kpi-bot
Builds a daily Slack KPI bot: takes any metric + SQL query, creates an n8n workflow that posts daily updates to a Slack channel
1