BD Intern Agent

Welcome to your first BD hire! Build you Business Development team in < 30 seconds staright from the CLI.

A configurable BD (Business Development) agent for Claude Code. Automates prospect research, outreach drafting, deal pipeline management, meeting prep, competitive analysis, and content creation.

Works for any company — configure once with your company details, products, and voice, then use immediately.

Quick Start

1. Open your Terminal and Clone the plugin

git clone https://github.com/mmashiat/bd-intern.git ~/.claude/plugins/bd-intern

2. enter a new Claude Code session and register the /bd-intern command

Claude Code discovers slash commands from skill files. You need to create one:

mkdir -p ~/.claude/skills/bd-intern
cp ~/.claude/plugins/bd-intern/install/SKILL.md ~/.claude/skills/bd-intern/SKILL.md

3. Configure

Start a new Claude Code session and run:

/bd-intern setup

The setup wizard interviews you about your company, products, voice, and pipeline. Takes ~5 minutes. It generates your config/company.yaml.

Or copy the example and edit manually:

cp ~/.claude/plugins/bd-intern/config/company.example.yaml ~/.claude/plugins/bd-intern/config/company.yaml

3. Use

/bd-intern                   # Main menu
/pipeline                    # View your deal pipeline
/prospect <company>          # Research a prospect
/outreach <company>          # Draft outreach messages
/prep <company>              # Meeting prep briefing
/weekly                      # Weekly pipeline review
/deal <company>              # Deal brief
/crm <company or person>     # Stakeholder lookup
/sales-enablement            # Decks, briefings, one-pagers

What It Does

Feature	Description
Prospect Research	Deep-dives on companies using public sources. Produces structured research docs with product fit assessment.
Outreach Drafting	Personalized cold emails, DMs, and follow-ups grounded in research and meeting history.
Pipeline Management	View, create, and update deals in Linear. Health checks flag stale and at-risk deals.
Meeting Prep	Briefing docs with company snapshot, relationship history, talking points, and strategic questions.
Weekly Review	Pipeline health digest — what moved, what's stale, what needs attention.
Deal Briefs	Comprehensive deal summaries synthesizing all intelligence.
CRM Lookup	Find contacts and stakeholders across your pipeline.
Sales Enablement	Meeting decks, pre-call briefings, post-meeting debriefs, technical briefs, one-pagers, competitive positioning.
Competitive Intel	Competitor profiles, landscape maps, and battle cards.
Follow-Up Tracking	Surfaces overdue action items across all deals.

Configuration

All company-specific settings live in config/company.yaml (gitignored). See config/company.example.yaml for full documentation.

Required Fields

• company.name, company.website, company.description
• products[] — at least one product with name and description
• contact.email

Optional Fields

• brand_voice — tone, personality traits, words to avoid/prefer
• crm.team_name — Linear team name (default: "Partnerships")
• paths.meeting_notes — where meeting notes live (default: ~/.meeting-notes/)
• pipeline.engagement_offer — your standard pilot/POC offer
• competitors[] — known competitors for positioning
• integrations.slack_channel — for pipeline update posts

Product Knowledge

For rich sales enablement content, add a references/product-knowledge.md file with detailed product documentation. The sales-enablement skill uses this as ground truth — it won't make claims not documented here.

Architecture

commands/     → User-facing commands (routing + UX)
skills/       → Execution logic (one skill per capability)
agents/       → Specialized sub-agents (researcher, writer, analyst, reviewer)
references/   → Templates, conventions, pipeline stages
config/       → Company-specific configuration
hooks/        → Session startup context loading
examples/     → Example configs and outputs using fictional companies

How It Works

1. Every command loads config/company.yaml first
2. Commands delegate to skills for execution
3. Skills use agents for specialized work (web research, content writing, analysis)
4. All output uses your configured brand voice, products, and engagement offer
5. Pipeline state tracked in Linear (or configured CRM)

Examples

The examples/ directory contains sample configs and outputs using fictional companies:

• example-config-saas.yaml — SaaS payment company (NovaPay)
• example-config-devtools.yaml — Developer tools company (Lattice Labs)
• example-research.md — Prospect research output
• example-outreach.md — Cold email drafts
• example-meeting-prep.md — Meeting prep briefing

Updating

BD Intern auto-updates on every /bd-intern invocation (silent git pull). Manual update:

cd ~/.claude/plugins/bd-intern && git pull

FAQ

/bd-intern shows "unknown skill" or doesn't appear as a command

Claude Code registers slash commands from skill files in ~/.claude/skills/, not from plugin directories. Cloning the plugin alone isn't enough — you need to register the command:

mkdir -p ~/.claude/skills/bd-intern
cp ~/.claude/plugins/bd-intern/install/SKILL.md ~/.claude/skills/bd-intern/SKILL.md

Then restart Claude Code (start a new session). The /bd-intern command should now appear.

I cloned the repo but nothing happens when I type /bd-intern

Three things to check:

1. Plugin location: The repo must be at ~/.claude/plugins/bd-intern/ (not a subdirectory)
2. Skill file: ~/.claude/skills/bd-intern/SKILL.md must exist (see above)
3. New session: Claude Code loads plugins on startup — you need a fresh session after installing

How do I reconfigure my company profile?

Run /bd-intern setup anytime. It will walk you through the wizard again and overwrite config/company.yaml.

Or edit the file directly:

$EDITOR ~/.claude/plugins/bd-intern/config/company.yaml

Where does my data go?

• Config: ~/.claude/plugins/bd-intern/config/company.yaml (gitignored, stays local)
• Research output: Wherever you set paths.research in config (default: Research/ in your working directory)
• Meeting notes: Wherever you set paths.meeting_notes (default: ~/.meeting-notes/)
• Pipeline: In your Linear workspace (or configured CRM)

Nothing is sent to external servers beyond what Claude Code and Linear already use.

How do I add product knowledge for better sales content?

Create ~/.claude/plugins/bd-intern/references/product-knowledge.md with detailed info about your products — capabilities, specs, use cases, competitive positioning, proof points. The sales-enablement skill uses this as ground truth and won't fabricate claims beyond what's documented.

See skills/sales-enablement/references/product-knowledge.md for the template.

How do I update the plugin?

It auto-updates on every /bd-intern invocation. For manual updates:

cd ~/.claude/plugins/bd-intern && git pull

After updating, also refresh the skill file in case it changed:

cp ~/.claude/plugins/bd-intern/install/SKILL.md ~/.claude/skills/bd-intern/SKILL.md

The setup wizard is too long / I want to skip questions

Say "skip" or "use defaults" at any point during setup. The wizard will fill in sensible defaults for anything you skip. Only company name, one product, and contact email are truly required.

License

MIT