scope-tool

Two Claude Code skills for scoping AI build sessions during prospect calls.

/scope-intake creates a client project directory and seeds notes, context, and estimate files. Run at the start of a call.

/scope-est generates a build estimate from your notes and context. Shows session breakdown, hours, and cost. The deliverable you email after the call.

Built for consultants who do live implementation sessions. Split-screen workflow: notes in your editor, Claude Code in the terminal.

Install

cp .env.example .env   # Set your rate, session length, calendar link
./install.sh            # Symlinks skills to ~/.claude/skills/

Then /scope-intake and /scope-est are available globally.

Config

Copy .env.example to .env and set your values:

HOURLY_RATE=300
SESSION_LENGTH_MINUTES=90
CALENDAR_LINK=https://your-calendar-link

The .env file is gitignored.

Usage

# Starting a prospect call:
/scope-intake Jane Smith       # Interactive setup
/scope-intake Jane --fast      # Skip prompts, auto-generate tagline

# After taking notes:
/scope-est                     # Interactive — asks about blockers
/scope-est --fast              # Skip prompts, treat blockers as assumptions

Workflow

1. Run /scope-intake before the call starts
2. Open notes.md in your editor — type while you listen
3. Claude tracks decisions and questions in context.md
4. Run /scope-est to generate the estimate
5. Email estimate.md to the prospect

Project Structure

Each client gets a directory under estimates/:

estimates/
  jane-smith/
    260308-jane-smith-podcast-automation/
      notes.md      # Your notes (human-owned)
      context.md    # Claude's notes (decisions, todos, questions)
      estimate.md   # Generated deliverable

Safety

• All writes constrained to estimates/ directory
• Path traversal validation before every write
• Allowed-tools whitelist enforced per skill

License

MIT