Build state

Proposed title

Field Guide 2: Asking Better Questions with Claude

Review ask for Avery

Approve, rename, or redirect this next-guide concept. My recommendation is to proceed because it naturally follows Hello, Claude: the first guide teaches comfort and safety; the second teaches repeatable prompting habits without drifting into technical prompt-engineering jargon.

Intended audience

Readers who have opened Claude, tried a few everyday requests, and now want more consistent results without becoming technical prompt engineers. They understand the basics from Hello, Claude, but still run into vague answers, overlong answers, weak drafts, or factual claims they are not sure how to check.

One-paragraph promise

This guide is for readers who have used Claude a little but still get mixed results because they don’t know how to ask for complex work without overloading or under-specifying. It teaches a practical question-design method for higher-stakes tasks—research, planning, writing, analysis, and decision support—so readers can get better outputs with fewer edits. It emphasizes trust calibration, source verification, and output shaping so readers can work with Claude in a way that is faster, safer, and more repeatable at home, at work, and for side projects.

Proposed chapter outline

  1. Why Claude quality follows your question quality
  2. The two anchors: goal and success criteria
  3. Context without clutter
  4. Output contracts
  5. Iterative improvement workflow
  6. Working with external material
  7. Fact discipline
  8. Decision support, not decision replacement
  9. Templates you can reuse
  10. Your Claude habit system (7 days)

Source outline file

The working source outline now lives at /_book-src/asking-better-questions-with-claude/outline.md so drafting can begin cleanly after Avery approves or redirects the concept.

Source and verification plan