strategy-interview
From the author
Use when the user wants to build or think through a strategy via guided conversation — for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).
Install
npx skills add existential-birds/beagle --skill strategy-interview -a claude-code
Installs to .claude/skills/strategy-interview/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 80
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- brainstorm-beagleexistential-birds/beagleUse when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews — produces a WHAT/WHY spec through dialogue, not a HOW plan.Planning★ 84
- brainstormingGanyuanRan/AegisUse when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.Planning★ 1.4K
- strategy-reviewexistential-birds/beagleUse when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).Engineering★ 84
- interview-meaddyosmani/agent-skillsExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.Planning★ 110.1K
- pm-deep-talkkonglong87/superPMUse when: 用户已有产品想法、方案、计划或待选方案，希望分析利弊、梳理选择标准、补全关键考虑或获得决策建议 用户明确要求“深入聊聊”“分析这个方案”“帮我梳理取舍”“我该怎么选” 用户在 pm-brainstorm 中选定方向后，主动要求进一步讨论其可行性与取舍 Do NOT use when: 用户还没有方向，只想产生多个创意（使用 pm-brainstorm） 用户只需要事实调研、需求验证、市场分析、优先级计算或文档撰写（使用对应 skill）Planning★ 83
- interviewboshu2/agentopsInterview you one question at a time, each choice with a recommendation, to settle a big outcome before agents work alone. Use when: asked to interview you about a goal or plan.Planning★ 450
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in