Help us improve
Share bugs, ideas, or general feedback.
From bd-intern
Generates deal brief synthesizing intelligence from Linear projects, research MDs, meeting notes, content, and config YAML. Includes executive summary, timeline, status, value prop, risks, next steps.
npx claudepluginhub mmashiat/bd-internHow this skill is triggered — by the user, by Claude, or both
Slash command
/bd-intern:deal-briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read `config/company.yaml` from the bd-intern plugin directory. Use:
Generates structured pre-meeting briefing documents from company config, research files, Linear projects, meeting history, and fresh intelligence via researcher agent. Saves as Markdown file.
Aggregates diligence findings into tiered briefings (exec summary, deal lead, working team). Invoke via 'brief the deal team' or 'deal update'.
Generates scannable HTML account dossiers and call prep documents for internal sales use from company domains, person emails, or contexts, tailored to occasions like discovery, demo, or QBR.
Share bugs, ideas, or general feedback.
Read config/company.yaml from the bd-intern plugin directory. Use:
company.name, products[] — for value propositionpipeline.engagement_offer — for recommended next stepscrm.team_name — for Linear queriespaths.research, paths.meeting_notes, paths.content — for intelligenceIf config is missing, stop and tell the user to run /bd-intern setup.
{crm.team_name} team{paths.research}/{company}*.md — prospect research{paths.research}/Competitive/{company}*.md — competitive research{paths.meeting_notes} for all company mentions{paths.content}Use the writer agent (agents/writer.md) to produce:
3-5 sentences: Who they are, where the deal stands, what's next, key risk.
Condensed from research — what matters for this deal.
| Date | Event | Key Outcome |
3 specific actions with suggested owners and dates.
Save to {paths.research}/{Company} Deal Brief.md