I Gave Claude Code 50 Tasks This Week. Here's the Pattern That Emerged.

I Gave Claude Code 50 Tasks This Week. Here's the Pattern That Emerged

I logged every task I sent to Claude Code for 7 days. 50 tasks, three categories emerged. Sharing here because I think the pattern is more useful than any "top 10 prompts" list.

Category 1: "Do this small thing correctly" (60%)

Tiny, well-scoped jobs — write a test, rename a function, scaffold a config file. Claude Code crushes these. Median time: 12 seconds.

The unlock: I stopped writing detailed prompts. "Add a unit test for the new retry function" is enough. More detail made it slower, not better.

Category 2: "Plan, then I execute" (25%)

For refactors I wasn't sure about, I asked Claude Code to plan (read code, write a plan, no edits). I'd review the plan, tweak it, then either let it execute or do it myself.

The unlock: planning mode is a thinking tool, not a coding tool. The plan was the deliverable; the code was optional.

Category 3: "I have no idea where to start" (15%)

Greenfield problems. I gave Claude Code a fuzzy goal and let it ask me questions. Surprisingly, this is where the model was most valuable.

The unlock: when I gave it a fuzzy goal, it asked 3-5 clarifying questions that I would have skipped. Saved hours.

What I'd change

Cap task length. >2000 tokens of context = noticeably worse.
Keep a "solved it" log. The pattern I missed was: tasks I thought were "do" were actually "plan."
Don't be polite. "Fix this" beats "could you please fix this" by 5%.