Brad Zhang / public archive

Brad Zhang

AI product notes, agent workflow writing, and open-source dossiers for founders and early technical teams.

Open source/skill-adoption-planner

Project dossier / README

skill-adoption-planner

yizhiyanhua-ai/skill-adoption-planner

A planning layer for whether a skill should actually be adopted.

AI workflow libraries fail when everything gets added but nothing gets adopted. Adoption discipline is part of product quality.

Repository reading order

Understand the workflow it replaces before deciding whether to stay in the README, open a topic path, or move toward collaboration.

01 / Workflow

Collecting skills without evaluating fit, payoff, or operational friction.

Start by naming the old workflow this repo is replacing.

02 / README

Skill Adoption Planner 🇨🇳 中文 Plan Skill rollout strategies within organizations, identify seed users, create phased plans, and prepare for resistance.

Then use the README and site interpretation to confirm the project boundary and delivery surface.

03 / Proof graph

Technical distribution for AI builders

Finally, place the repository back into a bigger market question and working conversation.

github.com/yizhiyanhua-ai/skill-adoption-planner

Skill Adoption Planner

🇨🇳 中文

Plan Skill rollout strategies within organizations, identify seed users, create phased plans, and prepare for resistance.

Features

  • Analyze department characteristics and tech acceptance
  • Prioritize departments for rollout
  • Identify key roles (seed users, influencers, resistors)
  • Generate phased adoption plans
  • Predict and address common resistance

Usage

# Analyze departments
python scripts/analyze_departments.py \
  --departments "技术,产品,销售,市场,财务,HR"

# With company size for headcount estimates
python scripts/analyze_departments.py \
  --departments "技术,产品,销售" \
  --total-size 200

# Output as JSON
python scripts/analyze_departments.py --json ...

Supported Departments

Department Tech Acceptance Best Strategy
Engineering High Seed department, emphasize efficiency
Product High Sync with engineering, collaboration focus
Sales Medium ROI-driven, ready-to-use Skills
Marketing Medium Creative assistance, content generation
Finance Low Accuracy focus, start with low-risk scenarios
HR Low Simple tools, emphasize assistance not replacement
Customer Service Medium High-frequency use cases, quick wins
Legal Low Expert involvement, human review required
Operations Medium Data-driven, show efficiency gains

License

MIT

Related clusters

A project page should also return to the bigger market question.

Commercial outcomes

Founding engineer fit

Design partner sprint

Developer-facing proof work

skill-adoption-planner | Open Source Project