Fable 5 leaves the Claude subscription plans tomorrow night (11:59pm PT on July 7, then it’s API-only at $10/M in, $50/M out). I have roughly 10% of my weekly limit left and I’m trying to spend it deliberately. I’ve been vibe coding with Claude Code for about 10 months and my setup shows it: CLAUDE.md files that grew past their purpose, skills I wrote and forgot, instructions I apparently love retyping by hand every single session. Fast agents let you outrun your own architecture. I’m not building anything new tonight. I’m having it hand over everything it learned about how I work. Run 1: harness archaeology Go through all my Claude history: conversations, docs, projects, skills, and workflows. Answer five questions: 1. What do I actually use you for most? (not what I think I use you for) 2. Which tasks do I repeat that were never turned into anything reusable? 3. Which instructions do I keep rewriting by hand, session after session? 4. Which workflows deserve to become permanent skills? 5. Where was my approach simply wrong? Point at things you watched me do that I should stop doing. Then convert every answer into artifacts: skills, usage guides, workflow templates. Everything worth keeping should survive as a file, not a memory. Run 2: agent-native audit My app gets more user bug reports than I can personally walk through a chat window, so this run reviews the architecture with one goal: an agent should be able to pick up a bug report, reproduce it, fix it, and verify it on a real build with me barely in the loop. Act as a principal architect reviewing this codebase with a single goal: make it agent-native. Definition: coding agents should be able to pick up a user bug report or a roadmap feature, then reproduce, implement, test, and verify it on a real build with minimal human input. Audit four things: 1. Human-judgment chokepoints: every place where a change currently requires my personal judgment or tribal knowledge. Which of these could become written conventions, decision tables, or CLAUDE.md rules an agent can follow on its own? 2. Verification gaps: for each core subsystem, what is missing for an agent to verify its own change end-to-end? (behavior tests, live probes, mock event injection, log assertions, screenshot diffs) 3. Reproduction paths: given a typical user bug report (text plus diagnostic bundle), what would an agent need to reproduce it autonomously? What fixtures or replay harnesses are missing? 4. Structural obstacles: modules too entangled for an agent to change safely without reading the whole repo. Propose boundaries. Deliverable: a prioritized plan ranked by human-attention-saved per unit of effort. The top 5 items must be specified concretely enough that an agent could start each one from this document alone. But I might be spending my last tokens wrong. If you had one deliberate run left before the cutoff, what would you spend it on? Looking for the thing I’ll still be using three months from now, after the model itself is gone. submitted by /u/imedwardluo
Originally posted by u/imedwardluo on r/ClaudeCode