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.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryScience & researchStars0
About this skill
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.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Science & research
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.