fathom-cli 0.1.4 → 0.1.7

package/README.md

@@ -52,6 +52,7 @@ fathom velocity --project myapp
 | `fathom status` | Project overview with tracking data |
 | `fathom pricing` | Show current model pricing |
 | `fathom setup` | Scaffold `.claude/` skill + hooks + registry |
+| `fathom rename <name>` | Rename project across all config files |
 | `fathom validate <spec>` | Validate spec file format |
 | `fathom init` | Initialize global config |
 
@@ -70,12 +71,16 @@ fathom estimate "Build a real-time chat system with WebSocket support"
 **`intake`** — full spec sheet from raw feedback:
 
 ```bash
-fathom intake "Users need real-time chat and the Zoom integration is broken" --project myapp
-# Extracts discrete work items, classifies each by complexity/priority,
-# estimates tokens + cost per item, attaches velocity benchmarks,
-# outputs structured markdown spec ready for implementation
+# Interactive mode — auto-detects project, shows local files to pick from,
+# prompts where to save the spec
+fathom intake
+
+# Or pass everything directly
+fathom intake --file meeting-notes.md -o intake-specs/sprint-plan.md
 ```
 
+Intake auto-detects your project name from `.claude/te/config.json`, scans the current directory for markdown files to offer as input, and saves specs to `intake-specs/` by default (configurable). Remembers your preferred output directory for next time.
+
 Use `estimate` when you want a quick number. Use `intake` when you want a plan.
 
 Both use a calibrated model: base tokens per task type × complexity multiplier × overhead (context resend, tool calls, thinking, error recovery, planning, review).
@@ -130,17 +135,30 @@ See the [full repo](https://github.com/olivelliott/fathom) for dashboard setup.
 Turn raw feedback into estimated, structured work items:
 
 ```bash
-# From text
-fathom intake "Users say the calendar is slow and Zoom links are missing" --project myapp
+# Interactive — detects files in cwd, prompts for everything
+fathom intake
+
+# Direct — pass input and output explicitly
+fathom intake --file meeting-notes.md -o intake-specs/plan.md
 
-# From a file
-fathom intake --file meeting-notes.md --project myapp --markdown
+# Pipe-friendly — markdown to stdout
+fathom intake --file feedback.md --markdown
 ```
 
-Requires `ANTHROPIC_API_KEY` environment variable.
+When run interactively, intake will:
+1. Auto-detect your project name (or prompt + save it)
+2. List markdown/text files in your current directory to pick from
+3. Show a results table, then ask where to save the spec
+4. Remember your preferred output directory for next time
+
+Output is a buildable markdown spec with task checkboxes, acceptance criteria, priority grouping, and cost estimates.
+
+Requires `ANTHROPIC_API_KEY` environment variable (auto-loaded from `.env`).
 
 ## Environment Variables
 
+Fathom auto-loads `.env` files from the current directory, so you can set these in your project's `.env` instead of exporting them globally.
+
 | Variable | Required | Purpose |
 |----------|----------|---------|
 | `ANTHROPIC_API_KEY` | For `estimate` + `intake` | AI complexity scoring and work item extraction |