Skip to content

feat: add Sales & Revenue division with 4 enterprise agents#124

Closed
kienbui1995 wants to merge 3 commits intomsitarzewski:mainfrom
kienbui1995:feat/add-sales-revenue-division
Closed

feat: add Sales & Revenue division with 4 enterprise agents#124
kienbui1995 wants to merge 3 commits intomsitarzewski:mainfrom
kienbui1995:feat/add-sales-revenue-division

Conversation

@kienbui1995
Copy link

What

Adds a new Sales & Revenue division with 4 specialized agents covering the full B2B revenue cycle — from technical pre-sales through deal close to post-sale success.

Why

The Agency has zero sales coverage across 112 agents and 11 divisions. Sales is a universal enterprise function and AI is transforming it rapidly. This fills the biggest enterprise-facing gap in the roster.

New Agents

Agent Specialty
🎯 Sales Engineer Technical pre-sales, demos, POCs, RFP/RFI responses, solution architecture
📈 Revenue Operations Analyst CRM optimization, pipeline analytics, forecasting, cross-functional alignment
🤝 Customer Success Manager Adoption, retention, expansion, health scoring, churn prevention
💼 Account Strategist Deal strategy, MEDDPICC qualification, stakeholder mapping, competitive positioning

Infrastructure Changes

  • scripts/convert.sh — added sales-revenue to AGENT_DIRS
  • scripts/install.sh — added sales-revenue to claude-code and copilot install loops
  • .github/workflows/lint-agents.yml — added sales-revenue/** to paths trigger
  • README.md — added Sales & Revenue roster between Product and Project Management

Testing

  • Lint: 0 errors, 0 warnings across all 4 files
  • Conversion: 116 agents total (112 existing + 4 new) — all convert correctly

bmkien added 3 commits March 11, 2026 15:04
Add a new Sales & Revenue division covering the full B2B revenue cycle:

- Sales Engineer: technical pre-sales, demos, POCs, RFP responses
- Revenue Operations Analyst: CRM optimization, forecasting, pipeline analytics
- Customer Success Manager: adoption, retention, expansion, health scoring
- Account Strategist: deal strategy, stakeholder mapping, competitive positioning

Infrastructure updates:
- Add sales-revenue to AGENT_DIRS in convert.sh
- Add sales-revenue to claude-code and copilot install loops
- Add sales-revenue/** to lint-agents.yml CI paths
- Add division roster to README.md
- Add profiles.yaml: 20 role-based profiles (4 global + 16 project)
  mapping curated skill sets to each agent
- Add convert.sh --tool kiro: generates 116 SKILL.md files + 19 agent
  JSON configs from profiles.yaml
- Add install.sh --tool kiro: installs skills-library + global agents,
  auto-migrates existing agency-* skills from ~/.kiro/skills/
- Add setup-project.sh: interactive project bootstrapper for .kiro/
- Add integrations/kiro/README.md with architecture docs

Solves token overhead: ~8000 tokens (all skills global) -> ~400 tokens
(agent with 4 progressive-loaded skills via skill:// URIs).
New agents (based on skills.sh top skills):
- Dev process: systematic-debugger, tdd-practitioner, code-reviewer, git-workflow-master
- Framework: react-specialist, nextjs-specialist, vue-specialist, python-specialist,
  typescript-advanced, database-optimizer
- Utility: document-generator, mcp-builder, conversion-optimizer

New Kiro profiles: react-dev, nextjs-dev, vue-dev, python-dev
Updated fullstack-dev profile with dev process skills
Total: 129 agents, 23 Kiro profiles
@msitarzewski
Copy link
Owner

Hey @kienbui1995 — really appreciate the ambition here. This is a big contribution and clearly a lot of work went into it.

A few things to sort through:

Sales Division — Great minds think alike! We actually just landed a Sales division today with 8 agents (Outbound Strategist, Discovery Coach, Deal Strategist, Sales Engineer, Proposal Strategist, Pipeline Analyst, Account Strategist, Sales Coach) grounded in MEDDPICC, SPIN, Challenger, Gap Selling, and other real methodologies. So the sales-revenue agents here overlap with what's already on main. Your Customer Success Manager is an interesting angle we didn't cover though — worth a look as a standalone PR if you're interested.

Kiro integration files — We have a standing policy that pre-generated integration output stays gitignored and never gets committed (see #73, #92 for prior context). Users run convert.sh locally. However, adding Kiro support to convert.sh and install.sh would be very welcome as a separate, focused PR!

Engineering agents — The 10 new engineering agents (Code Reviewer, Database Optimizer, TDD Practitioner, etc.) are potentially interesting. Could you split those out into a separate PR? That way we can evaluate them on their own merits without the noise of the larger changeset.

In general, smaller focused PRs are much easier to review and merge quickly. Would love to see this broken up into:

  1. Sales agents (covered now)
  2. Engineering agents (separate PR)
  3. Kiro convert.sh/install.sh support (separate PR, no generated files)

Thanks for the contribution!

@kienbui1995
Copy link
Author

Closing this in favor of smaller, focused PRs per your feedback. Thanks for the detailed review!

Breakdown plan:

  • Kiro CLI integration → Already covered by feat: add Kiro CLI integration #121 (convert.sh/install.sh support only, no generated files)
  • Sales agents → Covered by the Sales division already on main
  • Engineering agents (10 new agents) → Separate PR coming
  • Customer Success Manager → Standalone PR coming
  • Specialized agents (mcp-builder, document-generator, conversion-optimizer) → Separate PR coming

Will rebase each on latest main. Thanks again for the guidance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants