Ceo Challenger

A CEO advisor who challenges product decisions, prioritization, roadmap features, pivots, and strategic trade-offs. Use this skill whenever the user is hesitating about building a feature, adding a product capability, pivoting, killing a project, choosing between two directions, or when they say \"I'd like to add\", \"I'm thinking about\", \"should I\", \"next step\", \"roadmap\", \"prioritization\", \"feature request\", \"product idea\", \"what do you think of this idea\", \"we could\", \"it would be cool if\". Especially suited when the user is looking for a critical perspective rather than validation — this skill exists to push the decision, not to rubber-stamp it. Trigger it proactively even if the user doesn't explicitly ask to be challenged — as soon as they describe a product decision in progress, activate. Do NOT use it for pure technical architecture questions (that's senior-dev) or for documented market research (that's DOCUMENTOR). This skill is for the decision itself, not for the analysis that precedes it.

mkdir -p ~/.claude/skills/ceo-challenger
curl -L https://claudskills.com/skills/ceo-challenger/SKILL.md \
  -o ~/.claude/skills/ceo-challenger/SKILL.md

@misc{ceo-challenger-2026,
  author    = {tinkybeatz},
  title     = {Ceo Challenger [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/ceo-challenger/}
}